unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabrice Nicol <fabrnicol@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47408@debbugs.gnu.org
Subject: bug#47408: Etags support for Mercury [v0.5]
Date: Tue, 8 Jun 2021 02:38:12 +0200	[thread overview]
Message-ID: <CANTSrJsV1xW2UfAFmguuNCqFGa4uN5tmr=sxtQv=sEcBuufGzg@mail.gmail.com> (raw)
In-Reply-To: <83fsxthnye.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]

There is something to be fixed if this is the expected output, as ctags
invocation dose not work for Mercury files. I have not looked into the
issue yet but the fix should be quite small.

Le mar. 8 juin 2021 à 2:05 AM, Eli Zaretskii <eliz@gnu.org> a écrit :

> > Cc: 47408-done@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> > From: fabrice nicol <fabrnicol@gmail.com>
> > Date: Sun, 6 Jun 2021 22:49:19 +0200
> >
> > > That's difficult to tell for me.  However, etags provides ctags support
> > > for all languages it knows about.  I may be missing something, but I
> > > think Mercury would be the first exception.  If that's the case, maybe
> > > it would be worth  adding a comment telling so.
> >
> > ctags only differs from etags by the fact that its output is
> > Vim-compatible. But it so happens that Mercury has superior in-built
> > support for Vim tagging (the core team use Vim). So ctags would not
> > actually be used by users with Vim-compatibility requirements, they
> > would just use Mercury tagging on Vim.
>
> What do we lose if we make Mercury support active in ctags mode?  Do
> we even need to add any code for that?
>

[-- Attachment #2: Type: text/html, Size: 1803 bytes --]

  reply	other threads:[~2021-06-08  0:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <25b8baef-11f2-7079-69d8-3207a24658fc@gmail.com>
2021-03-26  7:09 ` bug#47408: Emacs etags support for Mercury [v0.2] fabrice nicol
2021-03-27 10:51   ` bug#47408: Etags support for Mercury [v0.3] fabrice nicol
2021-03-28 13:11     ` Eli Zaretskii
2021-03-28 15:49       ` fabrice nicol
2021-03-28 16:22         ` Eli Zaretskii
2021-03-29 11:53           ` bug#47408: Etags support for Mercury [v0.4] fabrice nicol
     [not found]             ` <70503251-f8ea-9006-b7e7-b13b93bb71de@gmail.com>
2021-05-15  8:31               ` bug#47408: Fwd: " Eli Zaretskii
     [not found]                 ` <53162dfb-0715-3077-78d1-3a8340943f2f@gmail.com>
2021-05-29  8:01                   ` Eli Zaretskii
     [not found]                     ` <CANTSrJtDMu=4SWUcBRt51X8n42mOfB6_sFi8mNoZ0YgYdtE-DA@mail.gmail.com>
2021-05-29 10:22                       ` Eli Zaretskii
2021-06-01  2:38                     ` bug#47408: Etags support for Mercury [v0.5] fabrice nicol
2021-06-06  9:48                       ` Eli Zaretskii
2021-06-06 13:34                         ` fabrice nicol
2021-06-06 18:18                           ` Francesco Potortì
2021-06-06 20:49                             ` fabrice nicol
2021-06-06 21:04                               ` Francesco Potortì
2021-06-07 12:13                               ` Eli Zaretskii
2021-06-08  0:38                                 ` Fabrice Nicol [this message]
2021-06-08 10:53                                 ` Francesco Potortì
2021-06-08 11:47                                   ` Eli Zaretskii
2021-06-08 12:47                                     ` Francesco Potortì
2021-06-10 13:59                                       ` Eli Zaretskii
2021-06-10 16:52                                         ` fabrice nicol
2021-06-10 17:05                                           ` Francesco Potortì
2021-06-10 17:20                                           ` Eli Zaretskii
2021-06-10 19:15                                             ` Eli Zaretskii
2021-06-10 20:39                                             ` bug#47408: Etags support for Mercury -- fix explicit tags for existentially-quantified procedures fabrice nicol
2021-06-11  5:56                                               ` Eli Zaretskii

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='CANTSrJsV1xW2UfAFmguuNCqFGa4uN5tmr=sxtQv=sEcBuufGzg@mail.gmail.com' \
    --to=fabrnicol@gmail.com \
    --cc=47408@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 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).