On Wed, Sep 24, 2003 at 12:19:05AM +, Angus Leeming wrote:
On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
Under Cygwin, LyX already attempts to fix the path (for all exported
files, paths to pictures, etc). The fix is to output the Windows name
(e.g.
Kayvan A. Sylvan wrote:
No. It produced garbage for the graphics name. I have attached the tex
files (from the LyX temp directory).
The difficulties of writing code without being able to test it out...
I am going to go back to my hack, since it works correctly.
Fair enough. We let this drop
James Frye [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On Tue, 23 Sep 2003, Bruce wrote:
Or perhaps you meant that the fact that a computer has directories with
spaces in their names indicates there may be a bug in the brain of the
individual who created it? That I will acknowledge
On Wed, Sep 24, 2003 at 12:19:05AM +, Angus Leeming wrote:
On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
Under Cygwin, LyX already attempts to fix the path (for all exported
files, paths to pictures, etc). The fix is to output the Windows name
(e.g.
Kayvan A. Sylvan wrote:
No. It produced garbage for the graphics name. I have attached the tex
files (from the LyX temp directory).
The difficulties of writing code without being able to test it out...
I am going to go back to my hack, since it works correctly.
Fair enough. We let this drop
James Frye [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On Tue, 23 Sep 2003, Bruce wrote:
Or perhaps you meant that the fact that a computer has directories with
spaces in their names indicates there may be a bug in the brain of the
individual who created it? That I will acknowledge
On Wed, Sep 24, 2003 at 12:19:05AM +, Angus Leeming wrote:
> On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
> > Under Cygwin, LyX already attempts to fix the path (for all exported
> > files, paths to pictures, etc). The fix is to output the Windows name
> > (e.g.
Kayvan A. Sylvan wrote:
> No. It produced garbage for the graphics name. I have attached the tex
> files (from the LyX temp directory).
The difficulties of writing code without being able to test it out...
> I am going to go back to my hack, since it works correctly.
Fair enough. We let this
James Frye <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> On Tue, 23 Sep 2003, Bruce wrote:
>
>> Or perhaps you meant that the fact that a computer has directories with
>> spaces in their names indicates there may be a bug in the brain of the
>> individual who created it? That I will
Paul == Paul A Rubin [EMAIL PROTECTED] writes:
Paul That those of us using Windows (not all voluntarily, I might
Paul add) do have to make accommodations (such as renaming
Paul directories, or adding symbolic links) to use LyX (and, for that
Paul matter, most any software ported from Unix-like
On Tue, 23 Sep 2003, John Levon wrote:
This is not how things work. PROGRA~1 is most definitely NOT the
real filename.
Well, that gets us into philosophical discussions about the nature of
reality :-) What I know ('cause I just tried it) is that if I open a
basic command-line prompt window on
James Frye wrote:
Well, that gets us into philosophical discussions about the nature of
reality :-) What I know ('cause I just tried it) is that if I open a
basic command-line prompt window on Win 2K, and do a dir \progra~1, I
get expected output from the dir command. If instead I do dir
On Tue, 23 Sep 2003, James Frye wrote:
On Tue, 23 Sep 2003, John Levon wrote:
This is not how things work. PROGRA~1 is most definitely NOT the
real filename.
Well, that gets us into philosophical discussions about the nature of
reality :-) What I know ('cause I just tried it) is that
[posted and mailed]
James Frye [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On Tue, 23 Sep 2003, John Levon wrote:
This is not how things work. PROGRA~1 is most definitely NOT the
real filename.
Well, that gets us into philosophical discussions about the nature of
reality :-)
Angus Leeming [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
Having said that, if you (that's a collective you, I guess) can
provide us with a cast-iron prescription to obtain the 8.3 version of
the name from its pretty-printing wrapper, then you may all just be in
luck. Does Win32 have
On Tue, 23 Sep 2003, [ISO-8859-1] Christian Ridderström wrote:
This behaviour is actually identical to *nix shells, you have to quote the
argument... for instance by doing:
dir \program files
The reason that you get two File Not Found is because you're trying to
list '\program' and
On Tue, 23 Sep 2003, James Frye wrote:
Guess we must have learned *nix from different sources, then. IIRC - it
has been a couple of decades - not using characters such as , , , or
space was one of the basic Intro to Unix things.
Well... I wouldn't recommend it in an introduction ;-)
And it
On 2003-09-23, 19:42 GMT, James Frye wrote:
Guess we must have learned *nix from different sources, then. IIRC - it
has been a couple of decades - not using characters such as , , , or
space was one of the basic Intro to Unix things. Though as you learn
more (or make more mistakes), you
Paul A. Rubin wrote:
Angus Leeming [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
Having said that, if you (that's a collective you, I guess) can
provide us with a cast-iron prescription to obtain the 8.3 version of
the name from its pretty-printing wrapper, then you may all just be in
On Tue, Sep 23, 2003 at 11:24:51PM +, Angus Leeming wrote:
Could you (or indeed anyone else with access to a compiler environment on a
Win32 box) write and test the equivalent function?
I'd imagine it would be something like
size_t const size =
On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
Under Cygwin, LyX already attempts to fix the path (for all exported
files, paths to pictures, etc). The fix is to output the Windows name
(e.g. C:/Cygwin/Home/Kayvan/foo.lyx) for all file references.
Well, apart from the final
Seeing as I started this thread, may as well wade in with my strictly
non-technical end user perspective ...
On Mon, Sep 22, 2003 at 01:48:42PM -0500, Les Denham wrote:
As far as I know, Windows is the only significant operating system which
allows spaces in file and directory names.
On Wed, Sep 24, 2003 at 12:19:05AM +, Angus Leeming wrote:
On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
Under Cygwin, LyX already attempts to fix the path (for all exported
files, paths to pictures, etc). The fix is to output the Windows name
(e.g.
Paul == Paul A Rubin [EMAIL PROTECTED] writes:
Paul That those of us using Windows (not all voluntarily, I might
Paul add) do have to make accommodations (such as renaming
Paul directories, or adding symbolic links) to use LyX (and, for that
Paul matter, most any software ported from Unix-like
On Tue, 23 Sep 2003, John Levon wrote:
This is not how things work. PROGRA~1 is most definitely NOT the
real filename.
Well, that gets us into philosophical discussions about the nature of
reality :-) What I know ('cause I just tried it) is that if I open a
basic command-line prompt window on
James Frye wrote:
Well, that gets us into philosophical discussions about the nature of
reality :-) What I know ('cause I just tried it) is that if I open a
basic command-line prompt window on Win 2K, and do a dir \progra~1, I
get expected output from the dir command. If instead I do dir
On Tue, 23 Sep 2003, James Frye wrote:
On Tue, 23 Sep 2003, John Levon wrote:
This is not how things work. PROGRA~1 is most definitely NOT the
real filename.
Well, that gets us into philosophical discussions about the nature of
reality :-) What I know ('cause I just tried it) is that
[posted and mailed]
James Frye [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On Tue, 23 Sep 2003, John Levon wrote:
This is not how things work. PROGRA~1 is most definitely NOT the
real filename.
Well, that gets us into philosophical discussions about the nature of
reality :-)
Angus Leeming [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
Having said that, if you (that's a collective you, I guess) can
provide us with a cast-iron prescription to obtain the 8.3 version of
the name from its pretty-printing wrapper, then you may all just be in
luck. Does Win32 have
On Tue, 23 Sep 2003, [ISO-8859-1] Christian Ridderström wrote:
This behaviour is actually identical to *nix shells, you have to quote the
argument... for instance by doing:
dir \program files
The reason that you get two File Not Found is because you're trying to
list '\program' and
On Tue, 23 Sep 2003, James Frye wrote:
Guess we must have learned *nix from different sources, then. IIRC - it
has been a couple of decades - not using characters such as , , , or
space was one of the basic Intro to Unix things.
Well... I wouldn't recommend it in an introduction ;-)
And it
On 2003-09-23, 19:42 GMT, James Frye wrote:
Guess we must have learned *nix from different sources, then. IIRC - it
has been a couple of decades - not using characters such as , , , or
space was one of the basic Intro to Unix things. Though as you learn
more (or make more mistakes), you
Paul A. Rubin wrote:
Angus Leeming [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
Having said that, if you (that's a collective you, I guess) can
provide us with a cast-iron prescription to obtain the 8.3 version of
the name from its pretty-printing wrapper, then you may all just be in
On Tue, Sep 23, 2003 at 11:24:51PM +, Angus Leeming wrote:
Could you (or indeed anyone else with access to a compiler environment on a
Win32 box) write and test the equivalent function?
I'd imagine it would be something like
size_t const size =
On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
Under Cygwin, LyX already attempts to fix the path (for all exported
files, paths to pictures, etc). The fix is to output the Windows name
(e.g. C:/Cygwin/Home/Kayvan/foo.lyx) for all file references.
Well, apart from the final
Seeing as I started this thread, may as well wade in with my strictly
non-technical end user perspective ...
On Mon, Sep 22, 2003 at 01:48:42PM -0500, Les Denham wrote:
As far as I know, Windows is the only significant operating system which
allows spaces in file and directory names.
On Wed, Sep 24, 2003 at 12:19:05AM +, Angus Leeming wrote:
On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
Under Cygwin, LyX already attempts to fix the path (for all exported
files, paths to pictures, etc). The fix is to output the Windows name
(e.g.
> "Paul" == Paul A Rubin <[EMAIL PROTECTED]> writes:
Paul> That those of us using Windows (not all voluntarily, I might
Paul> add) do have to make accommodations (such as renaming
Paul> directories, or adding symbolic links) to use LyX (and, for that
Paul> matter, most any software ported
On Tue, 23 Sep 2003, John Levon wrote:
> This is not how things work. "PROGRA~1" is most definitely NOT the
> "real filename".
Well, that gets us into philosophical discussions about the nature of
reality :-) What I know ('cause I just tried it) is that if I open a
basic command-line prompt
James Frye wrote:
> Well, that gets us into philosophical discussions about the nature of
> reality :-) What I know ('cause I just tried it) is that if I open a
> basic command-line prompt window on Win 2K, and do a "dir \progra~1", I
> get expected output from the dir command. If instead I do
On Tue, 23 Sep 2003, James Frye wrote:
> On Tue, 23 Sep 2003, John Levon wrote:
>
> > This is not how things work. "PROGRA~1" is most definitely NOT the
> > "real filename".
>
> Well, that gets us into philosophical discussions about the nature of
> reality :-) What I know ('cause I just tried
[posted and mailed]
James Frye <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> On Tue, 23 Sep 2003, John Levon wrote:
>
>> This is not how things work. "PROGRA~1" is most definitely NOT the
>> "real filename".
>
> Well, that gets us into philosophical discussions about the nature of
>
Angus Leeming <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> Having said that, if you (that's a collective you, I guess) can
> provide us with a cast-iron prescription to obtain the 8.3 version of
> the name from its pretty-printing wrapper, then you may all just be in
> luck. Does Win32
On Tue, 23 Sep 2003, [ISO-8859-1] Christian Ridderström wrote:
> This behaviour is actually identical to *nix shells, you have to quote the
> argument... for instance by doing:
> dir "\program files"
>
> The reason that you get two "File Not Found" is because you're trying to
> list
On Tue, 23 Sep 2003, James Frye wrote:
> Guess we must have learned *nix from different sources, then. IIRC - it
> has been a couple of decades - not using characters such as <, >, &, or
> space was one of the basic "Intro to Unix" things.
Well... I wouldn't recommend it in an introduction ;-)
On 2003-09-23, 19:42 GMT, James Frye wrote:
> Guess we must have learned *nix from different sources, then. IIRC - it
> has been a couple of decades - not using characters such as <, >, &, or
> space was one of the basic "Intro to Unix" things. Though as you learn
> more (or make more mistakes),
Paul A. Rubin wrote:
> Angus Leeming <[EMAIL PROTECTED]> wrote in
> news:[EMAIL PROTECTED]:
>
>> Having said that, if you (that's a collective you, I guess) can
>> provide us with a cast-iron prescription to obtain the 8.3 version of
>> the name from its pretty-printing wrapper, then you may all
On Tue, Sep 23, 2003 at 11:24:51PM +, Angus Leeming wrote:
>
> Could you (or indeed anyone else with access to a compiler environment on a
> Win32 box) write and test the equivalent function?
>
> I'd imagine it would be something like
>
> size_t const size =
>
On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
> Under Cygwin, LyX already attempts to fix the path (for all exported
> files, paths to pictures, etc). The fix is to output the Windows name
> (e.g. "C:/Cygwin/Home/Kayvan/foo.lyx") for all file references.
Well, apart from the
Seeing as I started this thread, may as well wade in with my strictly
non-technical end user perspective ...
> On Mon, Sep 22, 2003 at 01:48:42PM -0500, Les Denham wrote:
>> As far as I know, Windows is the only significant operating system which
>> allows spaces in file and directory names.
>
On Wed, Sep 24, 2003 at 12:19:05AM +, Angus Leeming wrote:
> On Tuesday 23 September 2003 10:53 pm, Kayvan A. Sylvan wrote:
> > Under Cygwin, LyX already attempts to fix the path (for all exported
> > files, paths to pictures, etc). The fix is to output the Windows name
> > (e.g.
James Frye [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On Thu, 18 Sep 2003, Bruce wrote:
I get this message when try to preview a file that (suprise) is in a
directory that has spaces in its name.
Not that this is a huge deal, I'm just curious... why is this?
There's an obvious
On Monday 22 September 2003 13:40, Paul A. Rubin wrote:
Sounds right for *nix, but spaces in paths are a way of life in the
Windoze world (not sure about Macs, but I think they're legal there,
too).
Any software which allows commands with arguments has to have some way of
separating commands
Paul A. Rubin wrote:
Sounds right for *nix, but spaces in paths are a way of life in the
Windoze world (not sure about Macs, but I think they're legal there,
too).
And your point is?
LyX could happily support spaces in paths. However, it farms out all the
'hard' work to other utilities.
Angus Leeming [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
Paul A. Rubin wrote:
Sounds right for *nix, but spaces in paths are a way of life in the
Windoze world (not sure about Macs, but I think they're legal there,
too).
And your point is?
That those of us using Windows (not all
On Mon, 22 Sep 2003, Paul A. Rubin wrote:
Angus Leeming [EMAIL PROTECTED] wrote in
That those of us using Windows (not all voluntarily, I might add) do have
to make accommodations (such as renaming directories, or adding symbolic
links) to use LyX (and, for that matter, most any software
On Mon, Sep 22, 2003 at 04:18:38PM -0700, James Frye wrote:
Which I suppose was really my point: The universe in which I think most
Lyx users spend most of their time is one in which simple, sensible
software is a desirable goal. The rule about filenames not containing
spaces is there for a
On 2003-09-22, 23:18 GMT, James Frye wrote:
For that matter, even in Windows the real filenames don't contain
spaces. Rather, each file has a name which follows the 8.3 rule, and
a text label that can be used instead. That label may contain spaces
(and be quite long), but the filename
On Mon, Sep 22, 2003 at 07:35:55PM -0400, Matej Cepl wrote:
On 2003-09-22, 23:18 GMT, James Frye wrote:
For that matter, even in Windows the real filenames don't contain
spaces. Rather, each file has a name which follows the 8.3 rule, and
a text label that can be used instead. That label
James Frye [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On Thu, 18 Sep 2003, Bruce wrote:
I get this message when try to preview a file that (suprise) is in a
directory that has spaces in its name.
Not that this is a huge deal, I'm just curious... why is this?
There's an obvious
On Monday 22 September 2003 13:40, Paul A. Rubin wrote:
Sounds right for *nix, but spaces in paths are a way of life in the
Windoze world (not sure about Macs, but I think they're legal there,
too).
Any software which allows commands with arguments has to have some way of
separating commands
Paul A. Rubin wrote:
Sounds right for *nix, but spaces in paths are a way of life in the
Windoze world (not sure about Macs, but I think they're legal there,
too).
And your point is?
LyX could happily support spaces in paths. However, it farms out all the
'hard' work to other utilities.
Angus Leeming [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
Paul A. Rubin wrote:
Sounds right for *nix, but spaces in paths are a way of life in the
Windoze world (not sure about Macs, but I think they're legal there,
too).
And your point is?
That those of us using Windows (not all
On Mon, 22 Sep 2003, Paul A. Rubin wrote:
Angus Leeming [EMAIL PROTECTED] wrote in
That those of us using Windows (not all voluntarily, I might add) do have
to make accommodations (such as renaming directories, or adding symbolic
links) to use LyX (and, for that matter, most any software
On Mon, Sep 22, 2003 at 04:18:38PM -0700, James Frye wrote:
Which I suppose was really my point: The universe in which I think most
Lyx users spend most of their time is one in which simple, sensible
software is a desirable goal. The rule about filenames not containing
spaces is there for a
On 2003-09-22, 23:18 GMT, James Frye wrote:
For that matter, even in Windows the real filenames don't contain
spaces. Rather, each file has a name which follows the 8.3 rule, and
a text label that can be used instead. That label may contain spaces
(and be quite long), but the filename
On Mon, Sep 22, 2003 at 07:35:55PM -0400, Matej Cepl wrote:
On 2003-09-22, 23:18 GMT, James Frye wrote:
For that matter, even in Windows the real filenames don't contain
spaces. Rather, each file has a name which follows the 8.3 rule, and
a text label that can be used instead. That label
James Frye <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> On Thu, 18 Sep 2003, Bruce wrote:
>
>> I get this message when try to preview a file that (suprise) is in a
>> directory that has spaces in its name.
>>
>> Not that this is a huge deal, I'm just curious... why is this?
>
>
On Monday 22 September 2003 13:40, Paul A. Rubin wrote:
> Sounds right for *nix, but spaces in paths are a way of life in the
> Windoze world (not sure about Macs, but I think they're legal there,
> too).
Any software which allows commands with arguments has to have some way of
separating
Paul A. Rubin wrote:
> Sounds right for *nix, but spaces in paths are a way of life in the
> Windoze world (not sure about Macs, but I think they're legal there,
> too).
And your point is?
LyX could happily support spaces in paths. However, it farms out all the
'hard' work to other utilities.
Angus Leeming <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> Paul A. Rubin wrote:
>> Sounds right for *nix, but spaces in paths are a way of life in the
>> Windoze world (not sure about Macs, but I think they're legal there,
>> too).
>
> And your point is?
That those of us using
On Mon, 22 Sep 2003, Paul A. Rubin wrote:
> Angus Leeming <[EMAIL PROTECTED]> wrote in
>
> That those of us using Windows (not all voluntarily, I might add) do have
> to make accommodations (such as renaming directories, or adding symbolic
> links) to use LyX (and, for that matter, most any
On Mon, Sep 22, 2003 at 04:18:38PM -0700, James Frye wrote:
> Which I suppose was really my point: The universe in which I think most
> Lyx users spend most of their time is one in which simple, sensible
> software is a desirable goal. The rule about filenames not containing
> spaces is there
On 2003-09-22, 23:18 GMT, James Frye wrote:
> For that matter, even in Windows the real filenames don't contain
> spaces. Rather, each file has a name which follows the 8.3 rule, and
> a text label that can be used instead. That label may contain spaces
> (and be quite long), but the filename
On Mon, Sep 22, 2003 at 07:35:55PM -0400, Matej Cepl wrote:
> On 2003-09-22, 23:18 GMT, James Frye wrote:
> > For that matter, even in Windows the real filenames don't contain
> > spaces. Rather, each file has a name which follows the 8.3 rule, and
> > a text label that can be used instead. That
On Thu, 18 Sep 2003, Bruce wrote:
I get this message when try to preview a file that (suprise) is in a
directory that has spaces in its name.
Not that this is a huge deal, I'm just curious... why is this?
There's an obvious answer: file and directory names should NEVER contain
spaces. If
On Thu, 18 Sep 2003, Bruce wrote:
I get this message when try to preview a file that (suprise) is in a
directory that has spaces in its name.
Not that this is a huge deal, I'm just curious... why is this?
There's an obvious answer: file and directory names should NEVER contain
spaces. If
On Thu, 18 Sep 2003, Bruce wrote:
> I get this message when try to preview a file that (suprise) is in a
> directory that has spaces in its name.
>
> Not that this is a huge deal, I'm just curious... why is this?
There's an obvious answer: file and directory names should NEVER contain
spaces.
(I sent this message last week, and though received no error message it
didn't seem to make it to the list (or at least not to the archive).
Apologies if it is a duplicate.)
___
I get this message when try to preview a file that (suprise) is in a
directory that has spaces in its
On Thu, Sep 18, 2003 at 11:54:46AM -0400, Bruce wrote:
(I sent this message last week, and though received no error message it
didn't seem to make it to the list (or at least not to the archive).
Apologies if it is a duplicate.)
As I seem to remember having answered it probably made it
Bruce [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
(I sent this message last week, and though received no error message
it didn't seem to make it to the list (or at least not to the
archive). Apologies if it is a duplicate.)
___
I get this message when try to preview a
At 20:49 18.09.2003 +, Paul A. Rubin wrote:
Not sure how to handle this if you're using the native Win32 port of LyX,
I solved it by installing the other software in simple pathes for a second
time. Should be the fastest solution.
Regards
M.
--
http://www.logies.de/ (u. a. _die_
(I sent this message last week, and though received no error message it
didn't seem to make it to the list (or at least not to the archive).
Apologies if it is a duplicate.)
___
I get this message when try to preview a file that (suprise) is in a
directory that has spaces in its
On Thu, Sep 18, 2003 at 11:54:46AM -0400, Bruce wrote:
(I sent this message last week, and though received no error message it
didn't seem to make it to the list (or at least not to the archive).
Apologies if it is a duplicate.)
As I seem to remember having answered it probably made it
Bruce [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
(I sent this message last week, and though received no error message
it didn't seem to make it to the list (or at least not to the
archive). Apologies if it is a duplicate.)
___
I get this message when try to preview a
At 20:49 18.09.2003 +, Paul A. Rubin wrote:
Not sure how to handle this if you're using the native Win32 port of LyX,
I solved it by installing the other software in simple pathes for a second
time. Should be the fastest solution.
Regards
M.
--
http://www.logies.de/ (u. a. _die_
(I sent this message last week, and though received no error message it
didn't seem to make it to the list (or at least not to the archive).
Apologies if it is a duplicate.)
___
I get this message when try to preview a file that (suprise) is in a
directory that has spaces in its
> On Thu, Sep 18, 2003 at 11:54:46AM -0400, Bruce wrote:
>> (I sent this message last week, and though received no error message it
>> didn't seem to make it to the list (or at least not to the archive).
>> Apologies if it is a duplicate.)
>
> As I seem to remember having answered it probably made
"Bruce" <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> (I sent this message last week, and though received no error message
> it didn't seem to make it to the list (or at least not to the
> archive). Apologies if it is a duplicate.)
> ___
>
>
> I get this message when try
At 20:49 18.09.2003 +, Paul A. Rubin wrote:
Not sure how to handle this if you're using the native Win32 port of LyX,
I solved it by installing the other software in simple pathes for a second
time. Should be the fastest solution.
Regards
M.
--
http://www.logies.de/ (u. a. _die_
90 matches
Mail list logo
