From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 19741@debbugs.gnu.org
Subject: bug#19741: 25.0.50; find-tag completion uses an outdated cache of the tags table
Date: Mon, 02 Feb 2015 19:32:13 +0200 [thread overview]
Message-ID: <83egq8gqxu.fsf@gnu.org> (raw)
In-Reply-To: <867fw1z9m9.fsf@yandex.ru>
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 01 Feb 2015 21:59:10 +0200
>
> 1. M-x find-file lisp/progmodes/etags.el. Being in that buffer, and not
> in *scratch*, is somehow important.
>
> 2. M-x visit-tags-table ../../lisp/TAGS.
>
> 3. M-x find-tag, press TAB, see the table loaded.
>
> 4. M-x visit-tags-table, ../../src/TAGS, press `y' (important!).
>
> 5. M-x find-tag, type `display_li', press TAB, see [No matches]!
>
> The main scenario ends here.
>
> 6. Finish typing `display_line', press RET, see the navigation succeed
> anyway (with a jump to src/xdisp.c:20013).
>
> 7. Press `M-,' to get back to etags.el, repeat 5., see the same result.
>
> 8. M-x find-file ../../src/search.c, repeat 5., see a different result.
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.
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".
next prev parent reply other threads:[~2015-02-02 17:32 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 [this message]
2015-02-03 1:46 ` Dmitry Gutov
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=83egq8gqxu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19741@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.