On Tue, Mar 16, 2004 at 03:47:50PM +0100, Jean-Marc Lasgouttes wrote:
For some time, I have been annoyed by the fact that, when I load a
file in lyx 1.4.0cvs, it appears in a random color. While the visual
effect is probably the consequence of a nonunititalized variable on my
particular
Georg Baum wrote:
I think the problematic case was something like
file foo1.lyx inputs dir1/foo2.lyx
file dir1/foo2.lyx inputs dir1/dir2/foo3.lyx
file dir1/dir2/foo3.lyx uses graphics graph.eps (in dir1/dir2)
the \includegraphics for graph.eps should read
On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
...reliably, any inset type, when opening the Document Settings
dialog, changing something and pressing OK/Apply.
Anybody else seeing this?
- Martin
pgp0.pgp
Description: PGP signature
Angus Leeming wrote:
So, can I summarise the requirement?
// If this is a child document and the parent is
// already loaded, then define 'base' as parent.base().
// If the parent is also a child, then it would return
// its own 'base'.
string base;
if
Kuba Ober wrote:
Thanks a lot!! I was looking forward to that.
Not very usable ATM, though. Floats are still broken (I tried to fix it, with
no success). That's why I was holding it back until now. But I have the
feeling that we are moving towards a feature freeze (which would be a good
Martin Vermeer wrote:
On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
...reliably, any inset type, when opening the Document Settings
dialog, changing something and pressing OK/Apply.
Anybody else seeing this?
Solved with the caveman's method.
Alfredo
?
Martin Vermeer wrote:
On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
...reliably, any inset type, when opening the Document Settings
dialog, changing something and pressing OK/Apply.
Anybody else seeing this?
Yes, confirmed. Nothing serious though, it's just that
Georg Baum wrote:
I think so.
I am not sure wether I understood you correctly, but I believe this
is exactly what
- string from_file =
params.filename.outputFilename(buffer.filePath());
+ // a relative filename should be relative to the master
buffer
+ string from_file
On Wed, Mar 17, 2004 at 11:28:08AM +0100, Alfredo Braunstein spake thusly:
Martin Vermeer wrote:
On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
...reliably, any inset type, when opening the Document Settings
dialog, changing something and pressing OK/Apply.
On Wed, Mar 17, 2004 at 11:15:05AM +0100, Juergen Spitzmueller spake thusly:
Kuba Ober wrote:
Thanks a lot!! I was looking forward to that.
Not very usable ATM, though. Floats are still broken (I tried to fix it, with
no success). That's why I was holding it back until now. But I have
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus I don't see why $$LatexName is needed. Is it still needed after
Angus Jean-Marc's Buffer::getMasterBuffer() is included in the
Angus source?
It seems to me that in some cases (when calling the script that
produces the right output, for
I retried, and still get this strange behaviour.
On 'closer' examination I get:
lilie:/home/poenitz # traceroute cvs.lyx.org
traceroute to cvs.lyx.org (80.232.38.163), 30 hops max, 40 byte packets
[...]
send failed: No buffer space available
send failed:
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus I don't see why $$LatexName is needed. Is it still needed
after Angus Jean-Marc's Buffer::getMasterBuffer() is included in
the Angus source?
It seems to me that in some cases (when calling the script
Andre Poenitz [EMAIL PROTECTED] writes:
| I retried, and still get this strange behaviour.
| On 'closer' examination I get:
| lilie:/home/poenitz # traceroute cvs.lyx.org
| traceroute to cvs.lyx.org (80.232.38.163), 30 hops max, 40 byte packets
| [...]
| send failed: No
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus I don't see why $$LatexName is needed. Is it still needed after
Angus Jean-Marc's Buffer::getMasterBuffer() is included in the
Angus source?
It seems to me that in some cases (when calling the script
Georg Baum wrote:
Of course, if the converter command was run from the master buffer
dir, the situation would be different, since $$FName would always
be the right variable to use.
This would work. I don't know very well all the capabilities of
external templates. Angus, if this does not
Hi all,
Some of you might be familiar with the poor quality of the fonts when viewing a
pdf file created from a lyx document. The fonts look pixelised and it is not
possible to mark text.
The reason for this is the
\usepackage[T1]{fontenc}
statement that lyx automatically adds to the document
On Wednesday 17 March 2004 11:18 am, Andreas wrote:
Hi all,
Some of you might be familiar with the poor quality of the fonts when
viewing a pdf file created from a lyx document. The fonts look pixelised
and it is not possible to mark text.
As a side note: This is a serious problem with
On Wed, Mar 17, 2004 at 04:05:45PM +0900, Rob Lahaye wrote:
I remember similar things happened here when I compiled with Qt.
I believe it was caused by the Qt libs which were compiled with
threads by default from the ports.
However, threads are not needed for LyX and thus LyX/Qt developers
Angus Leeming wrote:
Georg Baum wrote:
Of course, if the converter command was run from the master buffer
dir, the situation would be different, since $$FName would always
be the right variable to use.
This would work. I don't know very well all the capabilities of
external templates.
On Wed, Mar 17, 2004 at 04:18:12PM +, Andreas wrote:
Some of you might be familiar with the poor quality of the fonts when
viewing a pdf file created from a lyx document. The fonts look
pixelised and it is not possible to mark text.
Only if you use the default Computer Modern fonts.
Now,
Here's a patch to make André happy:
33 files changed, 56 insertions(+), 860 deletions(-)
(and of these, almost all the insertions are ChangeLog entries ;-)
The patch gets rid of the Forks dialog, as promised and discussed.
--
Angus
forks.diff.bz2
Description: BZip2 compressed data
On Tue, Mar 16, 2004 at 03:47:50PM +0100, Jean-Marc Lasgouttes wrote:
>
> For some time, I have been annoyed by the fact that, when I load a
> file in lyx 1.4.0cvs, it appears in a random color. While the visual
> effect is probably the consequence of a nonunititalized variable on my
> particular
Georg Baum wrote:
> I think the problematic case was something like
>
> file foo1.lyx inputs dir1/foo2.lyx
> file dir1/foo2.lyx inputs dir1/dir2/foo3.lyx
> file dir1/dir2/foo3.lyx uses graphics graph.eps (in dir1/dir2)
>
> the \includegraphics for graph.eps should read
>
On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
>
> ...reliably, any inset type, when opening the Document Settings
> dialog, changing something and pressing OK/Apply.
Anybody else seeing this?
- Martin
pgp0.pgp
Description: PGP signature
Angus Leeming wrote:
> So, can I summarise the requirement?
>
> // If this is a child document and the parent is
> // already loaded, then define 'base' as parent.base().
> // If the parent is also a child, then it would return
> // its own 'base'.
> string base;
> if
Kuba Ober wrote:
> Thanks a lot!! I was looking forward to that.
Not very usable ATM, though. Floats are still broken (I tried to fix it, with
no success). That's why I was holding it back until now. But I have the
feeling that we are moving towards a feature freeze (which would be a good
Martin Vermeer wrote:
> On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
>>
>> ...reliably, any inset type, when opening the Document Settings
>> dialog, changing something and pressing OK/Apply.
>
> Anybody else seeing this?
Solved with the caveman's method.
Alfredo
?
Martin Vermeer wrote:
> On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
>>
>> ...reliably, any inset type, when opening the Document Settings
>> dialog, changing something and pressing OK/Apply.
>
> Anybody else seeing this?
Yes, confirmed. Nothing serious though, it's
Georg Baum wrote:
> I think so.
> I am not sure wether I understood you correctly, but I believe this
> is exactly what
>
> - string from_file =
> params.filename.outputFilename(buffer.filePath());
> + // a relative filename should be relative to the master
> buffer
> + string
On Wed, Mar 17, 2004 at 11:28:08AM +0100, Alfredo Braunstein spake thusly:
> Martin Vermeer wrote:
>
> > On Fri, Mar 12, 2004 at 03:17:32PM +0200, Martin Vermeer spake thusly:
> >>
> >> ...reliably, any inset type, when opening the Document Settings
> >> dialog, changing something and pressing
On Wed, Mar 17, 2004 at 11:15:05AM +0100, Juergen Spitzmueller spake thusly:
>
> Kuba Ober wrote:
> > Thanks a lot!! I was looking forward to that.
>
> Not very usable ATM, though. Floats are still broken (I tried to fix it, with
> no success). That's why I was holding it back until now. But I
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I don't see why $$LatexName is needed. Is it still needed after
Angus> Jean-Marc's Buffer::getMasterBuffer() is included in the
Angus> source?
It seems to me that in some cases (when calling the script that
produces the right
I retried, and still get this strange behaviour.
On 'closer' examination I get:
lilie:/home/poenitz # traceroute cvs.lyx.org
traceroute to cvs.lyx.org (80.232.38.163), 30 hops max, 40 byte packets
[...]
send failed: No buffer space available
send failed:
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> I don't see why $$LatexName is needed. Is it still needed
> after Angus> Jean-Marc's Buffer::getMasterBuffer() is included in
> the Angus> source?
>
>
> It seems to me that in some cases (when
Andre Poenitz <[EMAIL PROTECTED]> writes:
| I retried, and still get this strange behaviour.
>
| On 'closer' examination I get:
>
| lilie:/home/poenitz # traceroute cvs.lyx.org
| traceroute to cvs.lyx.org (80.232.38.163), 30 hops max, 40 byte packets
| [...]
| send failed:
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> I don't see why $$LatexName is needed. Is it still needed after
> Angus> Jean-Marc's Buffer::getMasterBuffer() is included in the
> Angus> source?
>
>
> It seems to me that in some cases (when
Georg Baum wrote:
>> Of course, if the converter command was run from the master buffer
>> dir, the situation would be different, since $$FName would always
>> be the right variable to use.
>
> This would work. I don't know very well all the capabilities of
> external templates. Angus, if this
Hi all,
Some of you might be familiar with the poor quality of the fonts when viewing a
pdf file created from a lyx document. The fonts look pixelised and it is not
possible to mark text.
The reason for this is the
\usepackage[T1]{fontenc}
statement that lyx automatically adds to the document
On Wednesday 17 March 2004 11:18 am, Andreas wrote:
> Hi all,
>
> Some of you might be familiar with the poor quality of the fonts when
> viewing a pdf file created from a lyx document. The fonts look pixelised
> and it is not possible to mark text.
As a side note: This is a serious problem with
On Wed, Mar 17, 2004 at 04:05:45PM +0900, Rob Lahaye wrote:
> I remember similar things happened here when I compiled with Qt.
> I believe it was caused by the Qt libs which were compiled with
> threads by default from the ports.
>
> However, threads are not needed for LyX and thus LyX/Qt
Angus Leeming wrote:
> Georg Baum wrote:
>>> Of course, if the converter command was run from the master buffer
>>> dir, the situation would be different, since $$FName would always
>>> be the right variable to use.
>>
>> This would work. I don't know very well all the capabilities of
>>
On Wed, Mar 17, 2004 at 04:18:12PM +, Andreas wrote:
> Some of you might be familiar with the poor quality of the fonts when
> viewing a pdf file created from a lyx document. The fonts look
> pixelised and it is not possible to mark text.
Only if you use the default Computer Modern fonts.
Here's a patch to make André happy:
33 files changed, 56 insertions(+), 860 deletions(-)
(and of these, almost all the insertions are ChangeLog entries ;-)
The patch gets rid of the Forks dialog, as promised and discussed.
--
Angus
forks.diff.bz2
Description: BZip2 compressed data
44 matches
Mail list logo
