Michael Schmitt:
>> > 2. In math mode, it is not possible to use keys "_" and "^" for
>> > subscript/superscript. I understand that "^" may be a special
case but
>> > why does "_" not work???
>>
>> lyx -dbg key
...
KeySym is Shift_L
isOK is 1
isMod is 1
isModifier true
Press key 189 text "_", asc
> 2. In math mode, it is not possible to use keys "_" and "^" for
> subscript/superscript. I understand that "^" may be a special case but
> why does "_" not work???
lyx -dbg key
...
KeySym is Shift_L
isOK is 1
isMod is 1
isModifier true
Press key 189 text "_", ascii "95"
Setting key to 189, _
KeyS
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> \input{"extra long file name"}This would cause TeX to read
Michael> the file "extra long file name.tex".
Michael> Things get a little bit complicated if you want to use the
Michael> LaTeX primitive \include. You have to write
"Michael Schmitt" <[EMAIL PROTECTED]> writes:
>> The new teTeX 3.0 has a way (or two) to handle spaces. Something like
>>\include{"My Files"}
>>
>> So probably we should drop all safety checks concerning this and just
>> include the quotes whenever LyX creates such a TeX command.
>
| That is n
Michael Schmitt <[EMAIL PROTECTED]> writes:
>
> > The new teTeX 3.0 has a way (or two) to handle spaces. Something like
> >\include{"My Files"}
> >
> > So probably we should drop all safety checks concerning this and just
> > include the quotes whenever LyX creates such a TeX command.
>
> Th
The new teTeX 3.0 has a way (or two) to handle spaces. Something like
\include{"My Files"}
So probably we should drop all safety checks concerning this and just
include the quotes whenever LyX creates such a TeX command.
That is not enough; see the following snippet from the MikTeX documentation
Andreas Vox wrote:
>> Can you be more explicit? What fails? If LyX is refusing to do
>> something, can you track down the place in the code? (I've only got so
>> much time, y'know...)
>
> Something like this (found in Exporter::Export())
>
> } else if (contains(buffer->filePath(), ' ')) {
> Alert
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Michael Schmitt wrote:
> > 1. The fact that paths to documents are not allowed to contain spaces is
> > a big problem on the Windows platform. This restriction implies that all
> > Non-Administrators (i.e., users that cannot escape from their "Documen
On Sun, Feb 13, 2005 at 08:51:37PM +, Angus Leeming wrote:
> Michael Schmitt wrote:
> > 2. In math mode, it is not possible to use keys "_" and "^" for
> > subscript/superscript. I understand that "^" may be a special case but
> > why does "_" not work???
>
> lyx -dbg key
Michael, wh
Michael Schmitt wrote:
> 1. The fact that paths to documents are not allowed to contain spaces is
> a big problem on the Windows platform. This restriction implies that all
> Non-Administrators (i.e., users that cannot escape from their "Documents
> and Settings" environment cannot use LyX :-( I wo
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> 1. The fact that paths to documents are not allowed to
Michael> contain spaces is a big problem on the Windows platform. This
Michael> restriction implies that all Non-Administrators (i.e., users
Michael> that cannot escape fr
Dear Angus,
here are some initial comments on LyX/Win:
1. The fact that paths to documents are not allowed to contain spaces is a
big problem on the Windows platform. This restriction implies that all
Non-Administrators (i.e., users that cannot escape from their "Documents and
Settings" environm
12 matches
Mail list logo
