From: Michael Heerdegen <michael_heerdegen@web.de>
To: Arthur Miller <arthur.miller@live.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Eval keymapp in a macros
Date: Fri, 06 Aug 2021 05:18:27 +0200 [thread overview]
Message-ID: <877dgzp8fw.fsf@web.de> (raw)
In-Reply-To: <AM9PR09MB4977A8C952B6DCFED4BB252696F29@AM9PR09MB4977.eurprd09.prod.outlook.com> (Arthur Miller's message of "Thu, 05 Aug 2021 08:15:28 +0200")
Arthur Miller <arthur.miller@live.com> writes:
> Yes, I agree, and it is confusing to other people to see stuff without
> quotes and dashes, as I saw in that mentioned reddit thread.
The problem I mean is that when you later want to search where you bound
command XY, you can't just grep for define-key.*XY or so, it's harder to
find stuff afterwards. So while your file gets marginally smaller it
also gets harder to navigate. Seems most people come to the conclusion,
over the years, that such abbreviations are not worth it. Happened to
me as well. If you do this kind of thing in a lot of places you risk a
big mess in your init file.
Michael.
prev parent reply other threads:[~2021-08-06 3:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 12:16 Eval keymapp in a macros Arthur Miller
2021-08-02 20:33 ` Michael Heerdegen
2021-08-02 20:53 ` [External] : " Drew Adams
2021-08-03 21:20 ` Arthur Miller
2021-08-04 0:18 ` Michael Heerdegen
2021-08-04 10:52 ` Arthur Miller
2021-08-04 23:56 ` Michael Heerdegen
2021-08-05 6:03 ` Arthur Miller
2021-08-06 3:54 ` Michael Heerdegen
2021-08-12 20:28 ` Arthur Miller
2021-08-04 4:54 ` Yuri Khan
2021-08-04 9:38 ` Arthur Miller
2021-08-04 15:37 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-05 6:12 ` Arthur Miller
2021-08-05 13:53 ` Stefan Monnier
2021-08-05 16:04 ` Arthur Miller
2021-08-05 16:34 ` Stefan Monnier
2021-08-06 4:17 ` Michael Heerdegen
2021-08-12 20:21 ` Arthur Miller
2021-08-05 0:03 ` Michael Heerdegen
2021-08-05 6:15 ` Arthur Miller
2021-08-06 3:18 ` Michael Heerdegen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dgzp8fw.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=arthur.miller@live.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.