unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jeff Weiss'" <jweiss@redhat.com>, <jeffrey.m.weiss@gmail.com>,
	<help-gnu-emacs@gnu.org>
Subject: RE: migrating from ido to icicles
Date: Fri, 21 Dec 2012 10:31:41 -0800	[thread overview]
Message-ID: <B46C946BE52E425FB38FE9020746141C@us.oracle.com> (raw)
In-Reply-To: <87r4mkoybz.fsf@blinky.jweiss.com>

> Sorry yes I meant M-TAB.

I started that confusion, I guess. ;-)

> >> However the docs for icicle-word-completion-keys suggest that 
> >> I can also bind SPC if I wanted.  That actually sounds better
> >> because I can't remember the last time I tried to complete a
> >> filename with a space in it.
> >
> > I don't recommend that, but you are welcome to do it.  Icicles
> > completion works for all kinds of things, many of which contain
> > space chars.
> 
> Ok, maybe it won't work out,

It will work out.  It's just that with Icicles you might well end up completing
things that contain space chars, and in that case you might prefer not to have
to use `C-q SPC'.

> but I definitely use actual space characters very rarely in the
> minibuffer for completion.

You might end up using completion for more than you have so far.

> > 3. Toggle Icicle mode twice (exit and re-enter): M-x 
> > icy-mode M-x icy-mode.  (Or restart Emacs.)
> 
> I'll try that, thanks.  In general do I need to cycle icy-mode off/on
> when I change these bindings?  I've noticed sometimes changes 
> don't seem to take effect immediately, it's hard to tell which ones 
> require restart.

Most option value changes are reflected immediately, without your needing to do
anything else.

And in many cases you can hit a key during minibuffer input to toggle or cycle
particular options.  For example, `C-M-"' cycles
`icicle-expand-input-to-common-match' and `C-#' cycles
`icicle-incremental-completion'.

In some cases, notably minibuffer key bindings, you need to exit then reenter
Icicle mode, e.g., use `M-x icy-mode' twice.  The doc strings of the options
that require you to toggle Icicle mode should mention that.

Key-binding option changes generally require you to toggle Icicle mode because
it is when the mode is turned on/off that the bindings are made/unmade.

> > That option name should be without the `-flag'.  Long ago 
> > the option was a Boolean and its name had the suffix `-flag'.
> > Since you mention a value of `1' you clearly do not have an
> > older version of Icicles where the option had that former name.
> 
> Ok, I copy/pasted that from the wiki page,

Ouch!  Thanks, I found a couple such occurrences and have fixed them.

FYI, I update the plain-text doc that is distributed with the code, and then I
diff that to update the wiki pages.  Glad you caught this.

> > This explains common-match expansion:
> > 
> > http://www.emacswiki.org/emacs/Icicles_-_Expanded-Common-Match_Completion.
> >
> > This explains incremental completion:
> > http://www.emacswiki.org/emacs/Icicles_-_Icompletion
> >
> > You can cycle/toggle either of these during completion, to 
> > see the differences.  See the doc strings of
> > `icicle-expand-input-to-common-match' and
> > `icicle-incremental-completion'.
> 
> Ok now I'm confused.  I've read the docs, they seem clear enough.  I
> thought incremental completion means "when I type a character, the
> *Completions* buffer updates immediately to reflect what I just typed"

Yes.

> And I thought common-match expansion meant "when all the completions
> have common characters beyond what's already in the minibuffer, they're
> automatically added to the minibuffer".

That's right.  And highlighted in *Completions*.

> Which one affects what's in the minibuffer?

`i-e-i-t-c-m' affects expansion of your input to the common match, if there is
one.

`i-i-c' affects whether and when *Completions* gets updated incrementally as you
type/edit.

> I could have sworn that's the common-match expansion,

It is.  You have understood the doc correctly.

> which I have turned off.  And yet, somehow what I'm typing in the
> minibuffer ends up with extra characters that I didn't type,
> and ultimately there are 0 matches because I've got "foo"
> with an o that I typed, and an o that was added 
> automatically, but there are no completions starting with 'foo'.

Sounds like a bug.  Please report it using `M-x icicle-send-bug-report'.
Try to give a recipe starting from `emacs -Q', mentioning your Emacs version.

But I just uploaded a fix for a bug which made `i-e-i-t-c-m' = 0 and 1 not work
right.  You might try that first, to see if it also fixes the problem you see.
You will need to download the latest icicles-fn.el:
http://www.emacswiki.org/emacs-en/download/icicles-fn.el

Sorry for your trouble.




  reply	other threads:[~2012-12-21 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 22:30 migrating from ido to icicles Drew Adams
2012-12-21  3:53 ` Jeff Weiss
2012-12-21 18:31   ` Drew Adams [this message]
2012-12-21 14:41 ` Jeff Weiss
2012-12-21 18:32   ` Drew Adams
2012-12-21 19:06     ` Jeff Weiss
2012-12-21 19:12       ` Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2012-12-19 19:11 jeffrey.m.weiss
2012-12-19 22:41 ` Drew Adams
2012-12-20 14:51   ` Jeff Weiss
2012-12-20 15:45     ` Drew Adams
2012-12-20 21:11       ` Jeff Weiss
     [not found] ` <mailman.15718.1355956885.855.help-gnu-emacs@gnu.org>
2012-12-20 12:31   ` Michael Heerdegen
2012-12-21  0:10     ` Drew Adams

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=B46C946BE52E425FB38FE9020746141C@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jeffrey.m.weiss@gmail.com \
    --cc=jweiss@redhat.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).