From: Eli Zaretskii <eliz@gnu.org>
To: fabrice nicol <fabrnicol@gmail.com>
Cc: 47408@debbugs.gnu.org
Subject: bug#47408: [PATCH] Etags support for Mercury -- fix explicit tags for existentially-quantified procedures
Date: Fri, 18 Jun 2021 14:29:41 +0300 [thread overview]
Message-ID: <83zgvnxvfe.fsf@gnu.org> (raw)
In-Reply-To: <768bbdf8-19a9-7401-65a0-9171678c006b@gmail.com> (message from fabrice nicol on Thu, 17 Jun 2021 20:36:56 +0200)
> Cc: pot@gnu.org, 47408@debbugs.gnu.org
> From: fabrice nicol <fabrnicol@gmail.com>
> Date: Thu, 17 Jun 2021 20:36:56 +0200
>
> I could finalize my tests against the entire Mercury library code.
>
> All is OK. I applied your patch on top of mine.
>
> Also, I added two new corner-case fixes, which are mentioned in the
> commit message:
>
> 1. The first new fix is for 0-arity predicates and functions. Yes,
> Mercury has them. (They play the role of global immutable constants in
> other languages).
>
> They happened not to be caught by the previous code, now they are.
>
> 2. I also removed module names from within tag names. The point is that
> module name prefixing is optional in most cases, so if you leave the
> module prefix within the tag, you will fail to get to the declaration
> when striking M-. on a (non-prefixed) predicate name. It is better to
> remove the name altogether. This will automatically trigger an explicit tag.
Thanks, installed.
next prev parent reply other threads:[~2021-06-18 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12421.1623412982.2554.bug-gnu-emacs@gnu.org>
2021-06-14 15:10 ` bug#47408: [PATCH] Etags support for Mercury -- fix explicit tags for existentially-quantified procedures fabrice nicol
2021-06-14 16:04 ` Eli Zaretskii
2021-06-14 17:10 ` fabrice nicol
2021-06-14 17:42 ` Eli Zaretskii
2021-06-14 18:52 ` fabrice nicol
2021-06-17 10:50 ` Eli Zaretskii
2021-06-17 11:19 ` Fabrice Nicol
2021-06-17 11:42 ` Eli Zaretskii
2021-06-17 18:36 ` fabrice nicol
2021-06-18 11:29 ` Eli Zaretskii [this message]
2021-06-18 11:54 ` Francesco Potortì
2021-06-18 12:33 ` Eli Zaretskii
2021-06-18 13:53 ` fabrice nicol
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=83zgvnxvfe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47408@debbugs.gnu.org \
--cc=fabrnicol@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 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.