From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode + icicles, avoid key binding redefinitions?
Date: Thu, 23 Jan 2014 05:57:35 -0800 [thread overview]
Message-ID: <m21tzy7qcw.fsf@polytechnique.org> (raw)
In-Reply-To: <f7a93471-75d9-432e-b1b6-a1e7a9c4e8ba@default> (Drew Adams's message of "Wed, 22 Jan 2014 20:45:33 -0800 (PST)")
Hello Drew,
Drew Adams <drew.adams@oracle.com> writes:
> 1d. By default only. It is trivial to customize user option
> `icicle-top-level-keybindings', to bind `icicle-occur' to a
> different key or to give it no key binding at all.
>
> (And no, you do not need to fiddle with Lisp to do that - not
> even `define-key'. `M-x customize-option' is your friend -
> just get yourself a separate `custom-file', for sanity.)
>
> 1e. The same holds for `C-`', which Icicles binds by default
> to `icicle-search'. And it holds for any other top-level
> keys.
>
> If you think that Icicles is "clobbering" any key bindings
> that you prefer from another package (such as Org), it is
> simple to change keys (in Icicles anyway; dunno about Org).
> Icicles does not "clobber" any keys without your permission
> - just customize `icicle-top-level-keybindings'.
Thanks a lot for this suggestion. I'm just not used to the customize
system so I did not think of looking there.
I have an additional question: where does one ask for help about icicle?
I don't know how to make it work with bbdb, and searching online didn't
clarify things.
Thanks again,
Alan
next prev parent reply other threads:[~2014-01-23 14:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 4:45 org-mode + icicles, avoid key binding redefinitions? Drew Adams
2014-01-23 7:43 ` Bastien
2014-01-23 15:33 ` Drew Adams
2014-01-23 15:46 ` Bastien
2014-01-23 16:28 ` Drew Adams
2014-01-23 16:34 ` Bastien
2014-01-23 17:01 ` Drew Adams
2014-01-23 22:24 ` Bastien
2014-01-23 22:56 ` Drew Adams
2014-01-23 23:29 ` Thomas S. Dye
2014-01-24 8:39 ` Bastien
2014-01-25 7:34 ` Thomas S. Dye
2014-01-28 9:08 ` Bastien
2014-01-29 8:43 ` Sebastien Vauban
2014-01-29 9:39 ` Bastien
2014-01-29 10:35 ` Sebastien Vauban
2014-01-29 11:00 ` Bastien
2014-01-29 11:32 ` Sebastien Vauban
2014-01-29 17:34 ` Thomas S. Dye
2014-01-29 17:48 ` Bastien
2014-01-29 19:48 ` Thomas S. Dye
2014-01-29 20:11 ` Iannis Zannos
2014-01-30 0:39 ` Bastien
2014-01-29 11:44 ` Florian Beck
2014-01-29 13:16 ` Nick Dokos
2014-01-29 13:52 ` Bastien
2014-01-29 18:01 ` Achim Gratz
2014-01-29 20:06 ` Andreas Leha
2014-01-29 20:13 ` Iannis Zannos
2014-01-29 14:43 ` Florian Beck
2014-01-29 15:40 ` Bastien
2014-01-29 16:20 ` Nicolas Goaziou
2014-01-23 13:57 ` Alan Schmitt [this message]
2014-01-23 15:33 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2014-01-18 19:49 John Kitchin
2014-01-18 21:40 ` Alan Schmitt
2014-01-19 15:53 ` Bastien
2014-01-19 17:31 ` Memnon Anon
2014-01-19 20:56 ` John Kitchin
2014-01-20 2:34 ` Memnon Anon
2014-01-20 23:12 ` Alan Schmitt
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21tzy7qcw.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=drew.adams@oracle.com \
--cc=emacs-orgmode@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/org-mode.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).