Org Mode Summary

I recently saw this Org-mode summary from the Linux Journal mentioned in a tweet. It’s pretty old—from 2007—but still serves as a useful introduction to some of Org-mode’s power. If you’ve never used Org-mode, this article will give you a feeling for what it can do.

The best introduction and go-by remains Bernt Hansen’s excellent Org Mode – Organize Your Life In Plain Text! It’s quite long but very comprehensive and Hansen considers it a work in progress so it’s always up to date. It’s the perfect follow on to the Linux Journal article. Of course, Org-mode comes with a comprehensive manual that covers everything in detail. There is also an compact Org-mode Guide that can serve as a sort of quick start manual, although I prefer Hansen’s guide.

With all this great documentation, there’s no excuse for not giving Org-mode a spin. Be warned though: it will insinuate its way into almost every aspect of your work flow.

Posted in General | Tagged , | 2 Comments

Complexity Cheat Sheet

Eric Rowell and Nick Dizazzo have posted a great Big-O cheat sheet. The sheet gives time and space complexity for several popular algorithms such as searching, sorting, and manipulation of data structures and graphs. One feature that I like is a graph that shows the curves for O(1), O(log(n)), O(n), O(nlog(n)), O(n2), O(2n), and O(n!). It demonstrates in a dramatic way how algorithms exhibiting these behaviors differ.

If you find yourself having to look up the complexity of algorithms occasionally, bookmark this page and have the information at your fingertips.

Posted in Programming | Tagged | Leave a comment

linedit

Pavel Penev has updated and republished his excellent post Learning Lisp The Bump Free Way. It’s a nice introduction to the problems that Lisp n00bs face and how to overcome them. If you know anyone struggling with learning Lisp, this is a good resource to point them to.

I learned something too: linedit. linedit is a readline-like library (written in CL) that brings greater editing functionality to the CL REPL. It’s got a lot of features that are detailed at the link so be sure to take a look if you ever use Lisp directly from the terminal. It appears to be (at least somewhat) SBCL-centric so users of other distributions may have varying results. It’s available from Quicklisp so installation is a snap. You add a couple of lines to your .sbclrc file to enable it and another line to your Emacs configuration to prevent it from interfering with Slime. The appropriate incantations are explained on the linedit site.

If you’re like me, you mostly use Lisp in conjunction with Slime but when I do use the terminal I always miss having basic line editing so linedit is a win for me.

Posted in General | Tagged , | Leave a comment

DRM-Free Day

Today is DRM-free day. To celebrate O’Reilly is offering 50% off on their entire ebook inventory1. I used the occasion to pick up a copy of Writing GNU Emacs Extensions. If you have any O’Reilly books on your “to purchase” list, this would be a good time. The sale ends at the end of the day (May 3) so hurry.

Footnotes:

1 I’m not an affiliate or connected to O’Reilly in any way (other than as a customer) and I don’t get anything from this post other than the satisfaction of performing a public service by letting you know about an opportunity to save some money.

Posted in General | Tagged , | Leave a comment

A Summary of New Libraries in April’s Quicklisp

Ben Hyde has produced a summary of the new libraries in April’s Quicklisp distribution. Each item has a link to the library’s README so it’s easy to get a more detailed look at libraries that interest you. A very nice piece of work. I hope he continues with it or, as Masataro Asai suggested, automate it and make it available as an RSS feed.

Posted in Programming | Tagged , | Leave a comment

EmacsMovies Looks at Gnus

Noufal Ibrahim has resumed his EmacsMovies series. This time it’s part 1 of a series on Gnus. Gnus is famously complex so Ibrahim’s taking the subject in smaller bites makes sense. As it is, the video is over 21 minutes long.

I’ve often thought about learning Gnus but its fierce reputation always persuaded me to explore some other aspect of Emacs instead. Thus, I’m looking forward to this series to goad me into finally taking a serious look at it. This first video is really just an introduction to Gnus and doesn’t get into the details; presumably subsequent videos will deal with the nitty gritty.

I had a small problem with the video. I was unable to get it to expand to full screen—in either Safari or Chrome—and the default size is too small to read comfortably (at least for my eyes). Because of this, I had a hard time following part of the presentation. I don’t remember this happening with the previous videos so perhaps this problem will resolve itself in subsequent videos.

Posted in General | Tagged | 3 Comments

SBCL 1.1.7 Released

The folks at Steel Banks Common Lisp have released SBCL 1.1.7. As usual the build, test, and installation went without mishap. This month’s release is mainly bug fixes but also includes an enhancement to TRACE so that PRINT-ALL handles multiple-valued forms.

