Pavel Sanda wrote:
> i made a minimalistic backport upon the user request.
Fine with me. Please add the bug number to the status.15x entry, though.
Jürgen
Pavel Sanda wrote:
Can't we just put the comments in the C++ file?
This would even let us the keep the 'historical' lfun order.
in case your clean-coding heart can accept this patch, i can move
the doxies to .cpp file.
That's a bit weird but I am fine with it provided that you explain the
'
> Log:
> Add characters counting.
i made a minimalistic backport upon the user request.
Juergen?
Index: src/buffer_funcs.h
===
--- src/buffer_funcs.h (revision 22485)
+++ src/buffer_funcs.h (working copy)
@@ -56,6 +56,9 @@
/// Co
Pavel Sanda wrote:
the moment you put it outside of the lfuns.h into another file doxygen wont find it. i tried various
"lyx::" & "kb_action::" prefixes permutations wihtout success.
!$!$#%^*&%$&*&%#%#$%@@@ !
/*cough*/ /*cough*/
one spends hours of reading various docs to finally find
> Can't we just put the comments in the C++ file?
>
> This would even let us the keep the 'historical' lfun order.
in case your clean-coding heart can accept this patch, i can move
the doxies to .cpp file.
pavel
diff --git a/src/LyXAction.cpp b/src/LyXAction.cpp
index 243e2f9..513257a 100644
---
> > Following this idea, the dox comment would look like this in
> > LyXAction::init():
> >
> >
> > ev_item const items[] = {
> > /** \var kb_action::LFUN_ACCENT_ACUTE
>
> fyi /*! \var
>
> > * \li Action:
> > * \li Syntax:
> > *
Ich schrieb:
The attached patch renames the math numbering functions correctly.
The last patch was not ready, take this one instead.
regards Uwe
Index: lib/bind/math.bind
===
--- lib/bind/math.bind (revision 22480)
+++ lib/bind/m
The attached patch renames the math numbering functions correctly. This fixes bug
http://bugzilla.lyx.org/show_bug.cgi?id=2608 .
regards Uwe
Index: lib/ui/stdmenus.inc
===
--- lib/ui/stdmenus.inc (revision 22480)
+++ lib/ui/stdmenus
On Donnerstag 10 Januar 2008, Hans Meine wrote:
> No; you see that the menu item is checked, so you see that the
> corresponding setting is enabled. I wanted to post the authoritative KDE
> styleguide answer to this, but I cannot find any long discussion of this
> topic anymore (I know this came u
On Donnerstag 10 Januar 2008, Uwe Stöhr wrote:
> Jean-Marc Lasgouttes schrieb:
> > No, when the line is numbered I see
> > [X] Number this line
> > which is pretty clear.
>
> I still don't get it: When the formula is already numbered I see a
> checkmark indeed, but the menu name still states that
Jean-Marc Lasgouttes schrieb:
No, when the line is numbered I see
[X] Number this line
which is pretty clear.
I still don't get it: When the formula is already numbered I see a checkmark indeed, but the menu
name still states that the menu will number the formula.
When it is not clear for m
> * alpha 1 - 15 February
Right about time embedding can be tested publicly. The basic
infrastructure is there but to make sure embedding works smoothly
across platforms, under all editing operations would be a challenge.
Bo
> > > I would expect ../blah as valid relative file...
> >
> > BrowseFile is supposed to return an absolute path.
Can I apply my proposed patch? I do not see any negative side effect of it.
Bo
Andre Poenitz wrote:
On Thu, Jan 10, 2008 at 01:45:23AM -0500, rgheck wrote:
When lyx2lyx fails with an error:
gdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quiet(gdb) quitgdb
Completely unrelated out of interest: Why do you use --interpreter=mi2?
It does not give any advantages
Hi,
I think that now the major changes have landed in development we are
ready to
prepare the next stable version.
So (without further) delays I propose the following schedule for the
next two
releases:
* alpha 1 - 15 February
* beta 1 - 15 March
As us
On Thu, Jan 10, 2008 at 01:45:23AM -0500, rgheck wrote:
>
> When lyx2lyx fails with an error:
> gdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quiet(gdb) quitgdb
Completely unrelated out of interest: Why do you use --interpreter=mi2?
It does not give any advantages when used 'manually', does
Jürgen Spitzmüller wrote:
> No. Have a look at the method layouts_l10n in lyx_pot.py for a model.
You might also have to tweak Makefile and Scons. Have a look here for how I
did something similar to translate the external inset files (the first two
chunks of the patch are not relevant):
http://w
rgheck wrote:
> So, we need some code in po/lyx_pot.py. Do I then just pass the relevant
> strings through qt_()? E.g., something like: QString desc =
> qt_(module.getDescription())?
No. Have a look at the method layouts_l10n in lyx_pot.py for a model.
BTW I think the layouts/ folder gets a bit c
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes wrote:
>> Uwe Stöhr <[EMAIL PROTECTED]> writes:
>>
>>> But no matter, this menu entry still toggles the numbering: Use it on
>>> an already numbered formula and you get it unnumbered. This behaviour
>>> is OK and shouldn't be tou
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
There is a text object (Buffer::Impl::inset) but Text::pars_ is empty
on construction. Maybe we should create an empty paragraph there.
I see now. I you say it is safe, I believe you. But adding an empty
paragra
Abdelrazak Younes wrote:
rgheck wrote:
It's hard to tell with all the optimization in the code,
So this isn't a debug build?
Yes, it is. I mean the debugger reports that the crucial variables are
optimized out, so I can't be sure what they are.
but it looks like the error is here:
Paragr
Abdel wrote:
>Jean-Marc Lasgouttes wrote:
> [X] Number this line
>[X] Line numbering activated
why not a bit less verbose:
[X] Line Number
Jean-Marc Lasgouttes wrote:
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
rgheck wrote:
By the way: Anyone have views about translation issues here? I haven't
addressed those and don't have much (well, any) experience with that
sort of issue. A proper solution would involve having tra
Jean-Marc Lasgouttes wrote:
Uwe Stöhr <[EMAIL PROTECTED]> writes:
But no matter, this menu entry still toggles the numbering: Use it on
an already numbered formula and you get it unnumbered. This behaviour
is OK and shouldn't be touched. But the menu entry should still have
the word "toggled" a
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> But no matter, this menu entry still toggles the numbering: Use it on
> an already numbered formula and you get it unnumbered. This behaviour
> is OK and shouldn't be touched. But the menu entry should still have
> the word "toggled" as this it what it does.
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> Uwe Stöhr wrote:
>> Where is a checkbox?
>
> You don't see it in the menu?
I think it is a specificity of qt4 on X11 that the checkbox is always
visible. However, the other menu entries that have toggle semantics do
not have Toggle in their name.
Uwe Stöhr wrote:
> Where is a checkbox?
You don't see it in the menu?
> But no matter, this menu entry still toggles the numbering: Use it on an
> already numbered formula and you get it unnumbered. This behaviour is OK
> and shouldn't be touched. But the menu entry should still have the word
> "
> The entries were:
> - Item "Toggle Numbering|N" "math-number"
> - Item "Toggle Numbering of Line|u" "math-nonumber"
>
> Now that there is a checkbox (which is useful IMO), the word 'toggle'
> is not appropriate anymore (already implied by the check mark).
Where is a
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
There is a text object (Buffer::Impl::inset) but Text::pars_ is empty
on construction. Maybe we should create an empty paragraph there.
I see now. I you say it is safe, I believe you. But adding an empty
paragraph would
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> There is a text object (Buffer::Impl::inset) but Text::pars_ is empty
> on construction. Maybe we should create an empty paragraph there.
I see now. I you say it is safe, I believe you. But adding an empty
paragraph would be safer (we do it on new d
Uwe Stöhr <[EMAIL PROTECTED]> writes:
> Hello JMarc,
>
> I'm writing currently a math manual and thus want to have clear menu
> entris. So I'm interested why you renamed the toglle numbering menu
> entry, see my post about this below:
Hello Uwe, sorry if I did not answer earlier to your message.
On Thu, 10 Jan 2008, Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
As you say, alphabetical sort can be done through a script later.
However, this is also true for a thematical order - we could place a
category tag in each entry and then sort according to that tag. E.g.
LFUN-t
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Quite possibly. Text::pars_ is empty at construction and a non-loaded
buffer doesn't change that fact. This commit should do it.
Is this possibility due to your reorganizations?
This is due to additional new checks in
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Quite possibly. Text::pars_ is empty at construction and a non-loaded
> buffer doesn't change that fact. This commit should do it.
Is this possibility due to your reorganizations? You are fixing 1
case, but I suspect many code snippets could fail in
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> rgheck wrote:
>> By the way: Anyone have views about translation issues here? I haven't
>> addressed those and don't have much (well, any) experience with that
>> sort of issue. A proper solution would involve having translations of
>> the module de
Andrey V. Panov wrote:
> > > The entry for "Review":
> > > #: lib/layouts/iopart.layout:72 lib/ui/stdtoolbars.inc:186
> > > msgid "Review"
> > > should be splitted, meanings are different.
> >
> > What are the different meanings?
>
> The first is a kind of article, the second is the name of toolb
rgheck wrote:
It's hard to tell with all the optimization in the code,
So this isn't a debug build?
but it looks
like the error is here:
Paragraph & CursorSlice::paragraph() const
{
return text()->getPar(pit_);
}
and that it's pit_ that is invalid: pit_ is 0, but there's nothing in
text
rgheck wrote:
Abdelrazak Younes wrote:
Please see if this helps:
URL: http://www.lyx.org/trac/changeset/22473
I'll test it tomorrow. Time for bed
Fine. Time to really work for me ;-)
Abdel.
rgheck wrote:
> By the way: Anyone have views about translation issues here? I haven't
> addressed those and don't have much (well, any) experience with that
> sort of issue. A proper solution would involve having translations of
> the module descriptions in the module files themselves, I would sup
Abdelrazak Younes wrote:
Please see if this helps:
URL: http://www.lyx.org/trac/changeset/22473
I'll test it tomorrow. Time for bed
rh
It's hard to tell with all the optimization in the code, but it looks
like the error is here:
Paragraph & CursorSlice::paragraph() const
{
return text()->getPar(pit_);
}
and that it's pit_ that is invalid: pit_ is 0, but there's nothing in
text(). I think
rh
rgheck wrote:
Abdelrazak Younes wrote:
rgheck wrote:
Abdelrazak Younes wrote:
rgheck wrote:
Happened while it was just sitting there. I've seen this several
times.
But this doesn't look like a sane backtrace, did you forgot to type bt?
As non-sane as it may look, that's exactly what I go
[EMAIL PROTECTED] writes:
> As you say, alphabetical sort can be done through a script later.
> However, this is also true for a thematical order - we could place a
> category tag in each entry and then sort according to that tag. E.g.
>
> LFUN-type = Cursor Movement
We already have this in
Abdelrazak Younes wrote:
rgheck wrote:
Abdelrazak Younes wrote:
rgheck wrote:
Happened while it was just sitting there. I've seen this several
times.
But this doesn't look like a sane backtrace, did you forgot to type bt?
As non-sane as it may look, that's exactly what I got when I typed
rgheck wrote:
Abdelrazak Younes wrote:
rgheck wrote:
Happened while it was just sitting there. I've seen this several times.
But this doesn't look like a sane backtrace, did you forgot to type bt?
As non-sane as it may look, that's exactly what I got when I typed bt.
OK.
It seems that t
45 matches
Mail list logo
