all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: andreas.matthias@gmail.com, 21934@debbugs.gnu.org
Subject: bug#21934: 24.5; find-tag: reading TAGS file incorrectly
Date: Sun, 22 Nov 2015 18:54:40 +0200	[thread overview]
Message-ID: <5651F350.6080203@yandex.ru> (raw)
In-Reply-To: <83si3y2et4.fsf@gnu.org>

On 11/22/2015 06:12 PM, Eli Zaretskii wrote:
> Completion is not an integral part of find-tag.

It's not an integral part of xref-find-definitions either.

> As I said, completion in M-. in Emacs 25 works worse than in find-tag
> in this case: it doesn't even succeed to complete "Rec TAB" into
> "Rectangle".  I don't know why.

I didn't see any difference between them. Anyway, it should be fixed now.

>> Is it really any different? M-x find-tag RET TAB doesn't show anything
>> beginning with "Rectangle" either. I only get "getPos" as a completion
>> either way.
>
> It's different if you type "Rec TAB".

If I revert 51fd4a01395885077909c60b17ae3d7d42b8bb0a and reopen the TAGS 
file, the only completion I get is "getPos", either way.

It *is* different if you type "Rec RET", however, because in the end 
"Rec" gets a match via `tag-any-match-p', which 
etags--xref-find-definitions doesn't use.

But the user can add it to etags-xref-find-definitions-tag-order, if 
they want.

> My main point is that it's easy to solve the completion case, but that
> hardly help in using TAGS with Lua and the new xref commands.
> Something else is missing.

I believe I've addressed that.

And if I understand Andreas right, etags should output two tags for each 
such definition. Just like we do for C++.





  reply	other threads:[~2015-11-22 16:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 19:47 bug#21934: 24.5; find-tag: reading TAGS file incorrectly Andreas Matthias
2015-11-17  4:01 ` Dmitry Gutov
2015-11-17 16:06   ` Eli Zaretskii
2015-11-17 17:21   ` Andreas Matthias
2015-11-17 17:24     ` Dmitry Gutov
2015-11-17 17:40       ` Andreas Matthias
2015-11-17 17:46         ` Dmitry Gutov
2015-11-17 19:38           ` Andreas Matthias
2015-11-18  1:56             ` Dmitry Gutov
2015-11-21 13:07   ` Eli Zaretskii
2015-11-22  1:17     ` Dmitry Gutov
2015-11-22  4:38       ` Dmitry Gutov
2015-11-22 14:08       ` Andreas Matthias
2015-11-22 14:33         ` Dmitry Gutov
2015-11-22 14:41           ` Dmitry Gutov
2015-11-22 15:06           ` Andreas Matthias
2015-11-22 15:23             ` Dmitry Gutov
2015-11-22 16:41               ` Andreas Matthias
2015-11-22 16:43                 ` Dmitry Gutov
2015-11-22 16:12       ` Eli Zaretskii
2015-11-22 16:54         ` Dmitry Gutov [this message]
2015-11-22 17:38           ` Eli Zaretskii
2015-11-22 17:43             ` Dmitry Gutov
2015-11-22 17:49               ` Andreas Matthias
2015-11-22 18:13                 ` Eli Zaretskii
2015-11-23 16:50                   ` Andreas Matthias
2015-11-23 17:16                     ` Eli Zaretskii
2015-11-23 17:28                       ` Andreas Matthias
2015-11-23 18:17                         ` Eli Zaretskii
2015-11-28 10:33                           ` Eli Zaretskii
2015-11-28 17:25                             ` Andreas Matthias
2015-11-30 17:34                               ` Eli Zaretskii
2015-11-28 17:25                             ` Andreas Matthias
2015-11-22 18:09               ` Eli Zaretskii
2015-11-22 18:27                 ` Andreas Matthias
2015-11-22 18:33                   ` Dmitry Gutov
2015-11-22 18:52                     ` Andreas Matthias
2015-11-26  2:41       ` Dmitry Gutov
2015-11-17 11:05 ` Stephen Leake
2015-11-17 17:17   ` Andreas Matthias

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=5651F350.6080203@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=21934@debbugs.gnu.org \
    --cc=andreas.matthias@gmail.com \
    --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.