unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Francesco Potorti` <pot@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
	158@emacsbugs.donarmstrong.com
Cc: Emacs Bugs <bug-gnu-emacs@gnu.org>
Subject: bug#158: Etags completion problem for local tags table
Date: Fri, 30 May 2008 09:34:23 +0200	[thread overview]
Message-ID: <E1K1z83-00006l-9z@tucano.isti.cnr.it> (raw)
In-Reply-To: <jwvfxs0aj6k.fsf-monnier+emacsbugreports@gnu.org>

>> In (at least) emacs 22.1, completing reads for find-tag and list-tags
>> will use the global tags table list even if a local tags file has
>> been specified using a prefix argument for visit-tags-table.
>
>I believe this has already been fixed in the Emacs-23 CVS repository.
>Could you check it?
>
>About the other problems you mentioned, I don't understand enough of
>etags.el's handling of tags-table-list to know what is done on purpose,
>what is a limitation, and what is a bug.  Francesco?

I am not sure what are "the other problems ... mentioned".  Anyway,
regarding the relationship between tags-file-name and tags-table-list, I
always found it confusing.  I see three documentation problems:

First, the help for both variables says that if you set one, you should
not set the other, which is not clear: should one set one or the other?

Second, neither help mentions the visit-tags-table function, which I
think should be the only way to set those variables interactively.

Third, there is no single place where the relationships between the two
variables are described.






  reply	other threads:[~2008-05-30  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 21:36 bug#158: Etags completion problem for local tags table Stefan Monnier
2008-05-30  7:34 ` Francesco Potorti` [this message]
2008-05-30 13:39   ` Stefan Monnier
2008-05-30 13:42   ` Stefan Monnier
     [not found] <mailman.7663.1203474863.18990.bug-gnu-emacs@gnu.org>
2016-02-29  5:00 ` Lars Ingebrigtsen
2016-02-29 14:58   ` Radey Shouman
2016-11-22 18:23 ` Josiah Schwab

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=E1K1z83-00006l-9z@tucano.isti.cnr.it \
    --to=pot@gnu.org \
    --cc=158@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).