it is easy, when you do not insert the urls with LyX, then
Lyx does not write \uesepacjega{url} into the preamble and
you can use any option.
Thankyou very much Herbert! This does indeed fix my problem. Now I can use [obeyspaces].
El 26/02/2004, a las 8:32, Jean-Pierre.Chretien escribió:
You may also just comply to RFC 1630 ans put + instead of spaces
\path{/Really/long/path/that/is/going/to/need/to/have/a+line+break/in/ it.txt
instead of
\path{/Really/long/path/that/is/going/to/need/to/have/a line break/in/it.txt
Much cleaner solution IMHO.
Thanks a lot Jean-Pierre. I tested this solution and it also fixes the problem.
I was curious to see what would happen on my local filesystem when I tried using "+" instead of spaces, because as far as I know RFC 1630 is specifically intended for the WWW.
Here is what happens in my Bash shell:
$ mkdir "Test Path" $ ll | grep Test drwxr-xr-x 2 ghurrell ghurrell - 68 26 Feb 11:43 Test Path/ $ cd Test+Path $ pwd /Users/ghurrell/Test Path
So bash knows that "+" can signify space.
$ mkdir "Test+Path" $ ll | grep Test drwxr-xr-x 2 ghurrell ghurrell - 68 26 Feb 11:44 Test+Path/ $ cd "Test Path" $ pwd /Users/ghurrell/Test+Path
And it also knows that space can signify "+".
And if I create two identical folders, "Test Dir" and "Test+Dir", and try to "cd" into one of them then Bash just interprets the space or the "+" literally and I wind up in the appropriate folder.
Thanks once again for all your help, Best wishes, Greg Hurrell
