Juergen Spitzmueller wrote:
(btw if anyone notices style issues, feel free to improve the wording.
Where's Angus when you need him?)
Ich bin hier, mein freund, aber ich auch sehr beschäftigt bin. Sie
schreiben soviel, es sind schwierig zu folgen.
Anyway, attached is a slightly re-worked vers
- There is also no default value (should be "1").
i regarded it as string, which can be empty, i.e. no default value.
but we can change it if you disagree.
- It is possible to enter there other characters than the allowed numbers
0-9.
shouldn't be the user responsible ?
Uwe Stöhr wrote:
> As JMarc warned, having \label commands inside \sections (e.g.) will
cause LaTeX to choke when
> hyperref is loaded, in certain cases, crucially, when you also have
a TOC.
This is not the case as the UserGuide and other manuals use already
hyperref.
JMarc, could you give a
Pavel Sanda schrieb:
Anyway, as we want to cooperate, I will write some scripts that do the job
and give me svn output for you.
done. can you please try this version ? :)
Works, thanks.
Uwe
> As JMarc warned, having \label commands inside \sections (e.g.) will cause
LaTeX to choke when
> hyperref is loaded, in certain cases, crucially, when you also have a TOC.
This is not the case as the UserGuide and other manuals use already hyperref.
JMarc, could you give an example where tihs
Concerning the current state of the PDF support:
There are three remaining open issues:
- the bookmark level field is not working:
- No matter what you insert, it is converted to "False" or "True".
- There is also no default value (should be "1").
- It is possible to enter there other charact
> > > - the bookmark level field is not working:
> > > - No matter what you insert, it is converted to "False" or "True".
>
> my trunk is in complete rebuild and it will take years.. can you try this
> one ?
even better follows.
hyperref should be now before babel... its easy to move & play wit
> Anyway, as we want to cooperate, I will write some scripts that do the job
> and give me svn output for you.
done. can you please try this version ? :)
pavel
Index: src/frontends/qt4/ui/PDFSupportUi.ui
===
--- src/frontends/qt4/ui/P
> Pavel Sanda schrieb:
>
>> btw disagreement with your last fix
>> - opt += (pdfborder ?'1':'0'); + opt += (pdfborder ?'0':'1');
>> havent tried but expect it will break elsewhere and also reverts the
>> semantics.
>
> This fix is correct: the option is "no border", therefore when it
Pavel Sanda schrieb:
btw disagreement with your last fix
- opt += (pdfborder ?'1':'0');
+ opt += (pdfborder ?'0':'1');
havent tried but expect it will break elsewhere and also reverts the semantics.
This fix is correct: the option is "no border", therefore when it is checked, the
> - The dialog is smaller than the form, see the attached image: The
> aditional options field and the right border are hidden.
your change make it work under win, but broke right box width under linux.
so next iteration, diffed against last state.
pavel
Index: src/frontends/qt4/ui/PDFSupportUi.u
> > - the bookmark level field is not working:
> > - No matter what you insert, it is converted to "False" or "True".
my trunk is in complete rebuild and it will take years.. can you try this
one ?
> > - There is also no default value (should be "1").
i regarded it as string, which can be empt
> Concerning the current state of the PDF support:
>
> There are three remaining open issues:
thanks for report.
> - the bookmark level field is not working:
> - No matter what you insert, it is converted to "False" or "True".
> - There is also no default value (should be "1").
> - It is poss
Inset * readInset(Lexer & lex, Buffer const & buf)
{
...
// test the different insets
if (tmptok == "LatexCommand") {
lex.next();
string const cmdName = lex.getString();
lex.pushToken(cmdName);
...
} else if (cmdName == "listofalgorithms") {
inset.rese
Georg Baum wrote:
Richard Heck wrote:
Georg Baum wrote:
The bad news is that this change will require one controller class for
each inset. Currently there is only one command controller, used by all
command insets. That is the only reason I did not do this change already
during the Ins
I haven't looked into this in detail, but I strongly suspect that we do
now need to do something about bug 2154. As JMarc warned, having \label
commands inside \sections (e.g.) will cause LaTeX to choke when hyperref
is loaded, in certain cases, crucially, when you also have a TOC.
Abdel had
> Pavel Sanda schrieb:
>
>> I _do_ send them as an attachment _always_. If some web archives corrupt
>> it, its not my fault. But I can CC you which should solve this issue.
>
> Yes I see now that mail-archive.com has some problems recently.
I studied meanwhile why it is so; there is way how to b
Uwe Stöhr wrote:
But you already use it to check out the SVN repository.
No, he's using git, which is a different kind of VCS. In this case, the
advantage is that it's easy to maintain a local repository, to apply VC
to your own work. To do that with svn, the easiest way is to create a
branch,
Pavel Sanda schrieb:
I _do_ send them as an attachment _always_. If some web archives corrupt it,
its not my fault. But I can CC you which should solve this issue.
Yes I see now that mail-archive.com has some problems recently.
I have already written and will continue to write, that the orig
Does anyone know roughly how long it takes to build LyX on a machine with
one of these processors:
* Core 2 Duo E4300
* AMD Athlon 64 X2 4000+
* AMD Athlon X2 BE-2400 (or BE-2350)
The reason for my strange question is that I'm going to buy a server to
have at home, and I'm using LyX development
> > can you be more verbose what you mean or give me some link ? somehow i'm
> > reluctant to believe that mutt would break any RFC.
> >
> > pavel
>
> http://marc.info/?t=11835435303&r=1&w=2
>
> especially http://marc.info/?l=lyx-devel&m=118366121102662&w=2
>
> I would not blame mutt, but a
> can you be more verbose what you mean or give me some link ? somehow i'm
> reluctant to believe that mutt would break any RFC.
>
> pavel
http://marc.info/?t=11835435303&r=1&w=2
especially http://marc.info/?l=lyx-devel&m=118366121102662&w=2
I would not blame mutt, but a line may be needed t
> > I _do_ send them as an attachment _always_. If some web archives corrupt it,
> > its not my fault. But I can CC you which should solve this issue.
>
> I guess you have the same problem as Abdel once had. Your attachment
> should be coded as attachment.
can you be more verbose what you mean or
Jean-Marc Lasgouttes wrote:
But unfortunately, the nest-all approach complicates the use wrt
font-painting for no gain in 90% of the cases (IMO).
Well, I'm no expert whatsoever on that. I stay as far from painting as
possible.
BTW, you should try to grep for font-code in lib/bind...
Did.
Abdelrazak Younes wrote:
[EMAIL PROTECTED] wrote:
Author: younes
Date: Fri Sep 21 22:39:47 2007
New Revision: 20420
URL: http://www.lyx.org/trac/changeset/20420
Log:
* Inset:
- get rid of the cached Dimension. Text inset dimensions are saved in
ParagraphMetrics and mathed maintain their own di
> I _do_ send them as an attachment _always_. If some web archives corrupt it,
> its not my fault. But I can CC you which should solve this issue.
I guess you have the same problem as Abdel once had. Your attachment
should be coded as attachment.
Cheers,
Bo
> Pavel Sanda wrote:
>>> or directly the SVN programm to create diffs?
>> Because I don't use it.
>
> How do you update your tree then?
git-svn rebase
pavel
Pavel Sanda wrote:
or directly the SVN programm to create diffs?
Because I don't use it.
How do you update your tree then?
Abdel.
> >> Pavel, please attach patches the next time as unified diff as email
> >> attachment, this makes life much easier.
> >
> > This seems to be our popular issue :)
>
> Of course, because I cannot apply your patches but has to copy and paste
> them manually.
I'm sorry about that.
> And I meant
[EMAIL PROTECTED] wrote:
Author: younes
Date: Fri Sep 21 22:39:47 2007
New Revision: 20420
URL: http://www.lyx.org/trac/changeset/20420
Log:
* Inset:
- get rid of the cached Dimension. Text inset dimensions are saved in
ParagraphMetrics and mathed maintain their own dimension where needed.
- wi
Alfredo Braunstein wrote:
Hi,
I agree with Christian's objections/comments in general.
What would be the problem of having normal labels automatically
inserted by LyX when one refers to a section etc in an appropriately
enhanced insert->cross-reference dialog?
In this way, 1) one doesn't have
Richard Heck wrote:
> Georg Baum wrote:
>> The bad news is that this change will require one controller class for
>> each inset. Currently there is only one command controller, used by all
>> command insets. That is the only reason I did not do this change already
>> during the InsetCommandParams
Hi,
I agree with Christian's objections/comments in general.
What would be the problem of having normal labels automatically
inserted by LyX when one refers to a section etc in an appropriately
enhanced insert->cross-reference dialog?
In this way, 1) one doesn't have to insert them manually 2) L
[EMAIL PROTECTED] wrote:
On Fri, 21 Sep 2007, Helge Hafting wrote:
For me, the problem is the hassle of having to insert them. This is
very occationally useful.
Hi Helge,
I agree, having to insert and having to come up with a name.
Hello to both,
When you're done with the discussion, ple
>> Pavel, please attach patches the next time as unified diff as email
>> attachment, this makes life much easier.
>
> This seems to be our popular issue :)
Of course, because I cannot apply your patches but has to copy and paste them manually. And I meant
that whitespace issues can be avoided w
On Friday 21 September 2007 15:03:23 Jean-Marc Lasgouttes wrote:
> Yes, but you are probably aware that:
>
> pegase: msgfmt --statistics -o fr.gmo fr.po
> 2402 messages traduits, 728 traductions approximatives, 487 messages
> non-traduits.
I was not aware.
> You need to reset the locale.
Sur
Richard Heck <[EMAIL PROTECTED]> writes:
> OK. At least we're clear now what the issue is. (I agree completely
> about the need to separate fonts from charstyles, of course.) But
> here's what's moving me: Turning fonts into insets solves all kinds of
> problems involving nesting, as well as probl
Georg Baum wrote:
The bad news is that this change will require one controller class for each
inset. Currently there is only one command controller, used by all command
insets. That is the only reason I did not do this change already during the
InsetCommandParams rewrite.
Sorry, could you expl
Martin Vermeer wrote:
However, this is othogonal to the
discussion about changing fonts to insets (although I am not a
proponent of this change, as some people know).
Yes, what I was trying to argue is that I am against that too. Reason:
it adds one extra layer of complexity in-between, for
Jean-Marc Lasgouttes wrote:
What I'm suggesting is that command insets should behave the same way.
So we'd have:
\begin_inset Citation
command citet
key etctec
\end_inset
More or less.
This looks reasonable, in general.
A question: how will the parser know that this
Juergen Spitzmueller wrote:
Richard Heck wrote:
I'm looking now at re-working some of the code surrounding InsetCommand
and its derivatives. The motivation here is, ultimately, BibLaTeX
support
\begin{praise}
You're going to make me blush.
Richard
Pavel Sanda wrote:
1. view source dialog is still broken (Can not update). Can anyone fix it?
i will look.
ahh, i misread your post thinking that pdf stuff broke source dialog,
which is not the case.
seems ControlViewSource::updateContent is not entered at all.
This is probab
On Fri, 21 Sep 2007, Helge Hafting wrote:
[EMAIL PROTECTED] wrote:
On Tue, 18 Sep 2007, Yann Disser wrote:
> It would be nice if you considered implementing the possibility of
> cross-referencing to sections etc without the need of inserting ugly
> labels - the use of labels should in my
José Matos <[EMAIL PROTECTED]> writes:
> That was a direct cut and paste. Fixed.
Thanks.
> This is what I get:
Yes, but you are probably aware that:
pegase: msgfmt --statistics -o fr.gmo fr.po
2402 messages traduits, 728 traductions approximatives, 487 messages
non-traduits.
You need to re
On Friday 21 September 2007 14:40:11 Jean-Marc Lasgouttes wrote:
> Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> > Jean-Marc Lasgouttes wrote:
> >> Juergen, can I apply that to 1.5 too? It is only a maintainer tool.
> >
> > Sure.
>
> Jose, now that I try it, it seems that it does not work at a
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>> So, what name shall I give to this thing?
>
> From these, inverse is surely the least confusing one.
So this patch would be OK for trunk and branch?
JMarc
svndiff src lib/bind
Index: src/LyXAction.cpp
==
On Fri, Sep 21, 2007 at 02:13:55AM +0200, Andre Poenitz wrote:
> On Thu, Sep 20, 2007 at 02:23:28PM +0200, Enrico Forestieri wrote:
> > > What about deciding that we do not install the libraries? Of course,
> > > this would imply that an installable LyX is a static one, but I am not
> > > sure we
> > -void PDFOptions::writeLaTeX(odocstream &os) const
> > +void PDFOptions::writeLaTeX(odocstringstream &os) const
>
> Why?
my fault. PDFOptions::writeLaTeX is called with odocstringstream param
elsewhere and when we were haunting strange bug yesterday i was not sure
whether this couldnt make s
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>> Juergen, can I apply that to 1.5 too? It is only a maintainer tool.
>
> Sure.
Jose, now that I try it, it seems that it does not work at all :)
pegase: python postats.py fr.po
'fr', "date" => "2007-07-18",
"msg_tr
Jean-Marc Lasgouttes wrote:
> \makelyxbeamertitle is an horrible name... \lyxbeamermaketitle would
> be better, but I think you can at least drop 'lyx' or 'beamer' from
> there.
Fine. I just wanted to make sure that we are on the safe side, if Till
Tantau decides to implement a \beamermaketitle c
Jean-Marc Lasgouttes wrote:
> Ideas include:
>
> break-paragraph special
> break-paragraph inverse
> break-paragraph alt
> break-paragraph 1
>
> So, what name shall I give to this thing?
>From these, inverse is surely the least confusing one.
Jürgen
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>
>> Juergen, gcc complains about this variable, and I think it is right.
>> Shall I apply to branch and trunk?
>
> Yes, please.
Done.
JMarc
Jean-Marc Lasgouttes wrote:
> Juergen, gcc complains about this variable, and I think it is right.
> Shall I apply to branch and trunk?
Yes, please.
Jürgen
Jean-Marc Lasgouttes wrote:
> Juergen, can I apply that to 1.5 too? It is only a maintainer tool.
Sure.
Jürgen
[EMAIL PROTECTED] writes:
> Author: rgheck
> Date: Thu Sep 20 07:00:23 2007
> New Revision: 20366
>
> URL: http://www.lyx.org/trac/changeset/20366
> Log:
> Introduce LFUN_MASTER_BUFFER_VIEW and UPDATE. Code by Tommaso Cucinotta.
>
> Modified:
> lyx-devel/trunk/lib/bind/cua.bind
> lyx-devel
> > 1. view source dialog is still broken (Can not update). Can anyone fix it?
>
> i will look.
ahh, i misread your post thinking that pdf stuff broke source dialog,
which is not the case.
seems ControlViewSource::updateContent is not entered at all.
pavel
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
>> Actually, it could be renamed to something like
>> break-paragraph-special, or an 'inverse' option could be added to
>> break-paragraph.
>
> Yes, the current name is certainly misleading.
> I would prefer to merge the two lfuns and add an option (I
[EMAIL PROTECTED] writes:
> Author: jamatos
> Date: Fri Sep 7 18:37:38 2007
> New Revision: 20130
>
> URL: http://www.lyx.org/trac/changeset/20130
> Log:
> Convert postats to python
Juergen, can I apply that to 1.5 too? It is only a maintainer tool.
JMarc
Andre Poenitz <[EMAIL PROTECTED]> writes:
> Yes. We can do that. Should even. Tell me what to do...
First, replace all instances of pkglib_LTLIBRARIES by
noinst_LTLIBRARIES.
I did not find where you set static/shared depending on the platform,
but you should add a test for '$lyx_devel_version =
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> http://bugzilla.lyx.org/show_bug.cgi?id=3133
>
> The attached patch adds a "Title (Plain Frame)" style that can
> be used instead of "Title" to get a plain title frame (no head-/footlines
> and navigation bars). This is somewhat hackish, as a big p
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Great. Jean-Marc, can you please commit this to branch?
> The bug in question is
> http://bugzilla.lyx.org/show_bug.cgi?id=4014
Done.
JMarc
Juergen, gcc complains about this variable, and I think it is right.
Shall I apply to branch and trunk?
JMarc
svndiff src/LaTeX.cpp
Index: src/LaTeX.cpp
===
--- src/LaTeX.cpp (révision 20408)
+++ src/LaTeX.cpp (copie de travail)
@@
José Matos <[EMAIL PROTECTED]> writes:
> On Friday 21 September 2007 11:47:26 Jean-Marc Lasgouttes wrote:
>> Lokks again like a missing config.h. Does disabling pch change
>> something?
>
> This is already with --disable-pch.
It seems that there are a few files in trunk that do not include
conf
Roger Mc Murtrie wrote:
> Excellent "shot in the dark".
> Adding #include at the top of the original regex/
> src/pch.h file fixes the problem.
Great. Jean-Marc, can you please commit this to branch?
The bug in question is
http://bugzilla.lyx.org/show_bug.cgi?id=4014
Jürgen
On Friday 21 September 2007 11:47:26 Jean-Marc Lasgouttes wrote:
> Lokks again like a missing config.h. Does disabling pch change
> something?
This is already with --disable-pch.
> JMarc
--
José Abílio
José Matos <[EMAIL PROTECTED]> writes:
> Hi,
> when compiling lyx with external boost when I start lyx it immediately
> crashes. The backtrace follows attached. Any suggestion?
Lokks again like a missing config.h. Does disabling pch change
something?
JMarc
Hi,
when compiling lyx with external boost when I start lyx it immediately
crashes. The backtrace follows attached. Any suggestion?
--
José Abílio
[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New process 28078]
[New Thre
> I tried to play with the PDF property feature.
>
> 1. view source dialog is still broken (Can not update). Can anyone fix it?
i will look.
> 2. I only checked two items but your hyperref output has two lines of
> options. Can you remove some of them that are using their default
> values?
i wa
On 21/09/2007, at 6:26 PM, Jean-Marc Lasgouttes wrote:
A shot in the dark: this problem typically looks like having part of
the code forget to use #include . When this happens and
stdlib-debug is on, the mamory layout of std::string (for example) is
not the same in different parts of LyX code.
Andre Poenitz wrote:
Little puzzle for you:
What belongs together?
Configurations:
(A) current svn, --enable-pch
(B) current svn, --disable-pch
At some point, pch defaulted to on, and it broke the build for me.
I have used --disable-pch since then.
Is it problem-free to use these days?
[EMAIL PROTECTED] wrote:
On Tue, 18 Sep 2007, Yann Disser wrote:
It would be nice if you considered implementing the possibility of
cross-referencing to sections etc without the need of inserting ugly
labels - the use of labels should in my opinion be reduced to an
absolute minimum. My works
Richard Heck wrote:
> The change should be fairly simple, both in the code and in lyx2lyx:
> It's mostly a matter of file format, not so much of internal
> representation. Internal code concerned with writing and reading will be
> all that changes. This will significantly simplify factory.cpp's
>
Jean-Marc Lasgouttes wrote:
> Example I found yesterday and did not report yet: when using almost EC
> fonts, I need to use aeguill.sty too if I want to use <>
> guillemets (otherwise all I get is black squares). Either we always
> load it (but I suspect there is a reason why the ae style file doe
Jean-Marc Lasgouttes wrote:
> Example I found yesterday and did not report yet: when using almost EC
> fonts, I need to use aeguill.sty too if I want to use <>
> guillemets (otherwise all I get is black squares). Either we always
> load it (but I suspect there is a reason why the ae style file doe
On Fri, Sep 21, 2007 at 02:10:56AM -, [EMAIL PROTECTED] wrote:
> Author: rgheck
> Date: Fri Sep 21 04:10:50 2007
> New Revision: 20406
>
> URL: http://www.lyx.org/trac/changeset/20406
> Log:
> Fix from Pavel.
>
> Modified:
> lyx-devel/trunk/src/PDFOptions.cpp
> lyx-devel/trunk/src/PDF
On Friday 21 September 2007 10:28:06 Jean-Marc Lasgouttes wrote:
> OK, you mean font packages. Yes, something could be done, but some
> hardcoding is often necessary.
>
> Example I found yesterday and did not report yet: when using almost EC
> fonts, I need to use aeguill.sty too if I want to use <
On Fri, Sep 21, 2007 at 09:01:32AM +0200, Juergen Spitzmueller wrote:
> Roger Mc Murtrie wrote:
>
> > Problem finally found to be due to boost/libs/regex/src precompiled
> > headers.
> >
> > The problem no longer occurs when all lines of boost/libs/regex/src/
> > pch.h are commented out.
> > I co
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> The fonts we support are hardcoded in LyX. This means that new fonts (such
> as the TeXGyre fonts) need to be added to BufferParams::loadFonts (which
> always entails a file format change currently).
OK, you mean font packages. Yes, something cou
On Fri, Sep 21, 2007 at 03:53:52AM +0200, Pavel Sanda wrote:
> can you add this small polish ?
> pavel
> diff --git a/src/PDFOptions.cpp b/src/PDFOptions.cpp
> index d16b9cd..0bf5a0d 100644
> --- a/src/PDFOptions.cpp
> +++ b/src/PDFOptions.cpp
> @@ -76,7 +76,7 @@ void PDFOptions::writeFile(ostream
On Fri, Sep 21, 2007 at 02:43:48AM +0200, Pavel Sanda wrote:
> >- less than 80 - \epsilon chars per line.
>
> >- no tabs after the first non-tab on the line.
>
> > - Two empty lines between function definitions.
>
> > - includes roughly from most-specific to least-specific. In any case
> > "ou
On Fri, 21 Sep 2007 10:35:04 +0200
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> > Actually I'm not too sure we should "re-package" font attributes as insets.
> > They should remain themselves, only their direct use discouraged.
>
> Well, we sha
On Fri, 21 Sep 2007 10:29:17 +0200
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Martin Vermeer wrote:
> > On Fri, 21 Sep 2007 08:32:39 +0200
> > Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> >
> >> Martin Vermeer wrote:
> >>> On Fri, Sep 21, 2007 at 01:19:48AM +0200, Dov Feldstern wrote:
> >>>
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> do you have an easy fix handy ;-)
>
> What about this... could you try please?
How come cursorLeft does not set the font correctly? I tried to follow
that code, but I am not sure I understand. Ideally, the call to
setCurrentFont should be automatic
Jean-Marc Lasgouttes wrote:
>> Fonts, btw, should go down the same route eventually (however, we should
>> take care that we don't end up with 173 configuration files).
>
> What do you mean?
The fonts we support are hardcoded in LyX. This means that new fonts (such
as the TeXGyre fonts) need to
José Matos <[EMAIL PROTECTED]> writes:
> On Friday 21 September 2007 08:12:49 Juergen Spitzmueller wrote:
>> P.S.: José, I'm unsure about the file format policy in this specific case.
>> Would it require a file format change? If not, I'd like to commit this to
>> branch as well.
>
> This means tha
José Matos wrote:
> This means that if you a previous version of 1.5 (1.5.1) for all purposes
> you will not be able to work with that file if you use the new style as it
> will be converted to the default layout style.
>
> OTHO this is some kind of weak bondage in the sense that the files loads
Michael Gerz <[EMAIL PROTECTED]> writes:
> Hi,
>
> before I add lots of new patches to my list:
>
> Is PDFOptions a potential candidate for 1.5.x?
No, it is a format change.
JMarc
On Friday 21 September 2007 08:12:49 Juergen Spitzmueller wrote:
> P.S.: José, I'm unsure about the file format policy in this specific case.
> Would it require a file format change? If not, I'd like to commit this to
> branch as well.
This means that if you a previous version of 1.5 (1.5.1) for a
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Fonts, btw, should go down the same route eventually (however, we should
> take care that we don't end up with 173 configuration files).
What do you mean?
>> What I'm suggesting is that command insets should behave the same way.
>> So we'd have:
Martin Vermeer <[EMAIL PROTECTED]> writes:
> Actually I'm not too sure we should "re-package" font attributes as insets.
> They should remain themselves, only their direct use discouraged.
Well, we shall definitely keep a separation (at least in the UI)
between fonts and char styles, if only to m
Martin Vermeer wrote:
On Fri, 21 Sep 2007 08:32:39 +0200
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
Martin Vermeer wrote:
On Fri, Sep 21, 2007 at 01:19:48AM +0200, Dov Feldstern wrote:
Now there's a follow-up issue: when leaving the ERT inset by pressing
right-arrow at the end of the inse
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> Roger Mc Murtrie wrote:
>
>> Problem finally found to be due to boost/libs/regex/src precompiled
>> headers.
>>
>> The problem no longer occurs when all lines of boost/libs/regex/src/
>> pch.h are commented out.
>> I could not identify any partic
On Fri, 21 Sep 2007 08:32:39 +0200
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Martin Vermeer wrote:
> > On Fri, Sep 21, 2007 at 01:19:48AM +0200, Dov Feldstern wrote:
> >
> >> Now there's a follow-up issue: when leaving the ERT inset by pressing
> >> right-arrow at the end of the inset, to
http://bugzilla.lyx.org/show_bug.cgi?id=3133
The attached patch adds a "Title (Plain Frame)" style that can
be used instead of "Title" to get a plain title frame (no head-/footlines
and navigation bars). This is somewhat hackish, as a big part of the beamer
implementation in LyX is, but it's as go
Roger Mc Murtrie wrote:
> Problem finally found to be due to boost/libs/regex/src precompiled
> headers.
>
> The problem no longer occurs when all lines of boost/libs/regex/src/
> pch.h are commented out.
> I could not identify any particular header file causing the problem.
> The bug is only cur
95 matches
Mail list logo
