From: Eric Gallager <egall@gwmail.gwu.edu>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Enabling Ctags Tree Wide for GCC
Date: Wed, 11 Sep 2019 15:51:00 -0000 [thread overview]
Message-ID: <CAMfHzOvBwFxngfj_LNMht5RTw7f4UP8oeg3aULVzj7NDadtXQA@mail.gmail.com> (raw)
In-Reply-To: <b5af69f0-7edd-65a2-23f2-c6e3a3ffadb5@gmail.com>
On 9/11/19, Nicholas Krause <xerofoify@gmail.com> wrote:
> Greetings,
>
> I was wondering what is the easiest way to allow source tree wide ctags.
> There doesn't
>
> seem to be a make x command for it nor any real documentation online and
> it would
>
> be nice to have.
>
ISTR this topic coming up 2 years ago:
https://gcc.gnu.org/ml/gcc/2017-09/msg00266.html
>
> Thanks,
>
> Nick
>
>
prev parent reply other threads:[~2019-09-11 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 5:02 Nicholas Krause
2019-09-11 6:31 ` Andreas Schwab
2019-09-11 6:55 ` Nicholas Krause
2019-09-11 9:50 ` Hi-Angel
2019-09-11 10:05 ` Hi-Angel
2019-09-11 11:57 ` Martin Liška
2019-09-11 15:51 ` Eric Gallager [this message]
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=CAMfHzOvBwFxngfj_LNMht5RTw7f4UP8oeg3aULVzj7NDadtXQA@mail.gmail.com \
--to=egall@gwmail.gwu.edu \
--cc=gcc@gcc.gnu.org \
--cc=xerofoify@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.
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).