On 09-Apr-06 Larry Kollar wrote:
> Sourcing a file like this:
>
> .so ~/Library/XSL/html2ms.xsl
>
> Using either straight groff or soelim, I get the message:
> ./single.ms:207: can't open `~/Library/XSL/html2ms.xsl': No such file
> or directory
>
> It works with an explicit path. Is this
> Sourcing a file like this:
>
> .so ~/Library/XSL/html2ms.xsl
>
> Using either straight groff or soelim, I get the message:
> ./single.ms:207: can't open `~/Library/XSL/html2ms.xsl': No such file
> or directory
>
> It works with an explicit path. Is this a bug or a feature?
A feature,
Ted's interpretation is also correct for the bash shell used in
cygwin on windows. ~ is used to indicate home directory when
running bash (or any other shell that does the same expansion),
but filename expansion does not occur in any program that is not
equipped to do its own expansion or cannot/
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
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 dia
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 self
