From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51691@debbugs.gnu.org
Subject: bug#51691: 28.0.60; bug-reference-mode conflicts with rainbow-mode
Date: Tue, 9 Nov 2021 04:29:03 +0000 [thread overview]
Message-ID: <CAKDRQS6c0YxvtV9eSdki+ianGXY=RRcGD_00zT9=5F82MR7UvA@mail.gmail.com> (raw)
In-Reply-To: <87k0hirmhr.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
You have to put the file in a git repo, and have pushed it to an upstream
GitHub URL. Bug reference mode will then pick the github forge link for the
second value, which matches the GitHub issue number regex.
On Tue, 9 Nov 2021 at 4:17 am Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Jimmy Yuen Ho Wong <wyuenho@gmail.com> writes:
>
> > 1. emacs -q
> > 2. Visit an elisp file in a git repo that has a hex color value in a
> > string parameter followed by a
> > hash, e.g. (set-face-attribute 'default nil :background "#002b36"
> :foreground "#839496")
> > 3. M-x rainbow-mode.
> > 4. Observe that the hex color value has been highlighted.
> > 5. M-x bug-reference-mode or bug-reference-prog-mode.
> > 6. Observe that the hex color has and overlay with a link interface
> > applied.
>
> I'm unable to reproduce this with the attached test file:
>
>
> None of the hex colours here are buttonised by bug-reference-mode. Are
> there any additional steps needed to see the problem?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
--
Jimmy Yuen Ho Wong
[-- Attachment #2: Type: text/html, Size: 1802 bytes --]
next prev parent reply other threads:[~2021-11-09 4:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 17:41 bug#51691: 28.0.60; bug-reference-mode conflicts with rainbow-mode Jimmy Yuen Ho Wong
2021-11-09 4:17 ` Lars Ingebrigtsen
2021-11-09 4:29 ` Jimmy Yuen Ho Wong [this message]
2021-12-23 10:27 ` Lars Ingebrigtsen
2022-01-21 13:37 ` Lars Ingebrigtsen
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='CAKDRQS6c0YxvtV9eSdki+ianGXY=RRcGD_00zT9=5F82MR7UvA@mail.gmail.com' \
--to=wyuenho@gmail.com \
--cc=51691@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.