From: Michael Heerdegen <michael_heerdegen@web.de>
To: Glenn Morris <rgm@gnu.org>
Cc: larsi@gnus.org, Ignacio Casso <ignaciocasso@hotmail.com>,
54399@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#54399: 27.2; Problems with (let ((custom-variable ...)) (autoload-function ...))
Date: Wed, 13 Apr 2022 05:43:49 +0200 [thread overview]
Message-ID: <87y209ejgq.fsf@web.de> (raw)
In-Reply-To: <8ee21zmrp.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 12 Apr 2022 23:26:50 -0400")
Glenn Morris <rgm@gnu.org> writes:
> > If your mail client allows it you can also read the newsgroup
> > gnu.emacs.bug (or gmane.emacs.bug), look for your message and answer per
> > mail "from there".
>
> Please don't post via usenet for bug reporting or commenting on issues.
> It creates various technical problems.
> Please forget that gnu.emacs.bug exists.
Thanks for the important hint. That's why I said "answer _per_mail_".
But with the right setup one can have a convenient workflow. I more or
less never post via News, but reading the bug threads as Newsgroup is
just too convenient, for reasons like this one (how to respond to the
correct subthread).
If you can't ensure that you never post via usenet, then it's better to
forget gnu.emacs.bug, agreed.
Michael.
next prev parent reply other threads:[~2022-04-13 3:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 11:50 bug#54399: 27.2; Problems with (let ((custom-variable ...)) (autoload-function ...)) Ignacio Casso
2022-03-17 11:23 ` Lars Ingebrigtsen
2022-03-18 0:22 ` Michael Heerdegen
2022-03-18 1:02 ` Michael Heerdegen
2022-03-18 9:32 ` Lars Ingebrigtsen
2022-03-18 9:38 ` Ignacio Casso
2022-04-12 13:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 13:23 ` Ignacio Casso
2022-04-12 13:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 9:13 ` Ignacio Casso
2022-04-12 11:38 ` Eli Zaretskii
2022-04-12 12:16 ` Ignacio Casso
2022-04-12 13:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 14:27 ` Ignacio Casso
2022-04-12 15:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 15:27 ` Ignacio Casso
2022-04-12 22:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-13 15:26 ` Ignacio Casso
2022-04-13 0:24 ` Michael Heerdegen
2022-04-13 3:26 ` Glenn Morris
2022-04-13 3:43 ` Michael Heerdegen [this message]
2022-04-12 15:24 ` Eli Zaretskii
2022-04-13 17:22 ` Ignacio Casso
2022-04-12 13:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 13:51 ` Ignacio Casso
2022-04-12 15:22 ` Eli Zaretskii
2022-04-13 0:06 ` Michael Heerdegen
2022-04-13 12:08 ` Ignacio Casso
2022-05-12 2:32 ` Lars Ingebrigtsen
2022-05-12 6:58 ` Ignacio Casso
2022-05-12 7:34 ` Eli Zaretskii
2022-05-12 8:14 ` Ignacio Casso
2022-05-12 8:36 ` Eli Zaretskii
2022-05-12 8:41 ` Ignacio Casso
2022-05-12 9:40 ` Eli Zaretskii
2022-05-12 11:49 ` Lars Ingebrigtsen
2022-06-09 15:02 ` Lars Ingebrigtsen
2022-06-09 21:19 ` Ignacio Casso
2022-06-10 9:13 ` Lars Ingebrigtsen
2022-06-10 14:01 ` dick
2022-06-11 10:51 ` Lars Ingebrigtsen
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=87y209ejgq.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=54399@debbugs.gnu.org \
--cc=ignaciocasso@hotmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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 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).