From: Eric Lee Green <eric@badtux.org>
To: esr@thyrsus.com, Mark Galassi <rosalia@galassi.org>
Cc: Docbook Tools discussion list
<docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: new tools coming and a couple of renamings
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <00072106383601.17361@ehome.inhouse> (raw)
In-Reply-To: <20000721032257.F14571@thyrsus.com>
On Fri, 21 Jul 2000, esr@thyrsus.com wrote:
> Mark Galassi <rosalia@galassi.org>:
> > So my proposal is to deprecate the db2* names in favor of the
> > docbook2* names. This phase-out would be extremely slow, since
> > thousands of build procedures use the db2* scripts now.
>
> something to do with databases. Removing ambiguity is good. On the
> other hand, it's proper Unix tradition to have short names for a
> reason -- it saves typing for hapless fumble-fingers like me.
'db' is too much like a database name. 'docbook' is too long. How about "docb"?
as in, "docb2html" etc.? Yeah, it's just 3 characters shorter, but it appears
to be the shortest unambiguous name... clearly says the command has something
to do with docs, and the b is clue enough that it's dealing with docbook.
Alternately, "doc2html" etc... hmm... bit ambigous there. Might make me think
it's a generic x-format doc to html translater....
--
Eric Lee Green There is No Conspiracy
eric@badtux.org http://www.badtux.org
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Mark Galassi
2000-12-27 6:36 ` esr
2000-12-27 6:36 ` Jorge Godoy
2000-12-27 6:36 ` Eric Lee Green [this message]
2000-12-27 6:36 ` Sylvan Ravinet
2000-07-21 0:08 ` Sylvan Ravinet
2000-12-27 6:36 ` Bill Brooks
2000-12-27 6:36 ` Mark Galassi
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Norman Walsh
-- strict thread matches above, loose matches on Subject: below --
2000-12-27 6:36 Gregory Leblanc
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=00072106383601.17361@ehome.inhouse \
--to=eric@badtux.org \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=esr@thyrsus.com \
--cc=rosalia@galassi.org \
/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).