From: Christian Tietze <me@christiantietze.de>
To: Lars Ingebrigtsen <larsi@gnus.org>, Robert Pluim <rpluim@gmail.com>
Cc: , 49208@debbugs.gnu.org
Subject: bug#49208: 28.0.50; project-find-regexp's xref-mode result buffer is not editable
Date: Thu, 24 Jun 2021 21:40:51 +0200 [thread overview]
Message-ID: <m1tuln9hks.fsf@christiantietze.de> (raw)
In-Reply-To: <87zgvffbg8.fsf@gnus.org>
Sorry, I thought these were staples of the Emacs landscape with
`wdired' being the ancestor of them all. You know that one? If no,
check it out for in-place file renaming in dired listings, including
rectangle-mode (or multiple cursors, if one prefers) changes.
Not sure how to best implement this, and larger elisp code bases
are hard to follow for me still; it sounds like a problem I'd tackle
by storing the original, making an editable copy, then diffing the
buffers on commit ([C-c C-c]) and apply the diffs per reference. In
dired, apply line changes as renames; in wgrep, apply per-file diffs.
Xref has file references for each item already, so I can imagine
applying the changes might not be that difficult, since [r] offers
replacement among all findings in a similar way, but only
mass-replacements, not amendmends and free-form editing.
This is my first contribution to the mailing list -- should I
rephrase/add anything to my original email to clarify, or is there
anything else I can do to help with filing this?
I guess a better title would be:
"Make project-find-refexp's xref-mode result buffer editable" instead
of the complaint-like way I phrased it to make it sound like a 'bug'.
Happy to follow along and help where I can!
-- Christian
next prev parent reply other threads:[~2021-06-24 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 13:49 bug#49208: 28.0.50; project-find-regexp's xref-mode result buffer is not editable Christian Tietze
2021-06-24 16:04 ` Lars Ingebrigtsen
2021-06-24 16:29 ` Robert Pluim
2021-06-24 16:56 ` Lars Ingebrigtsen
2021-06-24 19:40 ` Christian Tietze [this message]
2021-06-24 20:52 ` Juri Linkov
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=m1tuln9hks.fsf@christiantietze.de \
--to=me@christiantietze.de \
--cc=49208@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@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 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.