From: Joel Reicher <joel.reicher@gmail.com>
To: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Cc: Heime <heimeborgia@protonmail.com>
Subject: Re: Structuring a list to run sequence of commands
Date: Sun, 22 Dec 2024 23:38:21 +1100 [thread overview]
Message-ID: <86jzbrj3k2.fsf@gmail.com> (raw)
In-Reply-To: <CmnqcpUkjiRESoIvrQLWCRBiQXquUWUvYsfFwMXX3bd3cFZgzUmvOZhe2WsCeN9wFYP146cInq8OskadVOhMBAtDTUYG9jNyvUY0PER793s=@protonmail.com> (Heime via Users list for the's message of "Mon, 25 Nov 2024 20:37:40 +0000")
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
> Have been hoping to grouping a sequence of commands and execute
> each one.
Isn't this just what progn does?
Regards,
- Joel
next prev parent reply other threads:[~2024-12-22 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 20:37 Structuring a list to run sequence of commands Heime via Users list for the GNU Emacs text editor
2024-12-22 12:38 ` Joel Reicher [this message]
2024-12-23 5:47 ` Jean Louis
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=86jzbrj3k2.fsf@gmail.com \
--to=joel.reicher@gmail.com \
--cc=heimeborgia@protonmail.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).