From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 69691@debbugs.gnu.org
Subject: bug#69691: 30.0.50; vc-pull buffer doesn't fontify links after refresh
Date: Fri, 15 Mar 2024 14:10:39 +0200 [thread overview]
Message-ID: <5b4d293f-ae32-45e0-91f2-50ce82882508@gutov.dev> (raw)
In-Reply-To: <86ttl79asu.fsf@gnu.org>
On 15/03/2024 10:08, Eli Zaretskii wrote:
>> Date: Fri, 15 Mar 2024 04:06:23 +0200
>> From: Dmitry Gutov<dmitry@gutov.dev>
>>
>>> for instance) is not fontified as such but as ordinary compiler output,
>>> and file names inside are not clickable. This is a bug, since no
>>> compelling reason exists to treat VCS commands as compilers once they
>>> are executed a second time.
>> I guess some specific provision for restoring more of the variables
>> after "recompile" could be made inside vc-compilation-mode's definition.
>>
>> Maybe it'll have to go as far as defining a separate major mode and its
>> own "recompile" command with a dedicated binding, since it doesn't seem
>> like 'M-x recompile' runs anything generic that would help us here.
> Maybe just customize revert-buffer-function in vc-compilation-mode?
'M-x recompile' doesn't call it.
next prev parent reply other threads:[~2024-03-15 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s0dwmqaiwsq.fsf.ref@yahoo.com>
2024-03-10 3:35 ` bug#69691: 30.0.50; vc-pull buffer doesn't fontify links after refresh Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-10 6:26 ` Eli Zaretskii
2024-03-10 6:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 2:06 ` Dmitry Gutov
2024-03-15 2:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 3:00 ` Dmitry Gutov
2024-03-15 8:08 ` Eli Zaretskii
2024-03-15 12:10 ` Dmitry Gutov [this message]
2024-03-15 12:41 ` Eli Zaretskii
2024-03-15 12:59 ` Dmitry Gutov
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=5b4d293f-ae32-45e0-91f2-50ce82882508@gutov.dev \
--to=dmitry@gutov.dev \
--cc=69691@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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.