Hello Gavin,
Answers below
Le 28/04/2016 20:35, Gavin Smith a écrit :
> On 28 April 2016 at 09:30, Vincent Belaïche
> wrote:
[...]
>
> That's what texi2dvi does. The foo~bar.texi file has a line in it
> "\input texinfo" which loads texinfo.tex, and the catcode and active
> definition of ~ are
<>| are not valid in filenames
They are on Unix. -k
On 27 April 2016 at 22:33, Vincent Belaïche wrote:
>> The solution is presumably to avoid using an absolute path.
>
> The space in filename problem is not sh lack of quoting. This is a TeX
> limitation of \input. \input gets the filname up to the first space or
> \relax. I will investigate whether
On 28 April 2016 at 09:30, Vincent Belaïche wrote:
> - catcoding to letters all the tex special characters that are valid in
> filename, that is to say: {}$#~ and space. I am using < > and | in
> place of { } and space respectively as <>| are not valid in filenames
> anyway. This does not h
One more patch --- see comments below
Le 28/04/2016 00:32, Stephen H. Dawson a écrit :
> Nice. Glad to see people working together. It is a rarity in life I
> greatly enjoy experiencing. :-)
>
> Thank You,
> Stephen H. Dawson
> (865) 804-3454
> http://www.linkedin.com/in/shdcs
>
>
> On 04/27/2016
