From: Jeremy Bryant via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, 67313-done@debbugs.gnu.org
Cc: 67313@debbugs.gnu.org
Subject: bug#67313: [PATCH] New command write-file-no-switch
Date: Fri, 01 Dec 2023 23:11:10 +0000 [thread overview]
Message-ID: <875y1ha54b.fsf@jeremybryant.net> (raw)
In-Reply-To: <83ttp29v1g.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Jeremy Bryant <jb@jeremybryant.net>
>> Cc: 67313@debbugs.gnu.org
>> Date: Thu, 30 Nov 2023 23:18:59 +0000
>>
>> > Thanks. As stated above, I'm not sure I agree we need a new command.
>> > write-region already exists, as a command, and I personally use it
>> > quite a lot in these cases.
>> >
>> > Does anyone else think we need an additional command for saving a
>> > buffer to a different file?
>>
>>
>> Eli, another way is also to clarify the manual to explain write-region.
>> Second patch attached for consideration. This may help users.
>
> Thanks, that's a no-brainer. Installed on the emacs-29 branch (after
> fixing some markup and punctuation issues).
>
> Should we close this bug now?
Yes, closing bug as fixed by this addition to the manual.
(noted usage of @w)
prev parent reply other threads:[~2023-12-01 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 23:33 bug#67313: [PATCH] New command write-file-no-switch Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-21 11:26 ` Eli Zaretskii
2023-11-21 22:52 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-24 8:04 ` Eli Zaretskii
2023-11-30 23:18 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-01 8:38 ` Eli Zaretskii
2023-12-01 23:11 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=875y1ha54b.fsf@jeremybryant.net \
--to=bug-gnu-emacs@gnu.org \
--cc=67313-done@debbugs.gnu.org \
--cc=67313@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jb@jeremybryant.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.