From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: laszlomail@protonmail.com, 52815@debbugs.gnu.org
Subject: bug#52815: Editable grep buffer
Date: Thu, 30 Dec 2021 23:24:35 -0500 [thread overview]
Message-ID: <E1n39T1-0004gn-6t@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmmxxTvfJMvjovs4Wv67F8PsZYFLE8AOhgRuocSLMzp99Q@mail.gmail.com> (message from Stefan Kangas on Wed, 29 Dec 2021 12:51:59 -0800)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > Actually editing the text in the Grep mode buffer is a nuisance, since
> > many self-inserting characters do unusual things. But that is a
> > different issue.
> This is the issue we are discussing here, as that is what wgrep does.
> It works well in practice, analogous to how wdired works but it edits
> multiple files. You enter wgrep-mode from grep-mode to make your edits
> with `C-x C-q', edit the text of the buffer and then type `C-x C-s' to
> save your changes to the relevant files.
That makes sense. The original message didn't describe it clearly.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2021-12-31 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 10:02 bug#52815: Editable grep buffer ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-27 15:09 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-29 0:29 ` Stefan Kangas
2021-12-29 6:31 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-29 16:01 ` Richard Stallman
2021-12-29 20:51 ` Stefan Kangas
2021-12-31 4:24 ` Richard Stallman [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=E1n39T1-0004gn-6t@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=52815@debbugs.gnu.org \
--cc=laszlomail@protonmail.com \
--cc=stefan@marxist.se \
/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.