unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Hadron" <hadronquark@googlemail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: mthesaur v synonyms
Date: Thu, 9 Aug 2007 11:02:02 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGEJODOAA.drew.adams@oracle.com> (raw)
In-Reply-To: <cobqdgr6we.fsf@news.ubuntu.home>

> > at point, into the minibuffer as your input. Edit it if you like, before
> > hitting RET.
> >
> > If you also use Icicles, and you want the default value to _always_ be
> > inserted in the minibuffer as the initial input, then customize
> > `icicle-init-value-flag' to `insert'. I personally prefer that
> > behavior, but I think most people do not.
>
> Any command which replies on word-at-point should default it IMO.

Not sure what you mean.

> I have now got icicles ( cant say I like it at first attempt -
> there's a lot there :)) and set the flag as above and its much
> better. Although if something is pre-selected then typing should
> erase it, not append to it. That would be a nice fix.

Use `delete-selection-mode' to type over selected text (region).

To automatically have the initial value be preselected in the minibuffer,
use `preselect-start' or `preselect-end' as the value of
`icicle-init-value-flag', depending on where you want the cursor to be.

I use `insert' as the value, because I don't want the initial input
preselected. I generally edit it only slightly - I don't want to replace it
entirely.

> Do you know if I can stop f5 being bound by icicles by normal
> customization?

(define-key icicle-mode-map [f5] 'whatever-you-want)

Put that on `icicle-mode-hook' if you want.

Or, if you also do not want other top-level commands rebound by Icicles,
customize option `icicle-bind-top-level-commands-flag' to nil.

HTH

  reply	other threads:[~2007-08-09 18:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4579.1186674061.32220.help-gnu-emacs@gnu.org>
2007-08-09 16:48 ` mthesaur v synonyms Hadron
2007-08-09 18:02   ` Drew Adams [this message]
     [not found] <mailman.4628.1186771826.32220.help-gnu-emacs@gnu.org>
2007-08-11 11:34 ` Hadron
2007-08-11 14:16   ` Drew Adams
2007-08-11 14:24     ` Hadron
2007-08-11 14:34       ` Drew Adams
2007-08-11 14:28     ` Drew Adams
     [not found] <mailman.4626.1186765860.32220.help-gnu-emacs@gnu.org>
2007-08-10 17:33 ` Hadron
2007-08-10 18:50   ` Drew Adams
     [not found] <mailman.4617.1186757453.32220.help-gnu-emacs@gnu.org>
2007-08-10 15:51 ` Hadron
2007-08-10 16:36   ` Hadron
2007-08-10 17:10   ` Drew Adams
     [not found] <mailman.4587.1186682548.32220.help-gnu-emacs@gnu.org>
2007-08-10 11:45 ` Hadron
2007-08-10 12:02   ` Hadron
2007-08-10 14:41     ` Drew Adams
2007-08-10 14:49   ` Drew Adams
2007-08-10 14:26 ` Hadron
2007-08-10 15:34   ` Drew Adams
2007-08-09 12:26 Hadron
2007-08-09 15:38 ` 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=DNEMKBNJBGPAOPIJOOICGEJODOAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=hadronquark@googlemail.com \
    --cc=help-gnu-emacs@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.
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).