From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Garreau\, Alexandre" <galex-713@galex-713.eu>
Cc: ding@gnus.org
Subject: Re: There’s no `fill-paragraph' on headers before inserting and sending
Date: Sat, 22 Jun 2019 12:16:43 +0200 [thread overview]
Message-ID: <m3wohdj56c.fsf@gnus.org> (raw)
In-Reply-To: <874ld3aby1.fsf@portable.galex-713.eu> (Alexandre Garreau's message of "Tue, 30 Oct 2018 12:52:38 +0100")
"Garreau, Alexandre" <galex-713@galex-713.eu> writes:
> In my posting styles I set the “User-Agent” header, to a value longer
> than 78 lines (RFC-“SHOULD”-standard max value for `fill-column' of
> headers), because I put “(emacs-version)” in there (so to provide more
> precise informations).
I think it should be possible for users to insert "too-long" header
lines -- that is, I don't think generally auto-filling all non-generated
header lines would be appreciated by all. But, yes, the default should
be to fill lines like User-Agent...
> But it seems that neither after inserting, neither before sending, this
> line is automatically filled: so it’s up to the user to guess their
> headers value should be short or pre-filled correctly. To me this seems
> an issue, but as I’m not sure and I’m not anymore sure of the correct
> way to report a bug (`gnus-bug' doesn’t appear to send to bug-gnu-emacs,
> to automatically assign to “emacs” package and doesn’t embed as much
> informations as it should, or as `report-emacs-bug' does) I’d like to
> have your opinions first.
Just use M-x report-emacs-bug.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-06-22 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 11:52 Garreau, Alexandre
2019-06-22 10:16 ` Lars Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wohdj56c.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=galex-713@galex-713.eu \
/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 NNTP newsgroup(s).