From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 47128@debbugs.gnu.org
Subject: bug#47128: 28.0.50; Be more helpful regarding message-syntax-checks
Date: Mon, 12 Apr 2021 09:46:19 -0700 [thread overview]
Message-ID: <87im4rsb6s.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k0qasmpr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 13 Mar 2021 14:38:56 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> The `message-syntax-checks' option doesn't have a very useful
> customization :type, and the manual section explaining what it does
> isn't in the most obvious spot. This patch moves the manual explanation
> from "News Headers" to the more general "Message Headers" section, as
> the option governs both mail and news. It also expands the :type
> definition to explicitly list all the possible options.
>
> The defcustom originally had two comments on it, one saying "Guess this
> one shouldn't be easy to customize...", and another on the :type line
> saying "improve this". That seems a bit contradictory.
>
> Anyway, I don't see the point of actually obfuscating the use of this
> option; this patch should make it a little more discoverable.
>
> What would be even better is to obsolete this in favor of a new
> `message-disabled-syntax-checks' option that was simply a plain list of
> symbols.
I feel like this is fairly uncontroversial -- does anyone have any
objections? I may just go ahead and push, otherwise. (I've since tweaked
the patch so that `message-syntax-checks' belongs to the
'message-headers group, in line with the other changes.)
next prev parent reply other threads:[~2021-04-12 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 22:38 bug#47128: 28.0.50; Be more helpful regarding message-syntax-checks Eric Abrahamsen
2021-04-12 16:46 ` Eric Abrahamsen [this message]
2021-04-13 7:47 ` Lars Ingebrigtsen
2021-04-13 15:46 ` Eric Abrahamsen
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=87im4rsb6s.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=47128@debbugs.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).