> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> It is not a complicated thing. I'm sure you will be able to
Asger> figure out how to do it in half an hour.
You mean that you want _me_ to do it? Ha!
Asger> I'm not fanatic, and I don't think this problem is such a big
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > While routine use of catcode magic counts as brain damage, all spaces take is
| > teeling TeX that space is a letter or other character. the scope of which can
| > be bracketed by a group. For example one could write
| >
| > {\aftergro
> While routine use of catcode magic counts as brain damage, all spaces take is
> teeling TeX that space is a letter or other character. the scope of which can
> be bracketed by a group. For example one could write
>
> {\aftergroup\input\catcode` =12\aftergroup{File name with spaces}}
We shoul
> Most applications keep a "recently used files" list (meaning that LyX
> should update its own list...). Remember that you want to code this
> feature for really dumb users (who can't rename themselves). So any
> small glitch in other applications is a big problem for them.
There will not be any
While routine use of catcode magic counts as brain damage, all spaces take is
teeling TeX that space is a letter or other character. the scope of which can
be bracketed by a group. For example one could write
{\aftergroup\input\catcode` =12\aftergroup{File name with spaces}}
which works becau
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> That's what a windows application would do. And then this will
>> break many other applications which work in the same directory.
Asger> No. It will only break applications with that rely on
Asger> directories names not to c
> That's what a windows application would do. And then this will break
> many other applications which work in the same directory.
No. It will only break applications with that rely on directories names
not to change. Which applications require this? For sure, LyX does not.
> You should now t
> "Duncan" == Duncan Simpson <[EMAIL PROTECTED]> writes:
Duncan> If LyX is going to detect and do special magic to deal with
Duncan> file names with natsty character like spaces in them, then the
Duncan> current suggestions are IMHO the wrong thing. File names with
Duncan> spaces, and practic
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Forgive me if I'm wrong, but doesn't lyx work from a temporary
Angus> directory? Why not create sym-links in this temporary directory
Angus> to all include/accessed/used files and then do the export to
Angus> TeX etc also in the tmp
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> "Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
>>
>> | What's wrong with offering to rename the directory?
>>
>> That you suddenly might break all the other programs that used this
>> dir without your knowledge?
As
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | > present).
Lars> Won't this always work irrespective of the names given by the
Lars> user ro | > his files? | | I use: | | \use_tempdir false | | So,
Lars> no. It's not guarante
If LyX is going to detect and do special magic to deal with file names with
natsty character like spaces in them, then the current suggestions are IMHO
the wrong thing. File names with spaces, and practically anything else, can be
made to work with catcode magic (see the TeXbook).
While it wo
> "Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
>
> | What's wrong with offering to rename the directory?
>
> That you suddenly might break all the other programs that used this
> dir without your knowledge?
As long as it is the choice of the user, I don't see the
problem.
To make t
On Thu, 29 Jun 2000, Asger K. Alstrup Nielsen wrote:
[Spaces in directories]
>
>
> I do not like the linking idea, since it's not portable.
>
I was wondering how that was going to work when someone compiled LyX to run on
a wind*ws machine with an x-emulator or the sort.
> However, a dialog th
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| What's wrong with offering to rename the directory?
That you suddenly might break all the other programs that used this
dir without your knowledge?
Lgb
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| > present). Won't this always work irrespective of the names given by the user ro
| > his files?
|
| I use:
|
| \use_tempdir false
|
| So, no. It's not guaranteed that LyX works in a temp directory.
And if we do it right we can remove that swit
I wrote:
> Asger> the user is in order. Potentially, it could even offer to do
> Asger> the renaming for the user.
Jean-Marc was pissed:
> and LyX renames "Work Dir" to "Work_Dir" behind my back, I will be
> really pissed off, I think
Please read what I wrote, before you are pissed off.
To help
>
> Forgive me if I'm wrong, but doesn't lyx work from a temporary directory? Why
> not create sym-links in this temporary directory to all include/accessed/used
> files and then do the export to TeX etc also in the tmp directory (as at
> present). Won't this always work irrespective of the names
Angus Leeming <[EMAIL PROTECTED]> writes:
| Forgive me if I'm wrong, but doesn't lyx work from a temporary directory? Why
| not create sym-links in this temporary directory to all include/accessed/used
| files and then do the export to TeX etc also in the tmp directory (as at
| present). Won't th
JMarc> Asger> [Directory with spaces in them] However, a dialog that warned
JMarc> Asger> the user is in order. Potentially, it could even offer to do
JMarc> Asger> the renaming for the user.
JMarc> >> Rename the directory? What a strange idea...
JMarc> Asger> What's strange about that?
JMarc>
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> [Directory with spaces in them] However, a dialog that warned
Asger> the user is in order. Potentially, it could even offer to do
Asger> the renaming for the user.
>> Rename the directory? What a strange idea...
Asger>
[Directory with spaces in them]
> Asger> However, a dialog that warned the user is in order.
> Asger> Potentially, it could even offer to do the renaming for the
> Asger> user.
>
> Rename the directory? What a strange idea...
What's strange about that?
Is the file system a sacred thing that we
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> "Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes: | I do not
Lars> like the linking idea, since it's not portable.
Lars> "linking" is portable if you create the link every time you need
Lars> access to that file. Then for
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| I do not like the linking idea, since it's not portable.
"linking" is portable if you create the link every time you need
access to that file. Then for fs's that supports symbolic links use
that, hardlinks use that, copy the file use that.
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> [Spaces in directories] Since it's "only" LaTeX that can't
Asger> handle this, we should not disallow spaces in directories in
Asger> general. For instance, it's entirely possible that DocBook
Asger> handles spaces perfec
[Spaces in directories]
Since it's "only" LaTeX that can't handle this, we should not disallow
spaces in directories in general. For instance, it's entirely possible
that DocBook handles spaces perfectly.
Therefore, any measures to circumvent or diagnose the problem should be
specific to the tool
On Mon, 26 Jun 2000, Jean-Marc Lasgouttes wrote:
> > "edscott" == edscott <[EMAIL PROTECTED]> writes:
> edscott> What does occur in 1.1.4 (and repeats itself in 1.1.5) is
> edscott> that input files which reside in directories with spaces
> edscott> (like: /blabla/blabla/chapter 1) will confu
27 matches
Mail list logo
