public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Cc: cygwin-apps@cygwin.com
Subject: Re: [ITA] ctags 6.1.0 - programming language source indexing and cross-reference tool
Date: Mon, 17 Jun 2024 16:40:02 +0100	[thread overview]
Message-ID: <b8f58402-7d70-4ce2-9ab0-9cb7989e78f7@dronecode.org.uk> (raw)
In-Reply-To: <46eeafb8-a3e0-4a8d-a00a-9cb1932c4c7a@SystematicSW.ab.ca>

On 15/06/2024 16:10, Brian Inglis via Cygwin-apps wrote:
> [Forgot attachments]
> 
> On 2024-06-14 23:20, Brian Inglis via Cygwin-apps wrote:
>> I would like to adopt ctags and update it to successor universal-ctags.

Thanks. I added this to your packages.

>> Description:
>> Generates an index (tag) file of language objects found in
>> source files.
>> The index makes it easy for text editors or other utilities to locate
>> the indexed items.
>> Ctags can also generate a cross reference file which lists information
>> about the various objects found in a set of language files in human
>> readable form.
>> Exuberant Ctags improves on ctags because it can find all types of

This should say "universal-ctags", right?

>> language tags, including macro definitions, enumerated values (values
>> inside enum{...}), function and method definitions, enum/struct/union
>> tags, external function prototypes, typedef names and variable
>> declarations.
>> Exuberant Ctags is far less likely to be fooled by code containing
>> preprocessor conditional constructs than ctags.
>> Exuberant ctags supports output of Emacs style TAGS files and can be
>> used to print out a list of selected objects found in source files.
>> Install ctags if you are going to use your system for C programming.



  reply	other threads:[~2024-06-17 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15  5:20 Brian Inglis
2024-06-15 15:10 ` Brian Inglis
2024-06-17 15:40   ` Jon Turney [this message]
2024-06-17 18:50     ` Brian Inglis

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=b8f58402-7d70-4ce2-9ab0-9cb7989e78f7@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Brian.Inglis@SystematicSw.ab.ca \
    --cc=cygwin-apps@cygwin.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).