From: Issac Trotts <ijtrotts@ucdavis.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Taglet 1.2
Date: Tue, 26 Aug 2003 23:17:31 -0700 [thread overview]
Message-ID: <3F4C4CFB.9040108@ucdavis.edu> (raw)
Here's another revision. Enjoy!
Changes for version 1.2:
o Handling of .ml files having no .mli counterparts
o Handling of files containing no lines without slashes
From the README:
Why write another tagger?
=========================
Taglet makes a tag file that just lists all the .mli files, which
reduces the number of redundant tags and helps you get the
documentation you want more quickly without having to dig through a
bunch of identical tags.
With otags, if I want to look up List.map, I put my cursor over
"map", press ctrl-], and look through a bunch of other map functions
until I find the one I want. With Taglet, I put my cursor over
"List", press ctrl-], and am immediately in list.mli. Then I search
for "map" in list.mli. Often, if the .mli file is short, I can find
what I need without having to page down.
Why not just add Taglet's functionality to an existing tagger?
==============================================================
Taglet is tiny and is useful alone, so it's nice to have it as a
separate program. I would like add its functionality to otags, but I
haven't yet figured out how to do it. Even if I do, Taglet will still
be useful and easy to understand on its own.
Issac Trotts
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2003-08-27 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 6:17 Issac Trotts [this message]
2003-08-27 11:20 ` Hendrik Tews
2003-08-27 17:40 ` Issac Trotts
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=3F4C4CFB.9040108@ucdavis.edu \
--to=ijtrotts@ucdavis.edu \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).