From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: removing extraneous information in repeat-complex-command
Date: Sat, 07 Jan 2023 23:02:39 +0100 [thread overview]
Message-ID: <87eds69f5s.fsf@dataswamp.org> (raw)
In-Reply-To: CAJr-wt0KikORORSM4om2zQz--cpTJWnSicJZL66bBkFn2UJ3FQ@mail.gmail.com
Frederick Bartlett wrote:
> Is there a simple way to resimplify complex commands? [...]
> Alternatively, if this can only be solved via a macro, I'd
> appreciate a clue or two. While I have written a few in the
> past, I'm not sure how to approach this.
Well, what are you trying to do exactly?
(eval (car command-history))
?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-01-07 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 18:59 removing extraneous information in repeat-complex-command Frederick Bartlett
2023-01-07 22:02 ` Emanuel Berg [this message]
2023-01-07 22:14 ` [External] : " Drew Adams
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=87eds69f5s.fsf@dataswamp.org \
--to=incal@dataswamp.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).