There should be a short usage section

[tuhdo]

I think even a link to this article from from @Malabarba would be very useful.

[tuhdo]

What I really mean is that there should be sample configuration with premade key bindings to all frequently used commands, so users can easily copy and try the package and later modify the keys.

[tuhdo]

w should be explicitly mentioned that it can copy code from answer to the mark ring. This is an extremely feature imo.

[Malabarba]

Yeah, we could suggest a keymap on the readme. More importantly, we need an entire Readme section about the question buffer, then we could mention the w key. Any volunteers? =)

[vermiculus]

I volunteer!

[Malabarba]

:+1: :-)

[vermiculus]

@tuhdo @Malabarba Anything you'd add to the above?

[tuhdo]

There should be a sample Elisp configuration with key bindings. That way, people can quickly copy/paste and try out sx, without the hassle of writing the boilerplate themselves.

[vermiculus]

I'm not sure what key-bindings are necessary beyond the default. Can you share your configuration? (Ironically, I don't get to use this much – my work computer can't manage the url business and I haven't had the free time to fix it there.)

[tuhdo]

Key bindings that enable us to enter sx to use the rest of default key bindings. The key bindings specified in @Malabarba's article is a good example.

[vermiculus]

@tuhdo Ah! I never thought about those commands :) Smex/flx-ido have spoiled me :) Is everyone satisfied with the above? Any more ideas/things to add?

[Malabarba]

I like both commits. It occurs to be now that we should mention sx-search in with the entry commands as well. Besides this, and the comments I made on the commit, I'm good with merging.

Thanks Sean

[tuhdo]

Look perfect now. I have no further idea.