j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
It's simpler for the end user. Instead of the end-user being mandated to supply a callable function, we should provide a couple recipes that they can supply as strings.
On Fri, Apr 8, 2011 at 11:53 AM, Stephen Skory firstname.lastname@example.org wrote:
I would propose it accept either a string that identifies an existing recipe or a callable.
I don't quite see how this is simpler, unless you're proposing that I write a whole bunch of built-in recentering functions in this new file. Maybe I'm misunderstanding you? I'm sorry that I'm thick!
-- Stephen Skory email@example.com http://stephenskory.com/ 510.621.3687 (google voice)
Yt-dev mailing list Ytfirstname.lastname@example.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org