unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 69691@debbugs.gnu.org
Subject: bug#69691: 30.0.50; vc-pull buffer doesn't fontify links after refresh
Date: Sun, 10 Mar 2024 08:26:30 +0200	[thread overview]
Message-ID: <86msr6wqjt.fsf@gnu.org> (raw)
In-Reply-To: <s0dwmqaiwsq.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)

> Date: Sun, 10 Mar 2024 11:35:17 +0800
> From:  Po Lu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> New VCS output inserted after the compilation buffer created by a
> `vc-pull' command is refreshed (by selecting "refresh" from tool bar,
> 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.

Please provide a recipe for reproducing the problem starting from
"emacs -Q".  The above description is too terse and lacks crucial
details, like the stuff you see in the buffer, which parts are not
fontified and/or not clickable, etc.

Thanks.





  reply	other threads:[~2024-03-10  6:26 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 [this message]
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
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

  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=86msr6wqjt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69691@debbugs.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 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).