unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: repeat-on-final-keystroke
Date: Mon, 24 Apr 2006 09:31:51 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICIEDEDFAA.drew.adams@oracle.com> (raw)
In-Reply-To: <Xg63g.8599$sq5.462@newsread2.news.atl.earthlink.net>

    > editing tens of different buffers, which is typical for me

    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.

Hack! Cough!

    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).

In that case it _would_ be convenient? Argggh!

    You can also filter out *Help, *Info, and other
    read-only buffers with iswitch...

Try Icicles. It's designed to be useful with large numbers of completion
candidates (in this case, buffer names). No need to jump through hoops to
finagle buffer names so they have prefixes that follow some convention, read
their names backward, or any such witchcraft.

In addition to the prefix matching of vanilla Emacs, Icicles gives you
apropos-style matching. You can 1) match any substring of the name (in fact,
you can match any regexp against the name), and you can 2) cycle among those
matches. With a large number of candidates, you typically use apropos
matching to narrow the choices and then you might cycle among the remaining
candidates using a single key (e.g. `next').

Does "regexp matching" sound scary, complicated, difficult? 1) Don't forget
that _any_ string of letters, numbers and such is also a regexp, so this
gives you substring matching without doing anything special. 2) With
Icicles, you can use one simple regexp (e.g. just a substring) to filter,
and then use another simple regexp (e.g. another substring) to filter
further, and so on - any number of times. This is just like doing grep plant
*.txt | grep food | grep mineral: you can find multiple substrings of a
buffer name (or file name or...) that might appear in any order within the
name.

Here is the doc (which has a link to the library files):
http://www.emacswiki.org/cgi-bin/wiki/Icicles. Have fun!

  parent reply	other threads:[~2006-04-24 16:31 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 ` repeat-on-final-keystroke B. T. Raven
2006-04-24 16:25   ` repeat-on-final-keystroke Kevin Rodgers
2006-04-24 16:31   ` Drew Adams [this message]
     [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=DNEMKBNJBGPAOPIJOOICIEDEDFAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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).