all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kaushal.modi@gmail.com, eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Cleaner way to not build the ctags that ships with emacs?
Date: Thu, 10 Mar 2016 14:48:41 +0100	[thread overview]
Message-ID: <22241.31545.974354.694899@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <8337rymqjc.fsf@gnu.org>

>>>>> On Thu, 10 Mar 2016, Eli Zaretskii wrote:

>> Date: Thu, 10 Mar 2016 12:47:09 +0100
>> Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org,
>> kaushal.modi@gmail.com
>> From: Ulrich Mueller <ulm@gentoo.org>
>> 
>> > Maybe we should even make that the default?  Does anyone still use
>> > the ctags that is distributed with Emacs?
>> 
>> Wouldn't that argument apply to etags as well?

> No, because the Exuberant program is named "ctags", not "etags".

Sorry, but I don't understand. Exuberant installs a ctags binary and
(if configured with the --enable-etags option) an etags symlink
pointing to it.

Why would the argument be different for the case of two separate
binaries, as opposed to one binary and a symlink to it? Either way,
there will be name (and file) collisions.

Ulrich



  reply	other threads:[~2016-03-10 13:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 20:56 Cleaner way to not build the ctags that ships with emacs? Kaushal Modi
2016-03-09 21:06 ` Eli Zaretskii
2016-03-09 21:29   ` Kaushal Modi
2016-03-10  6:10     ` Eli Zaretskii
2016-03-10  1:48 ` Paul Eggert
2016-03-10  6:56   ` Eli Zaretskii
2016-03-10 11:47     ` Ulrich Mueller
2016-03-10 12:34       ` Kaushal Modi
2016-03-10 12:48       ` Dmitry Gutov
2016-03-10 13:05       ` Eli Zaretskii
2016-03-10 13:48         ` Ulrich Mueller [this message]
2016-03-10 14:20           ` Eli Zaretskii
2016-03-10 15:05           ` Stefan Monnier

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=22241.31545.974354.694899@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kaushal.modi@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.