unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 66450-done@debbugs.gnu.org
Subject: bug#66450: 29.1; Debbugs/Gnus sometimes corrupt git formatted patches
Date: Sun, 10 Mar 2024 08:12:34 -0700	[thread overview]
Message-ID: <87zfv65del.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87mswfafd6.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 18 Oct 2023 12:40:37 -0700")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi,
>>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>> [...]
>>
>>>> If we worry about backward compatibility, perhaps we could add a
>>>> defcustom variable that'd be named
>>>> e.g. 'gnus-always-process-raw-message' or similar, that'd do what its
>>>> name says (e.g. when using 'pipe' or save-article, it'd process the raw
>>>> message).  Eventually, it could be made the default behavior, if it has
>>>> enough support.
>>>>
>>>> I could try implementing that, if it seems a good idea?
>>>
>>> I guess I think a whole option just for this would be overkill,
>>> particularly since it's only the pipe command that even offers the
>>> possibility of toggling raw/treated. I suppose we could float a query on
>>> gnus.general and see if anyone has a preference (I'd be interested in
>>> seeing how many people are actually aware of the symbolic prefix), and
>>> maybe call that good enough as a user survey.
>>
>> Maybe we can try that; the only Gnus mailing list I can find is
>> info-gnus-english; is there a more suitable one?
>
> I've already asked! It's on the emacs.gnus.general newsgroup, which used
> to have an HTML archive available on the web, but I guess doesn't
> anymore. The responses haven't been flooding in, but so far all in favor
> of changing the default.

We ended up not getting much in the way of response, and I'm kind of
reluctant to mess with things here. The thing that would probably make
most sense is allowing all the article savers to accept a "r" symbolic
argument to control raw-or-not, then default the pipe command to raw.
Otherwise this is the only command that takes a special modifier to use
the raw article and then... we default to raw. It doesn't quite make
sense!

I'm going to close this bug report, but Maxim if you feel very strongly
about this please re-open.

Thanks,
Eric





  parent reply	other threads:[~2024-03-10 15:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 18:29 bug#66450: 29.1; Debbugs/Gnus sometimes corrupt git formatted patches Maxim Cournoyer
2023-10-11 20:37 ` Eric Abrahamsen
2023-10-14 15:22   ` Maxim Cournoyer
2023-10-14 15:35     ` Maxim Cournoyer
2023-10-14 16:43     ` Eric Abrahamsen
2023-10-12 16:52 ` Michael Albinus
2023-10-12 22:04   ` Eric Abrahamsen
2023-10-13  7:01     ` Michael Albinus
2023-10-13 16:53       ` Eric Abrahamsen
2023-10-14 14:41         ` Michael Albinus
2023-10-14 16:40           ` Eric Abrahamsen
2023-10-16 14:59           ` Maxim Cournoyer
2023-10-17  7:03             ` Michael Albinus
2023-10-17 14:06               ` Eric Abrahamsen
2023-10-17 15:19                 ` Maxim Cournoyer
2023-10-17 16:41                   ` Eric Abrahamsen
2023-10-18 18:50                     ` Maxim Cournoyer
2023-10-18 19:40                       ` Eric Abrahamsen
2023-10-19  1:01                         ` Maxim Cournoyer
2023-10-19  2:50                           ` Eric Abrahamsen
2023-10-19  3:38                             ` Maxim Cournoyer
2023-10-19  6:26                         ` Visuwesh
2024-03-10 15:12                         ` Eric Abrahamsen [this message]
2023-10-19  1:53               ` Maxim Cournoyer
2023-10-19  7:05                 ` Michael Albinus
2023-10-14 20:27         ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]         ` <875y390x1s.fsf@>
2023-10-15  1:13           ` 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=87zfv65del.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=66450-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.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).