unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Christian Tietze <me@christiantietze.de>
Cc: 49208@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
	Robert Pluim <rpluim@gmail.com>
Subject: bug#49208: 28.0.50; project-find-regexp's xref-mode result buffer is not editable
Date: Thu, 24 Jun 2021 23:52:37 +0300	[thread overview]
Message-ID: <871r8r3rze.fsf@mail.linkov.net> (raw)
In-Reply-To: <m1tuln9hks.fsf@christiantietze.de> (Christian Tietze's message of "Thu, 24 Jun 2021 21:40:51 +0200")

> 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.

I don't know the details of wgrep and occur-edit-mode,
but I guess that after adding an option to specify the
format of the xref output buffer (instead of the hard-coded
xref--insert-xrefs), choosing an option to use a grep-like
output format will allow wgrep to edit it, and choosing an option
to use an occur-like output format will allow occur-edit-mode
to edit it.





      reply	other threads:[~2021-06-24 20:52 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
2021-06-24 20:52         ` Juri Linkov [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=871r8r3rze.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=49208@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=me@christiantietze.de \
    --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 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).