unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Scott via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: "51337@debbugs.gnu.org" <51337@debbugs.gnu.org>
Subject: bug#51337: Subject: 27.2; mouse-buffer-menu-mode-groups
Date: Sat, 23 Oct 2021 18:38:42 +0000	[thread overview]
Message-ID: <AM5PR0701MB264232E139E14BB99F707AE78E819@AM5PR0701MB2642.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <87sfwrd7ty.fsf@mail.linkov.net>

Thanks,
I also found that if I reverse the order of the tests the last one is valid. And it works then.

Many thanks

-----Original Message-----
From: Juri Linkov <juri@linkov.net> 
Sent: Saturday, 23 October 2021 7:58 PM
To: Peter Scott <peter.scott@ericsson.com>
Cc: 51337@debbugs.gnu.org
Subject: Re: bug#51337: Subject: 27.2; mouse-buffer-menu-mode-groups

> the verilog files are grouped as "Version Control”. Clearly this is 
> not correct. If i switch to a verilog file and do C-h major-mode Ret 
> the major mode is listed as verilog.
>
> I've tried to update the mouse-buffer-menu-mode-groups to this
> Value:
> ("log\\|diff\\|vc\\|cvs\\|Git\\|Annotate" . "Version Control")

Oh, it's unfortunate that "log\\|diff..." also matches "verilog".
This regexp should be tightened to match only VC buffers, but not buffers from other modes.  Maybe something like

  ("vc.*log\\|diff\\|vc\\|cvs\\|Git\\|Annotate" . "Version Control")

  reply	other threads:[~2021-10-23 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 17:27 bug#51337: Subject: 27.2; mouse-buffer-menu-mode-groups Peter Scott via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-23 17:58 ` Juri Linkov
2021-10-23 18:38   ` Peter Scott via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-10-24 18:32   ` Lars Ingebrigtsen
2021-10-24 18:32   ` Lars Ingebrigtsen
2021-11-08 19:24     ` 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

  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=AM5PR0701MB264232E139E14BB99F707AE78E819@AM5PR0701MB2642.eurprd07.prod.outlook.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=51337@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=peter.scott@ericsson.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).