From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Read only mode for sup
Date: Thu, 09 Apr 2009 10:30:09 -0700 [thread overview]
Message-ID: <1239297831-sup-5831@entry> (raw)
In-Reply-To: <1239226676-sup-7216@entry>
Reformatted excerpts from William Morgan's message of 2009-04-08:
> One easy thing to comes to mind would be to have buffer-list-mode
> (which is what you get when you hit B) sort the buffer list by last
> access. Remap that to something like ";" and you have one-handed
> buffer- switching with minimal keystrokes.
Ok, I've done this on branch 'better-buffer-list', which I've merged
into next. Pull and see how you guys like it. Summary:
1. 'b' rolls the buffer forward as usual.
2. 'B' now rolls the buffer backwards like in the olden days.
3. ';' pulls up the buffer list, which is now sorted by access time,
colorized to show "system" vs non-"system" buffers, and has little
stars for buffers with unsaved content.
4. '+' is now the apply-to-tagged command.
Sorry for changing so many keymappings, but I really wanted ';' so that,
with 'j' and 'k', you can swap buffers really quickly with just one
hand. Since that freed up B, I figured I'd reenable the old behavior,
and '+' kinda makes sense for apply-to-tagged anyways.
Nicolas, I had to revert your "Buffer switching, 'bn' for the next one
and 'bp' for the previous" change in next. I hope you're not offended! :)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-04-09 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 18:26 Nicolas Pouillard
2009-04-07 23:29 ` Ian Smith
2009-04-08 8:36 ` Nicolas Pouillard
2009-04-08 12:30 ` Ian Smith
2009-04-08 17:01 ` Andrew Pimlott
2009-04-08 22:18 ` William Morgan
2009-04-08 19:03 ` Wirt Wolff
2009-04-08 21:49 ` William Morgan
2009-04-09 11:55 ` Nicolas Pouillard
2009-04-09 17:30 ` William Morgan [this message]
2009-04-10 8:36 ` Nicolas Pouillard
2009-04-10 12:24 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1239297831-sup-5831@entry \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox