From: Cuihtlauac ALVARADO <cuihtlauac.alvarado@francetelecom.com>
To: Issac Trotts <ijtrotts@ucdavis.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] taggage 1.1
Date: Tue, 26 Aug 2003 16:59:50 +0200 [thread overview]
Message-ID: <20030826145950.GA19299@francetelecom.com> (raw)
In-Reply-To: <3F4B0060.1060803@ucdavis.edu>
Cool, yet another tag generator for ocaml :-)
Did you experienced trouble with otags for vim? In case you do, just
send me a bug report. Quoting a famous post on this mailing list, it
would make me feel like if I was not :
student-turned-professional-maker-of-animated-powerpoint-slideshows
BTW, otags 3.06.8 (hopefully the last for 3.06) is there :
http://perso.rd.francetelecom.fr/alvarado/soft/otags-3.06.8.tar.gz
Includes some fresh patches sent by Chris Hecker and Hendrik Tews,
thanks for contributions.
Ciao.
On Mon, Aug 25, 2003 at 11:38:24PM -0700, Issac Trotts wrote:
> This version fixes the problem I mentioned earlier. The new version is
> up at
>
>
> http://redwood.ucdavis.edu/~issac/taggage-1.1.ml
>
>
> Version 1.0 has been removed.
>
>
> Re: Karl Zilles' question about how taggage compares to otags. otags
> uses camlp4 macros to convert abstract syntax trees into tag files.
> taggage uses regular expressions, uses no camlp4, and has many fewer
> lines of code.
--
Cuihtlauac ALVARADO - France Telecom R&D - DTL/TAL
2, avenue Pierre Marzin - 22307 Lannion - France
Tel: +33 2 96 05 32 73 - Fax: +33 2 96 05 39 45
-------------------
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 prev parent reply other threads:[~2003-08-26 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 6:38 Issac Trotts
2003-08-26 14:59 ` Cuihtlauac ALVARADO [this message]
2003-08-26 22:09 ` taglet 1.0 (was Re: [Caml-list] taggage 1.1) Issac Trotts
2003-08-27 8:13 ` Hendrik Tews
2003-08-27 11:09 ` Hendrik Tews
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=20030826145950.GA19299@francetelecom.com \
--to=cuihtlauac.alvarado@francetelecom.com \
--cc=caml-list@inria.fr \
--cc=ijtrotts@ucdavis.edu \
/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