unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ole Laursen <olau@iola.dk>
To: emacs-devel@gnu.org
Cc: Ole Laursen <olau@iola.dk>
Subject: icomplete-mode as replacement for iswitchb
Date: Tue, 11 Nov 2014 10:10:09 +0100	[thread overview]
Message-ID: <CANb2OvJ-tJf2tnB0A6L7sFdKJEBfLFDfZ3grB0FPMgc6c6hZNQ@mail.gmail.com> (raw)

Hi!

I ending up using iswitchb many years ago after trying all other
alternatives at the time (iswitchb had the most polished buffer
switching implementation IMHO). Now I'm on 24.4 and have been trying
to switch to icomplete:

1) Turning on icomplete makes C-x C-f show a list of matches (despite
icomplete-show-matches-on-no-input being nil - this is a little
jarring, but I think I can get used to it)

2) However C-x b doesn't show any matches on no input - this breaks my
quick-switch-between-a-few-buffers-in-working-set habit (C-x b, C-s a
couple of times, RET)

3) RET in C-x b on a partial match means "open new buffer with partial
name" - I am trying to get used to C-j instead, but after a while I
think RET is more ergonomic in many cases because it frees you from
having to time a Ctrl press (e.g. f, o, o, RET is easier than f, o, o,
C-j)

I don't see why you'd want to be able to start a new buffer while
switching buffers. Switching buffers is a high-speed operation done
many times a day.

I realize some of this comes from old Emacs traditions, but from my
point of view, making sure RET has the same result as C-j when
switching buffers and either turning on
icomplete-show-matches-on-no-input as default, or even better only for
some completion scenarios where it makes sense (working set ones),
would be really helpful.


Ole



             reply	other threads:[~2014-11-11  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11  9:10 Ole Laursen [this message]
2014-11-11 16:31 ` icomplete-mode as replacement for iswitchb Stefan Monnier
2014-11-11 17:52   ` Ole Laursen
2014-11-12 12:46     ` Ole Laursen
2014-11-12 17:10       ` Stephen Leake

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=CANb2OvJ-tJf2tnB0A6L7sFdKJEBfLFDfZ3grB0FPMgc6c6hZNQ@mail.gmail.com \
    --to=olau@iola.dk \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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