From: Ergus <spacibba@aol.com>
To: Po Lu <luangruo@yahoo.com>
Cc: "Alfred M. Szmidt" <ams@gnu.org>,
eliz@gnu.org, dgutov@yandex.ru, emacs-devel@gnu.org
Subject: Re: etags name collision.
Date: Tue, 12 Apr 2022 13:03:09 +0200 [thread overview]
Message-ID: <20220412110309.b227g5q2yoqoa5hp@Ergus> (raw)
In-Reply-To: <87ilrewp5s.fsf@yahoo.com>
On Tue, Apr 12, 2022 at 06:51:11PM +0800, Po Lu wrote:
>Ergus <spacibba@aol.com> writes:
>
>> I use OpenBSD in my servers daily and all my team around use vim and
>> neovim with Universal Ctags with no issue. Universal ctags can generate
>> emacs tags, json, legacy and modern ctags, xref... if there is some
>> problem the right to do is to open an issue in their project...
>
>vim and neovim are not vi and mg, and are not standardized utilities
>either.
>
So you mean that we should maintain this executable with an old name
that collides with a better modern one; useful for all the vim (and
other editors) users, just to support two editors that are not emacs,
very popular and with minimal maintenance...
Any way I am tired of this pointless discussion... When things start
like this in the list we end up going nowhere.
Best,
Ergus
next prev parent reply other threads:[~2022-04-12 11:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411124736.3qijvtearh6wlen7.ref@Ergus>
2022-04-11 12:47 ` etags name collision Ergus
2022-04-11 13:18 ` Eli Zaretskii
2022-04-11 13:38 ` Dmitry Gutov
2022-04-11 13:52 ` Ergus
2022-04-11 14:11 ` Eli Zaretskii
2022-04-11 14:25 ` Ergus
2022-04-12 7:16 ` Alfred M. Szmidt
2022-04-12 8:30 ` Andreas Schwab
2022-04-12 10:48 ` Ergus
2022-04-12 10:51 ` Po Lu
2022-04-12 11:03 ` Ergus [this message]
2022-04-12 11:13 ` Dmitry Gutov
2022-04-12 11:28 ` Po Lu
2022-04-12 13:45 ` Alfred M. Szmidt
2022-04-12 14:29 ` Dmitry Gutov
2022-04-12 15:36 ` Óscar Fuentes
2022-04-12 17:13 ` Ergus
2022-04-12 13:45 ` Alfred M. Szmidt
2022-04-12 13:45 ` Alfred M. Szmidt
2022-04-12 16:40 ` Ergus
2022-04-12 17:21 ` Alfred M. Szmidt
2022-04-12 17:48 ` Ergus
2022-04-12 19:50 ` Alfred M. Szmidt
2022-04-12 20:49 ` Dmitry Gutov
2022-04-13 5:45 ` Alfred M. Szmidt
2022-04-12 17:53 ` Stefan Monnier
2022-04-11 13:59 ` Andreas Schwab
2022-04-11 14:07 ` Eli Zaretskii
2022-04-11 13:47 ` Ergus
2022-04-11 14:09 ` Eli Zaretskii
2022-04-11 14:18 ` Ergus
2022-04-11 15:46 ` [PATCH] " Ergus
2022-04-11 15:51 ` Eli Zaretskii
2022-04-11 16:19 ` Ergus
2022-04-11 16:40 ` Eli Zaretskii
2022-04-11 19:19 ` Ergus
2022-04-11 19:39 ` Ulrich Mueller
2022-04-11 19:53 ` Ergus
2022-04-11 21:04 ` Ulrich Mueller
2022-04-11 22:20 ` Ergus
2022-04-12 7:21 ` Alfred M. Szmidt
2022-04-12 7:34 ` Ulrich Mueller
2022-04-12 10:53 ` Ergus
2022-04-12 2:28 ` Eli Zaretskii
2022-04-12 2:43 ` Po Lu
2022-04-12 5:03 ` Ulrich Mueller
2022-04-12 11:13 ` Ergus
2022-04-12 11:48 ` Eli Zaretskii
2022-04-12 11:56 ` Eli Zaretskii
2022-04-12 12:50 ` Ulrich Mueller
2022-04-12 7:16 ` Alfred M. Szmidt
2022-04-12 12:15 ` Eli Zaretskii
2022-04-11 16:46 ` Stefan Monnier
2022-04-11 17:01 ` Eli Zaretskii
2022-04-11 17:41 ` Stefan Monnier
2022-04-11 18:15 ` Eli Zaretskii
2022-04-11 19:11 ` Ulrich Mueller
2022-04-12 7:42 ` Thierry Volpiatto
2022-04-11 18:15 ` Ergus
2022-04-11 23:09 ` Ergus
2022-04-11 14:10 ` Andreas Schwab
2022-04-11 13:56 ` Kaushal Modi
2022-04-11 14:16 ` Óscar Fuentes
2022-04-12 3:19 ` Richard Stallman
2022-04-12 7:16 ` Alfred M. Szmidt
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=20220412110309.b227g5q2yoqoa5hp@Ergus \
--to=spacibba@aol.com \
--cc=ams@gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.