From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Cleaner way to not build the ctags that ships with emacs?
Date: Thu, 10 Mar 2016 08:10:29 +0200 [thread overview]
Message-ID: <83y49qn9re.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY0XnXQqsHCCY-VKwOE8PaQut7idu=mQ1aXXQwJ_WgSP6A@mail.gmail.com> (message from Kaushal Modi on Wed, 9 Mar 2016 16:29:28 -0500)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Wed, 9 Mar 2016 16:29:28 -0500
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> Why not put your Exuberant ctags elsewhere, and use a shell alias to
> invoke it?
>
> That's definitely an option. But I was looking for a way to declutter my $PATH and $MANPATH of stuff I am
> never going to use. Also I prefer to not hard code aliases to binaries because my binary locations are dynamic
> (the $PATH is update based on the RHEL OS version and version of the software (master/stable/etc)).
An alias can use any shell construct you want, so it can be dynamic.
> Would removing "ctags${EXEEXT}" from this line (using something like sed) prevent building of ctags and its
> manpage?
Yes.
next prev parent reply other threads:[~2016-03-10 6:10 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 [this message]
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
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=83y49qn9re.fsf@gnu.org \
--to=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.