From: Thien-Thi Nguyen <ttn@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Learning "my emacs" from the start
Date: Sun, 20 Apr 2014 12:39:50 +0200 [thread overview]
Message-ID: <87mwfg5lop.fsf@zigzag.favinet> (raw)
In-Reply-To: <83lhv0fmrk.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Apr 2014 11:06:23 +0300")
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
() Eli Zaretskii <eliz@gnu.org>
() Sun, 20 Apr 2014 11:06:23 +0300
> leave many hundreds of commands alone, especially for the more
> obscure and complex, less frequently used modes and packages not
> worth taking the time to customize.
Alas, there's no practical way of discovering which is which. If
you intended to go over all of the commands provided by Emacs, then
that's impractical, as there are too many of them, even if you
restrict yourself to the default configuration. IOW, the way you
intend to take is much longer and less efficient than what was
suggested to you.
I agree OP's way is impractical and inefficient, but that doesn't mean
it is impossible or undesirable. It's no problem for people to scope
out the joint before joining the party; the door is always open and the
Software is (as always, thank GNU very much) Free. Too, some sidewalk
spectacle is its own reward, and keeps the puke out of the punchbowl...
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-04-20 10:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 20:10 Learning "my emacs" from the start (was: Generating a listing of all symbols) Hans BKK
2014-04-19 20:57 ` Emanuel Berg
2014-04-20 8:06 ` Eli Zaretskii
2014-04-20 10:39 ` Thien-Thi Nguyen [this message]
2014-04-20 11:04 ` Learning "my emacs" from the start Eli Zaretskii
2014-04-20 14:12 ` Thien-Thi Nguyen
2014-04-20 14:13 ` Eli Zaretskii
2014-04-22 8:47 ` Nicolas Richard
2014-04-22 16:40 ` Eli Zaretskii
2014-04-20 13:00 ` Florian v. Savigny
2014-04-20 13:29 ` Florian v. Savigny
2014-04-20 14:50 ` Thien-Thi Nguyen
2014-04-21 8:26 ` Florian v. Savigny
[not found] ` <mailman.19974.1398068777.10748.help-gnu-emacs@gnu.org>
2014-04-21 13:12 ` Hans BKK
[not found] ` <mailman.19908.1397981214.10748.help-gnu-emacs@gnu.org>
2014-04-20 13:23 ` Learning "my emacs" from the start (was: Generating a listing of all symbols) Rusi
2014-04-20 17:13 ` Bob Proulx
2014-04-20 18:51 ` Eli Zaretskii
[not found] ` <mailman.19947.1398019903.10748.help-gnu-emacs@gnu.org>
2014-04-21 14:37 ` Rusi
2014-04-21 19:01 ` Bob Proulx
2014-04-21 20:16 ` Robert Thorpe
2014-04-21 20:22 ` Robert Thorpe
2014-04-21 21:00 ` Eli Zaretskii
[not found] ` <mailman.20014.1398106904.10748.help-gnu-emacs@gnu.org>
2014-04-22 1:37 ` Rusi
2014-04-20 17:12 ` Hans BKK
2014-04-20 20:36 ` Robert Thorpe
2014-04-20 20:41 ` Emanuel Berg
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=87mwfg5lop.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--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).