From: "Drew Adams" <drew.adams@oracle.com>
To: "'Harry Putnam'" <reader@newsguy.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Can you recommand some good fonts for emacs22 ?
Date: Mon, 20 Jul 2009 11:08:17 -0700 [thread overview]
Message-ID: <3E28222C0EE14FC282100089B9CC1713@us.oracle.com> (raw)
In-Reply-To: <87ocrffjqz.fsf@newsguy.com>
> > That sounds correct, actually. The prefix for Icicles
> > commands and variables is `icicle-', not `icicles-'.
> > And SPC is self-inserting, by default - it does not
> > perform completion.
>
> I must have something set different than default here... <spc> does
> completion in all the modes I commonly use.
I meant in Icicle mode. In Icicle mode, SPC is self-inserting, at least by
default (i.e., if you change no keybindings). When you turn Icicle mode off
(e.g. via `icy-mode'), the vanilla Emacs behavior of SPC is restored.
> Yes, I see now where I used spc for completion in the initial command:
> M-x icic<spc> A tab does work there. I expected spc to work as it
> does in all other modes I use.
Not by default, but you can do that if you want. SPC is self-inserting in Icicle
mode, because there are lots of completions that contain space chars. Icicles
makes completion usable for lots of things that vanilla Emacs doesn't, and some
of them include space chars.
> Ok, its all starting to make sense now... sorry for bad mouthing your
> program without real effort testing.
>
> And thanks for the thorough walk thru on how to use the
> tools. Very helpful.
No problem. Once you learn the basic Icicles behavior, the rest follows. I can't
describe that basic behavior in the doc string of every command. (But the doc
string of `icicle-font' does describe how to act on individual candidates, and
it does say this:
"This is an Icicles command - see command `icicle-mode', and that leads you to
some of the basic behavior.
next prev parent reply other threads:[~2009-07-20 18:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1010.1245536389.2239.help-gnu-emacs@gnu.org>
2009-06-21 8:16 ` Can you recommand some good fonts for emacs22 ? Marc Tfardy
2009-06-21 9:33 ` Peter Breitfeld
2009-06-24 13:41 ` Marc Tfardy
2009-07-21 3:19 ` Harry Putnam
2009-06-21 15:29 ` Michael Ekstrand
2009-06-21 17:29 ` Thierry Volpiatto
2009-06-21 17:44 ` Drew Adams
2009-07-20 10:26 ` Harry Putnam
2009-07-20 10:56 ` Harry Putnam
2009-07-20 13:50 ` Drew Adams
2009-07-20 15:37 ` Harry Putnam
2009-07-20 18:08 ` Drew Adams [this message]
2009-07-20 10:30 ` Harry Putnam
2009-07-20 10:37 ` Harry Putnam
2009-07-20 10:52 ` Bernardo
2009-07-20 15:22 ` Harry Putnam
2009-07-20 11:34 ` Thierry Volpiatto
2009-07-20 15:32 ` Harry Putnam
2009-07-20 16:13 ` Thierry Volpiatto
2009-07-21 3:02 ` Harry Putnam
2009-07-21 5:05 ` Thierry Volpiatto
2009-07-21 15:45 ` Harry Putnam
2009-07-21 4:15 ` Drew Adams
[not found] ` <mailman.1032.1245605769.2239.help-gnu-emacs@gnu.org>
2009-07-15 11:36 ` David Combs
2009-07-15 12:15 ` Anselm Helbig
2009-07-15 12:43 ` Thierry Volpiatto
[not found] ` <mailman.2548.1247662203.2239.help-gnu-emacs@gnu.org>
2009-07-15 16:50 ` Ted Zlatanov
2009-07-15 19:26 ` Thierry Volpiatto
[not found] ` <mailman.2584.1247686398.2239.help-gnu-emacs@gnu.org>
2009-07-16 16:27 ` Ted Zlatanov
2009-06-20 11:37 waterloo
2009-06-20 23:04 ` Drew Adams
2009-06-21 9:49 ` Teemu Likonen
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=3E28222C0EE14FC282100089B9CC1713@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=reader@newsguy.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).