From: "B. T. Raven" <ecinmn@peoplepc.com>
Subject: Re: repeat-on-final-keystroke
Date: Mon, 24 Apr 2006 15:37:27 GMT [thread overview]
Message-ID: <Xg63g.8599$sq5.462@newsread2.news.atl.earthlink.net> (raw)
In-Reply-To: mailman.732.1145653193.9609.help-gnu-emacs@gnu.org
"Enzo Vitale" <enzo.vitale@epfl.ch> wrote in message
news:mailman.732.1145653193.9609.help-gnu-emacs@gnu.org...
> Dear Emacs experts,
>
> I have rebound the 'bs-cycle-next' command to 'C-x b' and I would very
> much like it to behave as 'repeat' in the sense that continuing to
> press
> simply the last character of the key-binding ('b' in this case) had
> the effect of scrolling one by one the list of active buffers.
>
> Currently, I have to retype 'C-x b' each time, very annoying when
> editing tens of different buffers, which is typical for me during code
> development.
>
> By the way, the same would also be very useful with the 'undo' command
> (C-x u), and probably many more...
>
> Is this possible ?
>
> Thank you,
> Enzo
>
>
For that many buffers it seems like iswitchb would work better if you
could use a naming convention that made the names differ more at the
beginning of the string than at the end. This might not be convenient
unless you could get used to reading the buffer names backwards a l'arabe
(i.e. "h.sfed" for "defs.h" by performing reverse-string of file name to
get buffer name). You can also filter out *Help, *Info, and other
read-only buffers with iswitch.
If you can set up a super key modifier, you could cycle through the
buffers by adding
(global-set-key [(super b)] 'bury-buffer)
to your .emacs, but this has the undesirable side effect of removing the
names from the menu bar buffer list. It does however require only one
keypress per buffer switch if you don't count holding down the super key
continously as a keypress.
Ed.
next prev parent reply other threads:[~2006-04-24 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.732.1145653193.9609.help-gnu-emacs@gnu.org>
2006-04-22 20:32 ` repeat-on-final-keystroke liyer.vijay
2006-04-24 10:40 ` repeat-on-final-keystroke Oliver Scholz
2006-04-24 15:37 ` B. T. Raven [this message]
2006-04-24 16:25 ` repeat-on-final-keystroke Kevin Rodgers
2006-04-24 16:31 ` repeat-on-final-keystroke Drew Adams
[not found] ` <mailman.870.1145895999.9609.help-gnu-emacs@gnu.org>
2006-04-24 19:56 ` repeat-on-final-keystroke B. T. Raven
[not found] <mailman.871.1145896319.9609.help-gnu-emacs@gnu.org>
2006-04-24 22:05 ` repeat-on-final-keystroke B. T. Raven
2006-04-21 13:45 repeat-on-final-keystroke Enzo Vitale
2006-04-21 21:23 ` repeat-on-final-keystroke Leon
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='Xg63g.8599$sq5.462@newsread2.news.atl.earthlink.net' \
--to=ecinmn@peoplepc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).