> "Charles" == Charles P Wright <[EMAIL PROTECTED]> writes:
Charles> Asger Alstrup Nielsen wrote:
>> > Linux does support spaces in file names, and LyX output's
>> postscript > with spaces in filenames. The lpr command tries to
>> use _'s instead of > spaces which is the problem.
>>
>> I c
On Tue, 9 Feb 1999, Asger Alstrup Nielsen wrote:
> > Linux does support spaces in file names, and LyX output's postscript
> > with spaces in filenames. The lpr command tries to use _'s instead of
> > spaces which is the problem.
>
> I can confirm that this is most probably a bug in LyX.
> Someo
Tim Waugh wrote:
>
> On Tue, 9 Feb 1999, Asger Alstrup Nielsen wrote:
>
> > > Linux does support spaces in file names, and LyX output's postscript
> > > with spaces in filenames. The lpr command tries to use _'s instead of
> > > spaces which is the problem.
> >
> > I can confirm that this is mo
Asger Alstrup Nielsen wrote:
>
> > Linux does support spaces in file names, and LyX output's postscript
> > with spaces in filenames. The lpr command tries to use _'s instead of
> > spaces which is the problem.
>
> I can confirm that this is most probably a bug in LyX.
> Someone with some time
On Tue, 9 Feb 1999, Charles P. Wright wrote:
> As can I, it is that LyX will try printing "a_file" instead. Try making
> a dummy document with a space and printing it.
I just did; it worked. I started LyX, File->New, "space age", typed in
"space age", and clicked on the save icon. "space age.
> Linux does support spaces in file names, and LyX output's postscript
> with spaces in filenames. The lpr command tries to use _'s instead of
> spaces which is the problem.
I can confirm that this is most probably a bug in LyX.
Someone with some time on their hands should have a look and check
I think your problem may be that for UNIXes, a space in a file/directory
name is a definite NO-NO.
? Try
touch "to be or not to be"
Mate
Ralph Meyer wrote:
> I think your problem may be that for UNIXes, a space in a file/directory
> name is a definite NO-NO. The OS will only recognize the material before a
> space and parse the material after it as another argument on a command
> line. Quoting a filename with a space in it won't w
