Subject: Re: technical acronyms (misc/17559)
To: Jan Schaumann <email@example.com>
From: Julio Merino <firstname.lastname@example.org>
Date: 04/09/2003 13:37:15
On Tue, 8 Apr 2003 22:13:49 -0400
Jan Schaumann <email@example.com> wrote:
> Hubert Feyrer <firstname.lastname@example.org> wrote:
> > On Tue, 8 Apr 2003, Julio Merino wrote:
> > > afaik, the share/misc/acronyms file is not intended to contain technical
> > > acronyms. Although, I could find it useful if wtf(6) could explain what
> > > some of these terms mean; this is why I sent PR misc/17559 at first.
> > >
> > > But, as said above, that file should not contain this stuff. So what
> > > to do? Close this PR?
> > > Or maybe we can add an acronyms.comp (or whatever) file to contain such
> > > words?
> > Move wtf to some other place, make it a package and add things there.
> Eew, I don't like that. I'd rather suggest to add a flag to wtf and
> thus allow it to use a different file. Say
> wtf -f ~/my.acronyms bsd
> Then you can alias it and keep your own private acronyms file.
Or, what I was thinking about "wtf -t <something> acronym"
So you do: "wtf -t comp pci" and it searches the pci acronym in the
Julio M. Merino Vidal <email@example.com>
The NetBSD Project - http://www.NetBSD.org/