From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 69141@debbugs.gnu.org
Subject: bug#69141: [PATCH] Allow attaching files at point using 'gnus-dired-attach'
Date: Mon, 26 Feb 2024 10:15:30 +0000 [thread overview]
Message-ID: <875xybcz0d.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmnVvqBkhDCSORiHd_vPxvV2jgn5pecEmMJb_8PPNS6ttQ@mail.gmail.com> (Stefan Kangas's message of "Mon, 19 Feb 2024 15:33:45 -0500")
Stefan Kangas <stefankangas@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Do you think it would be OK to modify the default behaviour? If so, I
>> guess we should mention it in NEWS and point out how to restore the old
>> behaviour, for anyone would really needs it.
>
> I'm not sure it's worth changing it, because other attach commands in
> message-mode adds attachments in place, which kind of makes sense if you
> are dealing with in-line images. So I can realistically see users
> wanting either behaviour, and providing an option does that.
>
> WDYT?
The argument for changing it would precisely be to be more consistent
with what other commands do. The argument against it, as usual, would
be that it could conceivably break someones workflow.
--
Philip Kaludercic on peregrine
prev parent reply other threads:[~2024-02-26 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 11:12 bug#69141: [PATCH] Allow attaching files at point using 'gnus-dired-attach' Philip Kaludercic
2024-02-17 18:10 ` Eric Abrahamsen
2024-02-19 15:54 ` Philip Kaludercic
2024-02-19 16:21 ` Eric Abrahamsen
2024-02-19 19:02 ` Philip Kaludercic
2024-02-19 16:52 ` Eli Zaretskii
2024-02-19 19:00 ` Stefan Kangas
2024-02-19 19:02 ` Philip Kaludercic
2024-02-19 20:33 ` Stefan Kangas
2024-02-20 2:22 ` Visuwesh
2024-02-26 10:15 ` Philip Kaludercic [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=875xybcz0d.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=69141@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=stefankangas@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).