Stephen Harris wrote:
German doesn't have a problem with spaces by default
because Programme doesn't have any spaces in it.
Therefore C:\programme\lyx or C:\programme\miktex
will not have a space in it.
Beginning with WindowsXPx64 Microsoft only delivers native OS versions
for english and jap
- Original Message -
From: "Bo Peng" <[EMAIL PROTECTED]>
To:
Cc:
Sent: Monday, January 02, 2006 4:41 PM
Subject: Re: [announce] sixth release of LyXWinInstaller
Dear all,
It is confirmed that if the .bst file is in a path without space, the
bibliography will be generated correctly,
This is not something I really expected to work, with gcc 4.1 being
a work in progress. Still, if someone is interested,
here is what happened:
In file included from ../../boost/boost/config.hpp:35,
from ../../boost/boost/bind.hpp:23,
from ../../src/support/trans
Dear all,
It is confirmed that if the .bst file is in a path without space, the
bibliography will be generated correctly, even if lyx is installed
under c:\program files\lyx. So,
1. It is safe to install lyx to c:\program files,
2. It is not safe to put .bst files in a path with spaces. .lyx file
Angus Leeming a écrit :
Abdel wrote:
your row signature patch is excellent as it reduces screen flickering
significantly (you could the flicking on Windows with qtwin).
FYI, without this patch (I have not update my cvs yet), my Qt4 port has
zero flickering :-)
Right. Because Qt4 double buffer
Stephen Harris wrote:
>> Right. And since I install at C:\Program Files\LyX and the bloody thing
>> works for me, I'm going to put on my grumpy old man hat and say it's a
>> "user error" to try and use a .bst file in a path with spaces.
> And to think, just last night it was a party hat.
The mood
Abdel wrote:
>> your row signature patch is excellent as it reduces screen flickering
>> significantly (you could the flicking on Windows with qtwin).
>
> FYI, without this patch (I have not update my cvs yet), my Qt4 port has
> zero flickering :-)
Right. Because Qt4 double buffers everything.
>
Michael Gerz a écrit :
Martin,
your row signature patch is excellent as it reduces screen flickering
significantly (you could the flicking on Windows with qtwin).
FYI, without this patch (I have not update my cvs yet), my Qt4 port has
zero flickering :-)
I think this patch is solving here a
- Original Message -
From: "Angus Leeming" <[EMAIL PROTECTED]>
To:
Cc:
Sent: Monday, January 02, 2006 10:21 AM
Subject: Re: [announce] sixth release of LyXWinInstaller
Michael Gerz wrote:
Bo Peng wrote:
The mistake is making C:\Program files the default for LyX and
friends.
- Original Message -
From: "Michael Gerz" <[EMAIL PROTECTED]>
To: "Bo Peng" <[EMAIL PROTECTED]>
Cc: "Stephen Harris" <[EMAIL PROTECTED]>; ;
Sent: Monday, January 02, 2006 10:04 AM
Subject: Re: [announce] sixth release of LyXWinInstaller
Bo Peng wrote:
The mistake is making C:\Pr
On Mon, Jan 02, 2006 at 08:26:13PM +0100, Michael Gerz wrote:
> Martin,
>
> your row signature patch is excellent as it reduces screen flickering
> significantly (you could the flicking on Windows with qtwin).
>
> However, I don't understand why we have to redraw the whole screen in
> case of s
Martin,
your row signature patch is excellent as it reduces screen flickering
significantly (you could the flicking on Windows with qtwin).
However, I don't understand why we have to redraw the whole screen in
case of selections. Doesn't your nice "always draw current row" patch
capture sele
On Mon, Jan 02, 2006 at 06:17:31PM +0200, Martin Vermeer wrote:
...
> Actually I would put it differently: you are not supposed to mix
> character styles and font attributes :-)
>
> My idea with charstyles has always been, longer term, to become a
> logical replacement for visual font attribute
Michael Gerz wrote:
> Bo Peng wrote:
>
>>>The mistake is making C:\Program files the default for LyX and
>>>friends.
>>>
>>>
>>I totally agree. I think it is a good idea to install Lyx to c:\lyx by
>>default.
>>
>>
> No, the directory must be configurable. On my (German) machine, the
> appr
Bo Peng wrote:
The mistake is making C:\Program files the default for LyX and
friends.
I totally agree. I think it is a good idea to install Lyx to c:\lyx by default.
No, the directory must be configurable. On my (German) machine, the
appropriate directory is "C:\Programme". There is n
On Monday 02 January 2006 17:41, Herbert Voss wrote:
> uuh, this causes an error!
>
> \tabular{lr}
> Jür & gen
> \endtabular
You are really a magician, splitting Jürgen in half. ;-)
> and don't forget \usepackage[latin9]{inputenc} ... :-)
We are very modest, in this case 1 is enough. ;-)
>
Juergen Spitzmueller wrote:
Martin Vermeer wrote:
Perhaps this should be called an enhancement request and get its own bug
number.
perhaps.
Now convince HIM to put the #2015-fix in ;-)
Which of them? ;-)
Lars or Gullik. Jean and Marc have already expressed their principal
accordance
Martin Vermeer wrote:
> Perhaps this should be called an enhancement request and get its own bug
> number.
perhaps.
> > Now convince HIM to put the #2015-fix in ;-)
>
> Which of them? ;-)
Lars or Gullik. Jean and Marc have already expressed their principal
accordance on bugzilla IIRC.
Jür & ge
Angus Leeming wrote:
>
> Jean-Marc contacted the real TeX gurus on the tex-k mailing list to ask
> for some advice. You can find the full thread in the tex-k archives here:
> http://www.tug.org/pipermail/tex-k/2005-April/index.html#1287
>
A bit more background:
http://sarovar.org/tracker/index.
On Mon, Jan 02, 2006 at 05:39:52PM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
...
> This sounds very reasonable to me.
> Perhaps you could add this explanation to the bug report. IIRC there is also
> another bug involved which will be fixed by your #2015-patch.
>
> I propose to
Martin Vermeer wrote:
> Actually I would put it differently: you are not supposed to mix
> character styles and font attributes :-)
>
> My idea with charstyles has always been, longer term, to become a
> logical replacement for visual font attributes. In XML they represent
> "elements"; in LaTeX my
On Mon, Jan 02, 2006 at 03:30:21PM +0200, Martin Vermeer wrote:
> On Mon, Jan 02, 2006 at 01:01:46PM +0100, Juergen Spitzmueller wrote:
> > Martin Vermeer wrote:
> > > Actually I don't dare to touch this stuff. The whole font architecture
> > > needs an overhaul/simplification. E.g., there are two
Bo Peng wrote:
>> _TeX_ cannot handle spaces. I suppose that you do not really
>> know the difference of TeX, LaTeX, pdfTeX, pdfLaTeX, bibTeX, MiKTeX
>
> I do not. My understanding is that miktex is another implementation of
> latex standard ( if there is such a standard). If miktex aims at
> win
> The mistake is making C:\Program files the default for LyX and
> friends.
I totally agree. I think it is a good idea to install Lyx to c:\lyx by default.
This will save us from some troubles, but not all. Most windows users
save their files under "...\My Documents" or "... and
Settings\Desktop"
> _TeX_ cannot handle spaces. I suppose that you do not really
> know the difference of TeX, LaTeX, pdfTeX, pdfLaTeX, bibTeX, MiKTeX
I do not. My understanding is that miktex is another implementation of
latex standard ( if there is such a standard). If miktex aims at
windows platform, I assume th
On Mon, Jan 02, 2006 at 11:41:55AM +0100, Abdel wrote:
> Helge Hafting a écrit :
> >On Fri, Dec 23, 2005 at 04:42:17PM +0100, Jean-Marc Lasgouttes wrote:
> >>>"Abdel" == Abdel <[EMAIL PROTECTED]>
> >>>writes:
> >>Abdel> Jean-Marc Lasgouttes a écrit :
> >"Abdel" == Abdel <[EMAIL PR
Angus Leeming wrote:
> When the dialog is open, clicking in the main document resets the position
> of both dialog and document to the beginning. I find that I have to use
> the dialog to naviagate to an error, close the dialog, fix the problem,
> rerun chktex and hope that I can return to the same
When the dialog is open, clicking in the main document resets the position
of both dialog and document to the beginning. I find that I have to use
the dialog to naviagate to an error, close the dialog, fix the problem,
rerun chktex and hope that I can return to the same point relatively
quickly by
On Mon, Jan 02, 2006 at 01:01:46PM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > Actually I don't dare to touch this stuff. The whole font architecture
> > needs an overhaul/simplification. E.g., there are two different
> > getFonts, one in lyxtext (for display) and one in paragrap
A Happy New Year to verybody!
Lars Gullik Bjønnes wrote:
> Michael Gerz <[EMAIL PROTECTED]>
> writes:
> | How about the first change regarding amsart-seq?
>
> If it is only a label change then it should not be changed now. If it
> OTOH fixes a real problem, then we should fix it now.
It fixes a
Bennett Helm wrote:
>> 1. One for the Mac users: where is the "preferences" file to be found?
>> Currently I have:
> It's at ~/Library/Application Support/LyX/preferences.
Thanks, Bennett
--
Angus
Stephen Harris wrote:
> Bo
>
> The Miktex installation doc recommends installing Miktex into paths
> and/or directories without spaces. LyX has a history of problems
> with paths having spaces some passed on from Miktex.
>
> http://wiki.lyx.org/pmwiki.php/Windows/LyX136pre
> 13 July 2005
> Axel R
Martin Vermeer wrote:
> Actually I don't dare to touch this stuff. The whole font architecture
> needs an overhaul/simplification. E.g., there are two different
> getFonts, one in lyxtext (for display) and one in paragraph (for
> latexing).
If it is too complicated or risky to fix this stuff now,
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > > I think bug 2019 deserves your special attendance.
> >
> > Hmmm... perhaps the remark in insetcharstyle.C:draw:
> >
> > // I don't understand why the above .reduce and .realize aren't
> > //needed, o
On Monday 02 January 2006 10:15, Martin Vermeer wrote:
> That having been said, obviously *some* font attributes should appear
> both on-screen and in output. My understanding was that, for LaTeX use,
> charstyles were for things like Emph and Noun. They should not use
> any coloured representation
Juergen Spitzmueller wrote:
> Jean-Marc Lasgouttes wrote:
> > I'm very glad that you found the
> > cause, but the fix doesn't look
> > right.
>
> Too bad. Then I am at my witness end.
I have tried to enhance my witness a bit this year. Here's how I understand
this case:
After DEPM, doRecordUndo
Helge Hafting a écrit :
On Fri, Dec 23, 2005 at 04:42:17PM +0100, Jean-Marc Lasgouttes wrote:
"Abdel" == Abdel <[EMAIL PROTECTED]> writes:
Abdel> Jean-Marc Lasgouttes a écrit :
"Abdel" == Abdel <[EMAIL PROTECTED]>
writes:
Abdel> Oups, I have just discovered the math and table bars right
Abde
On Monday 02 January 2006 02:32, Lars Gullik Bjønnes wrote:
>
> Does it actually say 'voil' or is my mailreader/terminal a bit off?
I see "voilà"... So probably some encoding mess from your mailreader. :-)
:-)
--
José Abílio
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > > I think bug 2019 deserves your special attendance.
> >
> > Hmmm... perhaps the remark in insetcharstyle.C:draw:
> >
> > // I don't understand why the above .reduce and .realize aren't
> > //needed, o
On Fri, Dec 23, 2005 at 04:42:17PM +0100, Jean-Marc Lasgouttes wrote:
> > "Abdel" == Abdel <[EMAIL PROTECTED]> writes:
>
> Abdel> Jean-Marc Lasgouttes a écrit :
> >>> "Abdel" == Abdel <[EMAIL PROTECTED]>
> >>> writes:
> Abdel> Oups, I have just discovered the math and table bars right
On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > > I think bug 2019 deserves your special attendance.
> >
> > Hmmm... perhaps the remark in insetcharstyle.C:draw:
> >
> > // I don't understand why the above .reduce and .realize aren't
> > //needed, o
Martin Vermeer wrote:
> > I think bug 2019 deserves your special attendance.
>
> Hmmm... perhaps the remark in insetcharstyle.C:draw:
>
> // I don't understand why the above .reduce and .realize aren't
> //needed, or even wanted, here. It just works. -- MV 10.04.2005
>
> isn't quite true... could y
On Mon, Jan 02, 2006 at 09:21:09AM +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > I believe bug 822 is fixed.
> > Is 1561 still major? Was partly fixed by Andre.
> >
> > Are these (and 2155) the only major bugs left for 1.4.0?
>
> and 1656.
I remember that this can be fixed, but i
On Mon, Jan 02, 2006 at 01:10:00AM +0100, Jean-Marc Lasgouttes wrote:
> | What is this a response to?
>
> >Your 'let's always repaint the row >with the cursor in it' patch I
> >belive.
>
> Right. My palm is not very good at
> quoting messages, sorry.
>
> JMarc
>
> --
> Lgb
For some reas
Martin Vermeer wrote:
> I believe bug 822 is fixed.
> Is 1561 still major? Was partly fixed by Andre.
>
> Are these (and 2155) the only major bugs left for 1.4.0?
and 1656.
Cf. the list of open, non-fixedintrunk bugs targeted to 1.4.0:
http://tinyurl.com/7qacq
I think bug 2019 deserves your spec
45 matches
Mail list logo
