RE: [Ilisp-help] RE: Re: Using Emacs as a Lisp IDE

"Clementson, Bill" <[email protected]> Wed, 16 Jul 2003 09:04:40 -0600
Newsgroups gmane.lisp.ilisp.devel,gmane.lisp.ilisp.general
Message-ID <[email protected]>
From: Bob Rogers on Tuesday, July 15, 2003 9:12 PM
[snip]=20
> Although I use C-h m frequently, I still find lists of=20
> command bindings useful.  Recall that C-h m lists bindings=20
> alphabetically, with it's own rules for how to alphabetize=20
> prefix combinations, so a cheat sheet that is topically=20
> organized does have some value-added of its own.

True, however, with the new fsf keybindings, the commands ARE grouped
topically because of the 3-key keybindings (e.g. -- all the compile
commands are grouped under "C-c C-k ...", all the eval commands are
grouped under "C-c C-j ...", etc.
=20
[snip]
> I would like to suggest a topically-organized index of=20
> commands with key bindings.  What I liked about the Web page=20
> is that it showed all three sets of bindings -- original, old=20
> FSF, and your proposal -- in parallel. We'd only need two now=20
> -- "standard" and "traditional" -- but I think it's still a=20
> good idea to document both, especially since switching=20
> bindings modes in order to do "C-h m" is onerous.

Why is (setq ilisp-*use-fsf-compliant-keybindings* t), "M-x run-ilisp",
"C-h m" so onerous?

So, I'm not really convinced, but let's consider what the "optimal" way
of presenting such a listing would be and then decide if the value of
such a listing would be worth the effort to create it. At the moment,
the "legacy" bindings (but not the "fsf" bindings) are displayed next to
the individual commands in the "ILISP Commands" section of the manual. I
can think of three reasonable alternatives if we did decide to provide
keybinding detail in the documentation:

1. Remove the "legacy" bindings from the "ILISP Commands" section so
that the section contains only command descriptions. Then, add a table
to the "Keybindings" section of the manual showing a list of the ILISP
commands (grouped topically) with the corresponding "legacy" and "fsf"
bindings.

2. Leave the "legacy" binding detail in the "ILISP Commands" section but
add the "fsf" binding detail in there too.

3. Remove the "legacy" bindings from the "ILISP Commands" section so
that the section contains only command descriptions. Then, create 2
separate reference cards (similar to ilisp-refcard.tex but with all
commands) showing the ILISP commands and their keybindings.

All of these would take a few hours work and I'm not convinced that they
would provide substantially more value than just the "C-h m" listings.=20

Thoughts?

--
Bill Clementson


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0