unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bob Rogers <rogers@rgrjr.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Verifying tags in the wrong file
Date: Wed, 9 Nov 2022 12:57:18 -0800	[thread overview]
Message-ID: <25452.5166.879297.777509@orion.rgrjr.com> (raw)
In-Reply-To: <CAAeL0STARQ2KQvNQ_JOqaKMGv4Hzq2HvJ7wke5GYHUJNNRxOiQ@mail.gmail.com>

   From: Juanma Barranquero <lekktu@gmail.com>
   Date: Wed, 9 Nov 2022 12:46:58 +0100

   M-x load-library <RET> etags <RET>
   M-: (tags-verify-table "any-file-not-tags") <RET>

   It returns nil and leaves behind a buffer visiting the file, in Tags Table
   mode. Not nice, but more or less as expected. Not a bug.

   However, if you verify a (no tags) file already being visited in a buffer,
   it returns nil and *leaves* the buffer in Tags Table mode!

   Well, you'll say, "don't do that". Ok, except that you can do it by
   accident, for example if you're using bs-show and happen to type "t" in the
   wrong line.

   Which, arguably, could be fixed in bs (though I think it's a bug in
   etags.el, not bs.el), except that I don't think there's a
   tags-table-buffer-p or equivalent to check that the buffer contains a Tags
   Table. The way to test it seems to be `tags-verify-table'...

I had a similar issue recently (see bug#54133 [1]) though coming from
buffer-menu-mode.  I would recommend filing a bug report, though the
upshot was that in some situations putting the buffer into
tags-table-mode is TRT, but making it harder to do by accident is also a
good thing.

					-- Bob Rogers
					   http://www.rgrjr.com/

[1]  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54133



  reply	other threads:[~2022-11-09 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 11:46 Verifying tags in the wrong file Juanma Barranquero
2022-11-09 20:57 ` Bob Rogers [this message]
2022-11-10  0:28   ` Juanma Barranquero

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=25452.5166.879297.777509@orion.rgrjr.com \
    --to=rogers@rgrjr.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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).