unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ole Laursen <olau@iola.dk>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: icomplete-mode as replacement for iswitchb
Date: Tue, 11 Nov 2014 18:52:33 +0100	[thread overview]
Message-ID: <CANb2Ov+R3iRsvuJCMzF1RpTQCuV=3-4_US1EFT8_2GZDbydSdg@mail.gmail.com> (raw)
In-Reply-To: <jwvmw7xitw0.fsf-monnier+emacs@gnu.org>

Thanks for the kind answer.

2014-11-11 17:31 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> 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)
>
> I think that's a bug.  Could you M-x report-emacs bug so we don't forget it?

I think it's perhaps triggered by the path. But yes, I'll report it.

I played around with things a bit more and found another more serious
bug so I'm back on iswitchb. I'll report that too.

>> 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 think this will have to stay a user-config (you can change that for
> yourself in icomplete-mode-map).

Yeah, I see that it's a useful difference for C-x C-f. It works the
way I expect for M-x completions, so perhaps my request is really to
remove the possibility of opening a new named buffer through C-x b - I
think then RET and C-j would be the same. I don't know if that's out
of the question.


Ole



  reply	other threads:[~2014-11-11 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11  9:10 icomplete-mode as replacement for iswitchb Ole Laursen
2014-11-11 16:31 ` Stefan Monnier
2014-11-11 17:52   ` Ole Laursen [this message]
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='CANb2Ov+R3iRsvuJCMzF1RpTQCuV=3-4_US1EFT8_2GZDbydSdg@mail.gmail.com' \
    --to=olau@iola.dk \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).