|
From: | Miklos Somogyi |
Subject: | Re: [Groff] gtroff & soelim don't recognize ~ in paths |
Date: | Mon, 10 Apr 2006 14:29:28 +1000 |
Ditto. Environment variables too. Everything valid to the shell, should be valid to groff.
Why? User convenience. Shouldn't this be consideration No 1? Slight problems: which shell, what OS?Again it raises the question: who is (or whom gnu.org targets as) a customer?
From my admittedly selfish point of view, usability far outweighs everything,
including `total compatibility'.The less a user needs to concentrate of the `how' of the job, the better. E.g. integer arithmetic etc is a relic from an age long gone, it would be so nice
to say good bye to it.I would rather pay for a thoroughly modern implementation of troff that only inherits the wonderful original ideas but not the constraints of the original times.
But that's just wishful thinking and I hope that this does not offend the keepers of the flame.
Miklos On 10/04/2006, at 11:39 AM, Greg 'groggy' Lehey wrote:
On Sunday, 9 April 2006 at 10:00:25 -0400, Larry Kollar wrote:Werner LEMBERG asked, perhaps rhetorically:Why on earth do you expect tilde expansion within groff?I'm used to it working in vi(m) and I seem to remember it working in awk. I've also seen it work in X11-based file dialogs. Over time, I suppose I've come to assume that ~ was a Un*x idiom rather than a shell idiom.Agreed; why shouldn't it work in groff? It should be relatively straightforward to implement it (looks the other way). Greg -- Finger address@hidden for PGP public key. See complete headers for address and phone numbers. _______________________________________________ Groff mailing list address@hidden http://lists.gnu.org/mailman/listinfo/groff
[Prev in Thread] | Current Thread | [Next in Thread] |