On Tue, Oct 26, 2004 at 09:03:23AM +0300, Martin Vermeer wrote:
To add my spicing to this soup, shouldn't we first take inventory of
what bugs we actually have, and how critical they are? There is all
kinds of stuff on bugzilla, and I suspect some of them must be
absolutely fixed while others
On Wed, Oct 27, 2004 at 11:23:59AM -0700, Kevin Martin wrote:
...here is a screen capture of the error message:
Could you please stop this nonsense of posting screen shots of
_text_ messages?
Thank you.
Andre'
On Thu, Oct 28, 2004 at 12:31:57PM +0200, Alfredo Braunstein wrote:
I'm compiling your coordinates rewrite patch, and I'll try to work a bit on
it in the next few days.
That would be really nice.
But don't hesitate to drop it completely and stick to current CVS if you
get the impression that
[EMAIL PROTECTED] wrote:
Can you give me a (LaTeX) example for that? I have no idea what you're=20
refering too, to be honest.
If only I remembered... try placing a noun charstyle inside a section
header and see how it prints. Or inside a std paragraph formatted for
big font size.
Both come
On Sat, Oct 30, 2004 at 11:30:29AM +0200, Juergen Spitzmueller wrote:
If it works for LaTeX, it will work there too.
I will not touch this. Maybe Jose can have a look at it.
If you change the call to latex then do the same for linuxdoc and docbook.
Or else I will do it. :-)
What we
José Abílio Oliveira Matos wrote:
I will not touch this. Maybe Jose can have a look at it.
If you change the call to latex then do the same for linuxdoc and
docbook. Or else I will do it. :-)
Well, if you put it like this ;-)
But please review the attached patch (especially I'm not sure if
On Sat, Oct 30, 2004 at 12:00:53PM +0200, Juergen Spitzmueller wrote:
Well, if you put it like this ;-)
:-)
It was not a threat, but a treat. ;-)
But please review the attached patch (especially I'm not sure if
sgml::escapeString is still needed with InsetText::docbook/linuxdoc).
John Weiss wrote:
On Fri, Oct 22, 2004 at 09:59:40PM +0100, Angus Leeming wrote:
The attached patch enables us to move XFig files to the temp directory
and continue to generate DVI files, etc that show any included picture
files.
Question:
Why move the files? Will LaTeX not respect
John Weiss wrote:
One could certainly add an assert to a trace class. You'd then need
a 3-state #define constant: undefined (for the no-op defn.),
defined, gentle mode (does not abort), defined, harsh mode (aborts).
[Note: I'll provide my own Trace.{h,cc} files on request.]
Here's your
Kayvan A. Sylvan wrote:
On Fri, Oct 29, 2004 at 01:04:27PM -0700, Kayvan A. Sylvan wrote:
Recent CVS exhibits the following problem:
lyx --export program foo.lyx
This seems to always return an error, even when the build script appears
to work. Is there something that has changed with the
John Weiss [EMAIL PROTECTED] writes:
On Fri, Oct 22, 2004 at 09:59:40PM +0100, Angus Leeming wrote:
The attached patch enables us to move XFig files to the temp directory and
continue to generate DVI files, etc that show any included picture files.
Question:
Why move the files? Will
Am Freitag, 29. Oktober 2004 19:49 schrieb Angus Leeming:
It looks very clever. Didn't realise I'd helped write tex_copy.py.
I used lyxpreview2bitmap.py as a base, and this really helped!
I see why the $$l stuff is necessary, but... Well done anyway, for
working
it all out. You clearly have
Am Freitag, 29. Oktober 2004 22:11 schrieb Kayvan A. Sylvan:
On Fri, Oct 29, 2004 at 01:04:27PM -0700, Kayvan A. Sylvan wrote:
Recent CVS exhibits the following problem:
lyx --export program foo.lyx
This seems to always return an error, even when the build script
appears
to work.
As mentioned in the previous thread, entering a charstyle inset with the mouse
leads to an infinite loop. The attached oneliner fixes this (typo). I will
just commit this since it seems uncontroversial.
Jürgen
Index: insetcharstyle.C
On Sat, Oct 30, 2004 at 04:50:23PM +0200, Juergen Spitzmueller wrote:
As mentioned in the previous thread, entering a charstyle inset with the mouse
leads to an infinite loop. The attached oneliner fixes this (typo). I will
just commit this since it seems uncontroversial.
Jürgen
Do it.
On Sat, 30 Oct 2004 11:30:29 +0200 Juergen Spitzmueller [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Can you give me a (LaTeX) example for that? I have no idea what
you're=20
refering too, to be honest.
If only I remembered... try placing a noun charstyle inside a section
header
These are just some minor cosmetics to make the char style inset look a little
bit better, now that is usable again (most importantly: I have removed the
left margin which really annoyed me all the time).
Still missing: the label (not drawn for some reason I couldn't figure out
yet).
I will
Juergen Spitzmueller [EMAIL PROTECTED] writes:
| if (has_label_) {
| + lyxerr params_type = params_.type endl;
Please conditionalize this one a debug flag.
--
Lgb
On Tue, Oct 26, 2004 at 09:03:23AM +0300, Martin Vermeer wrote:
> To add my spicing to this soup, shouldn't we first take inventory of
> what bugs we actually have, and how critical they are? There is all
> kinds of stuff on bugzilla, and I suspect some of them must be
> absolutely fixed while
On Wed, Oct 27, 2004 at 11:23:59AM -0700, Kevin Martin wrote:
> ...here is a screen capture of the error message:
Could you please stop this nonsense of posting screen shots of
_text_ messages?
Thank you.
Andre'
On Thu, Oct 28, 2004 at 12:31:57PM +0200, Alfredo Braunstein wrote:
> I'm compiling your coordinates rewrite patch, and I'll try to work a bit on
> it in the next few days.
That would be really nice.
But don't hesitate to drop it completely and stick to current CVS if you
get the impression that
[EMAIL PROTECTED] wrote:
> >Can you give me a (LaTeX) example for that? I have no idea what you're=20
> >refering too, to be honest.
>
> If only I remembered... try placing a noun charstyle inside a section
> header and see how it prints. Or inside a std paragraph formatted for
> big font size.
On Sat, Oct 30, 2004 at 11:30:29AM +0200, Juergen Spitzmueller wrote:
> >
> > If it works for LaTeX, it will work there too.
>
> I will not touch this. Maybe Jose can have a look at it.
If you change the call to latex then do the same for linuxdoc and docbook.
Or else I will do it. :-)
What
José Abílio Oliveira Matos wrote:
> > I will not touch this. Maybe Jose can have a look at it.
>
> If you change the call to latex then do the same for linuxdoc and
> docbook. Or else I will do it. :-)
Well, if you put it like this ;-)
But please review the attached patch (especially I'm not
On Sat, Oct 30, 2004 at 12:00:53PM +0200, Juergen Spitzmueller wrote:
>
> Well, if you put it like this ;-)
:-)
It was not a threat, but a treat. ;-)
> But please review the attached patch (especially I'm not sure if
> sgml::escapeString is still needed with InsetText::docbook/linuxdoc).
John Weiss wrote:
> On Fri, Oct 22, 2004 at 09:59:40PM +0100, Angus Leeming wrote:
>> The attached patch enables us to move XFig files to the temp directory
>> and continue to generate DVI files, etc that show any included picture
>> files.
>
> Question:
>
> Why move the files? Will LaTeX not
John Weiss wrote:
> One could certainly add an "assert" to a trace class. You'd then need
> a 3-state "#define" constant: undefined (for the no-op defn.),
> defined, gentle mode (does not abort), defined, harsh mode (aborts).
>
> [Note: I'll provide my own "Trace.{h,cc}" files on request.]
Kayvan A. Sylvan wrote:
> On Fri, Oct 29, 2004 at 01:04:27PM -0700, Kayvan A. Sylvan wrote:
>> Recent CVS exhibits the following problem:
>>
>> lyx --export program foo.lyx
>>
>> This seems to always return an error, even when the build script appears
>> to work. Is there something that has
John Weiss <[EMAIL PROTECTED]> writes:
>
> On Fri, Oct 22, 2004 at 09:59:40PM +0100, Angus Leeming wrote:
> > The attached patch enables us to move XFig files to the temp directory and
> > continue to generate DVI files, etc that show any included picture files.
>
> Question:
>
> Why move the
Am Freitag, 29. Oktober 2004 19:49 schrieb Angus Leeming:
> It looks very clever. Didn't realise I'd helped write tex_copy.py.
I used lyxpreview2bitmap.py as a base, and this really helped!
> I see why the $$l stuff is necessary, but... Well done anyway, for
working
> it all out. You clearly
Am Freitag, 29. Oktober 2004 22:11 schrieb Kayvan A. Sylvan:
> On Fri, Oct 29, 2004 at 01:04:27PM -0700, Kayvan A. Sylvan wrote:
> > Recent CVS exhibits the following problem:
> >
> > lyx --export program foo.lyx
> >
> > This seems to always return an error, even when the build script
appears
As mentioned in the previous thread, entering a charstyle inset with the mouse
leads to an infinite loop. The attached oneliner fixes this (typo). I will
just commit this since it seems uncontroversial.
Jürgen
Index: insetcharstyle.C
On Sat, Oct 30, 2004 at 04:50:23PM +0200, Juergen Spitzmueller wrote:
> As mentioned in the previous thread, entering a charstyle inset with the mouse
> leads to an infinite loop. The attached oneliner fixes this (typo). I will
> just commit this since it seems uncontroversial.
>
> Jürgen
Do
On Sat, 30 Oct 2004 11:30:29 +0200 Juergen Spitzmueller <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > >Can you give me a (LaTeX) example for that? I have no idea what
> you're=20
> > >refering too, to be honest.
> >
> > If only I remembered... try placing a noun charstyle inside a
These are just some minor cosmetics to make the char style inset look a little
bit better, now that is usable again (most importantly: I have removed the
left margin which really annoyed me all the time).
Still missing: the label (not drawn for some reason I couldn't figure out
yet).
I will
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| if (has_label_) {
| + lyxerr << "params_type = " << params_.type << endl;
Please conditionalize this one a debug flag.
--
Lgb
36 matches
Mail list logo
