From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19741@debbugs.gnu.org
Subject: bug#19741: 25.0.50; find-tag completion uses an outdated cache of the tags table
Date: Tue, 03 Feb 2015 03:46:51 +0200 [thread overview]
Message-ID: <54D0288B.7000503@yandex.ru> (raw)
In-Reply-To: <83egq8gqxu.fsf@gnu.org>
On 02/02/2015 07:32 PM, Eli Zaretskii wrote:
> I think this happens because visiting the second TAGS table doesn't
> invalidate or recalculate tags-completion-table, which was generated
> when you pressed TAB at the first find-tag prompt. Look at the
> function tags-completion-table, it does this:
>
> (defun tags-completion-table ()
> "Build `tags-completion-table' on demand.
> The tags included in the completion table are those in the current
> tags table and its (recursively) included tags tables."
> (or tags-completion-table
> ;; No cached value for this buffer.
Seems so, but should the `tags-completion-table' value in the lisp/TAGS
buffer really include the entries from the other currently visited tables?
Looking at `visit-tags-table' signature, some buffers might only have
the above in the local `tags-file-name' value, whereas others might use
`tags-table-list'.
Furthermore, lisp/TAGS doesn't include src/TAGS (it's the other way
around), so `tags-completion-table' variable, judging by the above
docstring, should only store its tags. Even when there are no
buffer-local values involved.
> IOW, it reuses the existing value of tags-completion-table (the
> variable). However, visiting the second TAGS table didn't update the
> completion table, so you get "No match".
See above.
next prev parent reply other threads:[~2015-02-03 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 19:59 bug#19741: 25.0.50; find-tag completion uses an outdated cache of the tags table Dmitry Gutov
2015-02-02 17:32 ` Eli Zaretskii
2015-02-03 1:46 ` Dmitry Gutov [this message]
2015-02-03 18:57 ` Eli Zaretskii
2016-11-26 17:43 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D0288B.7000503@yandex.ru \
--to=dgutov@yandex.ru \
--cc=19741@debbugs.gnu.org \
--cc=eliz@gnu.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.