As always, thanks to the developers for continuing to make SBCL one of the best Lisp environments.

Posted in Programming | Tagged , | Leave a comment

Why Sites Have Bad Password Policies

Ars Technica has an excellent article on why many sites have security limiting password policies. I’ve written about this before on my old blog, but the Ars Technica article is particularly infuriating. So much so that this is my second attempt at writing about it; I had to abandon the first attempt for mental health reasons.

We all know the horror stories. There’s the brokerage firm that limits passwords to 5, 6, or 7 characters. Others have a seemingly arbitrary prohibition on some or all symbols. Many limit password length in arbitrary ways. Ways that suggest the passwords themselves are being stored rather than a hash of the passwords1.

But why do they have these restrictions? If they are implementing robust password security (using bcrypt, scrypt, PBKDF2, etc.) the restrictions don’t make any sense. Sure, maybe you want to limit your input buffer to 1K or even 512 bytes but that’s not a serious restriction. To find out, Ars Technica queried some of the offending sites about the reasons for their password policies.

The answers, as I say, are infuriating. One major company, which should certainly know better, says that most attacks can’t be defended against by password length and that in any event password cracking is hardly their biggest security problem. Another says that they allow only the dash and underscore symbols because symbols are harder to enter on mobile devices and customers don’t like entering them even on computers (I’m not making this up).

Go read it for yourself. There are other examples. Some make reasonable technical arguments involving regular expressions that check for password validity but here’s the thing: if you simply accept up to some number—512, say—of bytes for the password and hash the result using something like bcrypt you don’t have to do any validity checking. Hash functions don’t care what bytes you feed them and the end result of bcrypt and its brethren are a fixed length so managing storage space in a non-issue. Really, doing it right is simpler. It’s time to fix this instead of offering lame excuses. And please, stop telling me it’s raining.

Footnotes:

1 What does a maximum password of 15 ASCII characters suggest to you?

Posted in General | Tagged | Leave a comment

Vi(m) and Lisp

Those of you who have been around for a while know that I was a Vi(m) user for a long time. I switched to Emacs when I started doing most of my programming in Lisp and Scheme. My main reason for the switch was to get Slime. It’s inconvenient, although possible, to program Lisp interactively in Vi. Yes, Yes, I know about Paul Graham and doubtless many others but the point stands.

Until I read Dorai Sitaram’s post on Editing Lisp and Scheme files in vi, I hadn’t realized another problem with programming Lisp in Vi: indentation. When you’re programming in C, which I mostly was in those days, the Vi family of editors does a very nice job of autoindenting your code as you enter it. It wasn’t as good at reformatting, as I recall, but I don’t remember ever being annoyed by it so it was, apparently, good enough. I usually handled natural language reformatting with fmt which, again, wasn’t seamless but seemed good enough at the time.

Sadly, there’s not a good solution for Lisp/Scheme code1. That’s what Sitaram’s post is about: external, fmt-like, filters to handle the chore. The seamless formatting of whatever code you happen to be writing is something that Emacs users just take for granted and reading Sitaram’s post made me realize that I’ve been spoiled—or assimilated as the Borg would say—by this. I wouldn’t want to be using Vi even if they had a reasonable Slime solution (which, apparently, they do).

As I’ve written before, I never enlisted in the Vi/Emacs holy wars and even though I’m (now) thoroughly committed to Emacs I still have warm feelings for Vi(m) and maintain a great deal of respect for it. That said, I don’t think I’d want to be a Vi Lisp programmer. One can (and many do) live in both worlds by using Evil but when I switched I decided to go all in and embrace the native interface. I’m glad I did but everyone’s different so Evil or even Vi(m) might be a better fit for some. If you’re a Vi(m) user and write in Lisp, what has your experience been?

Footnotes:

1 Apparently Vim has improved this situation somewhat in the last few releases. If you’re a Vim user and your experience is different, please leave a comment and let us know.

Posted in Programming | Tagged , | Leave a comment

Tips on Securing a WordPress Site

After the recent WordPress Administration Page attack, my hosting provider sent its customers a link to the WordPress page on securing WordPress sites. It’s an excellent resource if you’re running WordPress and some of the ideas are general enough that they can be used in other environments as well.

If you’ve got a blog or some other permanent Web presence, you should take a look at the page and implement the suggestions that make sense for your situation.

Posted in General | Tagged | Leave a comment