From: Lorenzo Isella <lorenzo.isella@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Trouble with Command for Eshell
Date: Tue, 23 Jul 2019 16:35:27 +0200 [thread overview]
Message-ID: <20190723143527.rojyxwslg4oxn4z5@chicca2> (raw)
Dear All,
I have recently updated my system (Debian) to the new stable and I am experiencing a few minor glitches.
I have in my .emacs file the following
(fset 'auxiliary
(lambda (&optional arg) "Keyboard macro." (interactive "p") (kmacro-exec-ring-item (quote ([21 escape 120 101 115 104 101 108 108 return escape 120 114 101 110 97 109 right right return 97 117 120 105 108 105 97 114 121 return] 0 "%d")) arg)))
Which means that the combination
Alt+x auxiliary
opens a second emacs shell and names it auxiliary.
However, right now, the same command opens something like >20 emacs shells...
Does anyone know how I should fix this?
I am no emacs guru and this is an (ugly) macro I recorded ages ago, but which has served me well until now.
Cheers
Lorenzo
next reply other threads:[~2019-07-23 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 14:35 Lorenzo Isella [this message]
2019-07-23 16:48 ` Trouble with Command for Eshell Stefan Monnier
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=20190723143527.rojyxwslg4oxn4z5@chicca2 \
--to=lorenzo.isella@gmail.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.
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).