From: Juri Linkov <juri@linkov.net>
To: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
Cc: 47690-done@debbugs.gnu.org
Subject: bug#47690: 28.0.50; repeat-mode: Introduce a defmacro for chaining commands ???
Date: Mon, 12 Apr 2021 19:13:45 +0300 [thread overview]
Message-ID: <87blaj1qwy.fsf@mail.linkov.net> (raw)
In-Reply-To: <TY2PR0101MB3693E16111BF41316E7B23D2DA729@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (Ramesh Nedunchezian's message of "Sat, 10 Apr 2021 17:58:58 +0530")
> Think of this email not as a bug, but as a note ... So, feel free to
> close it after digesting the contents.
Thanks, your notes will be saved for posterity, although I see
nothing actionable here, repeat-mode is not like a hydra package.
prev parent reply other threads:[~2021-04-12 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 12:28 bug#47690: 28.0.50; repeat-mode: Introduce a defmacro for chaining commands ??? Ramesh Nedunchezian
2021-04-12 16:13 ` Juri Linkov [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
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=87blaj1qwy.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=47690-done@debbugs.gnu.org \
--cc=rameshnedunchezian@outlook.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).