Jean-Marc Lasgouttes wrote:
One is supposed to use inset-toggle to put a math inset (e.g. a fraction
in a formula) in a closed state, where the cursor cannot eenter in the
inset. This state is saved in the .lyx file.
Thanks for the explanation.
Actually, I am not sure anymore that it is a
Jean-Marc Lasgouttes wrote:
> One is supposed to use inset-toggle to put a math inset (e.g. a fraction
> in a formula) in a closed state, where the cursor cannot eenter in the
> inset. This state is saved in the .lyx file.
Thanks for the explanation.
> Actually, I am not sure anymore that it is
Jean-Marc Lasgouttes wrote:
Hi all,
Does anyone has an idea on the usefulness of Text::autoBreakRow_? It
seems to be read in only one place (insertStringAsLines) and I am not
even sure of why it could make sense there.
Is it a remnant of something that used to make sense?
Unfortunately
Le 29/03/15 13:04, Georg Baum a écrit :
PS: I have another of these remnants in the mathed code: inset locking. I
think it used to work, but it looks pretty dead now.
I stumbled about that as well. Do you know what this was supposed to do?
One is supposed to use inset-toggle to put a math
Jean-Marc Lasgouttes wrote:
> Hi all,
>
> Does anyone has an idea on the usefulness of Text::autoBreakRow_? It
> seems to be read in only one place (insertStringAsLines) and I am not
> even sure of why it could make sense there.
>
> Is it a remnant of something that used to make sense?
Le 29/03/15 13:04, Georg Baum a écrit :
PS: I have another of these remnants in the mathed code: inset locking. I
think it used to work, but it looks pretty dead now.
I stumbled about that as well. Do you know what this was supposed to do?
One is supposed to use inset-toggle to put a math
Hi all,
Does anyone has an idea on the usefulness of Text::autoBreakRow_? It
seems to be read in only one place (insertStringAsLines) and I am not
even sure of why it could make sense there.
Is it a remnant of something that used to make sense?
JMarc
PS: I have another of these remants in
Hi all,
Does anyone has an idea on the usefulness of Text::autoBreakRow_? It
seems to be read in only one place (insertStringAsLines) and I am not
even sure of why it could make sense there.
Is it a remnant of something that used to make sense?
JMarc
PS: I have another of these remants in
Looks like it's done in lyx_1_2.py, by change_listof. So I'll schedule
it for removal, if that's OK by you, JMarc.
Sure.
JMarc
Looks like it's done in lyx_1_2.py, by change_listof. So I'll schedule
it for removal, if that's OK by you, JMarc.
Sure.
JMarc
Richard Heck wrote:
So far as I can see, the above can never be reached, because float lists
don't appear in the form:
\begin_inset LatexCommand
but rather as:
\begin_inset FloatList figure
Is it there for some actual reason?
AFAIK Compatibility.
Should it be removed, or should
Georg Baum [EMAIL PROTECTED] writes:
Richard Heck wrote:
So far as I can see, the above can never be reached, because float lists
don't appear in the form:
\begin_inset LatexCommand
but rather as:
\begin_inset FloatList figure
Is it there for some actual reason?
AFAIK
Jean-Marc Lasgouttes wrote:
Georg Baum [EMAIL PROTECTED] writes:
Richard Heck wrote:
So far as I can see, the above can never be reached, because float lists
don't appear in the form:
\begin_inset LatexCommand
but rather as:
\begin_inset FloatList figure
Is it there for some
Richard Heck wrote:
> So far as I can see, the above can never be reached, because float lists
> don't appear in the form:
> \begin_inset LatexCommand
> but rather as:
> \begin_inset FloatList figure
> Is it there for some actual reason?
AFAIK Compatibility.
> Should it be removed, or
Georg Baum <[EMAIL PROTECTED]> writes:
> Richard Heck wrote:
>
>> So far as I can see, the above can never be reached, because float lists
>> don't appear in the form:
>> \begin_inset LatexCommand
>> but rather as:
>> \begin_inset FloatList figure
>> Is it there for some actual reason?
>
Jean-Marc Lasgouttes wrote:
Georg Baum <[EMAIL PROTECTED]> writes:
Richard Heck wrote:
So far as I can see, the above can never be reached, because float lists
don't appear in the form:
\begin_inset LatexCommand
but rather as:
\begin_inset FloatList figure
Is it there for
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.reset(new
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") {
Michael Schmitt wrote:
Hello,
I have prepared a new list of dead code, just in case anybody is
interested in it...
Ah... btw, I used the QT frontend.
which explains both the ControlForks and ControlPreamble code. I fear
that it is no longer straightforward to selectively compile
Michael Schmitt wrote:
> Hello,
>
> I have prepared a new list of dead code, just in case anybody is
> interested in it...
>
> Ah... btw, I used the QT frontend.
which explains both the ControlForks and ControlPreamble code. I fear
that it is no longer straightforward to s
Hello,
I have prepared a new list of dead code, just in case anybody is
interested in it...
Ah... btw, I used the QT frontend.
Michael
(anonymous namespace)::Correction* std::__copy_backward(anonymous
namespace)::Correction*, (anonymous namespace)::Correction*((anonymous
namespace
Hello,
I have prepared a new list of dead code, just in case anybody is
interested in it...
Ah... btw, I used the QT frontend.
Michael
> (anonymous namespace)::Correction* std::__copy_backward<(anonymous
> namespace)::Correction*, (anonymous namespace)::Correction*>((anonymous
Can Sectioning.[Ch] be deleted ? Not used as far as I can see.
Also can I rip out the keymap dialog ? It's not currently used
and I don't fancy porting it to GUII.
john
--
"Allocation is a fatal error."
- me, cpd_util.c. Never document at 4AM
John Levon [EMAIL PROTECTED] writes:
| Can Sectioning.[Ch] be deleted ? Not used as far as I can see.
No, but it will be. Sectioning will be the companion of
InsetSectioning.
| Also can I rip out the keymap dialog ? It's not currently used
| and I don't fancy porting it to GUII.
Do we have an
On 19 Feb 2001, Lars Gullik Bjønnes wrote:
John Levon [EMAIL PROTECTED] writes:
| Can Sectioning.[Ch] be deleted ? Not used as far as I can see.
No, but it will be. Sectioning will be the companion of
InsetSectioning.
ok
| Also can I rip out the keymap dialog ? It's not currently
Can Sectioning.[Ch] be deleted ? Not used as far as I can see.
Also can I rip out the keymap dialog ? It's not currently used
and I don't fancy porting it to GUII.
john
--
"Allocation is a fatal error."
- me, cpd_util.c. Never document at 4AM
John Levon <[EMAIL PROTECTED]> writes:
| Can Sectioning.[Ch] be deleted ? Not used as far as I can see.
No, but it will be. Sectioning will be the companion of
InsetSectioning.
| Also can I rip out the keymap dialog ? It's not currently used
| and I don't fancy porting it to GUII.
Do we have
On 19 Feb 2001, Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | Can Sectioning.[Ch] be deleted ? Not used as far as I can see.
>
> No, but it will be. Sectioning will be the companion of
> InsetSectioning.
>
ok
> | Also can I rip out the keymap dialog ? It's not
28 matches
Mail list logo
