On 13-Jan-13 4:53 AM, Uwe Stöhr wrote:
Am
03.01.2013 09:04, schrieb Zohar Levi:
My friend,
I am no your friend and I don't understand why you are impolite. I
only wanted to help you.
I'm not into se
Am 28.12.2012 11:21, schrieb Jürgen Spitzmüller:
I have implemented now the possibility to place (inset-inserted) arguments
after the main (workarea-inserted) argument for commands.
Such arguments have the prefix "post:", i.e.
Argument post:1
Hello Jürgen,
as I promised I had a look and test
Am 03.01.2013 09:04, schrieb Zohar Levi:
My friend,
I am no your friend and I don't understand why you are impolite. I only wanted
to help you.
I'm not into semantics here if it's a bug, feature, my fault or not.
I want to use sub-figures in a siggraph teaser.
You can of course do what yo
Back on the bisection trail
I'm having more trouble building from source for this bisection.
When trying to build 2.0.0, I got
LyX only supports automake 1.8 to 1.11.
Macports made it easy to roll back from 1.12.5 or the like to some version of
1.11, at which point I got:
LyX only sup
On Sat, Jan 12, 2013 at 7:24 AM, Jean-Marc Lasgouttes
wrote:
> Le 12/01/13 07:14, Scott Kostyshak a écrit :
>
>> @@ -2760,7 +2760,7 @@ void LyXRC::write(ostream & os, bool
>> ignore_system_lyxrc, string const & name) c
>> || sysfmt == sysend //
>>
On Sat, Jan 12, 2013 at 11:26 AM, Jürgen Spitzmüller wrote:
> Julien Rioux wrote:
>> Should we kill the Custom submenu then?
>
> We need to have a good alternative first.
>
I think a good starting point would be fixing
http://www.lyx.org/trac/ticket/7877 . This looks like a relatively
easyfix, but
On 12/01/2013 11:34 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
The goal is to translate these strings (using mo database) to the
document language.
Then Buffer::B_() is the correct approach.
Jürgen
Thank you, I'll try that.
Regards,
Julien
Julien Rioux wrote:
> The goal is to translate these strings (using mo database) to the
> document language.
Then Buffer::B_() is the correct approach.
Jürgen
On 12/01/2013 11:19 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
Hmmm, this removal is surely caused by
http://www.lyx.org/trac/changeset/62b131975244d6f389d2c2c43bf8a982a057f00f/l
yxgit ... but for the fix to be effective, the translations should remain
available in the po file for these s
Julien Rioux wrote:
> Hmmm, this removal is surely caused by
> http://www.lyx.org/trac/changeset/62b131975244d6f389d2c2c43bf8a982a057f00f/l
> yxgit ... but for the fix to be effective, the translations should remain
> available in the po file for these strings.t I guess gettext does not catch
> the
On Sat, Jan 12, 2013 at 10:54 AM, Juergen Spitzmueller wrote:
> The branch, 2.0.x, has been updated.
>
> - Log -
>
> commit e5a40e9616d4ab82ed092de22bdc8969eedfc051
> Author: Juergen Spitzmueller
> Date: Sat Jan 12 16:54:11 2013 +0
On 12/01/2013 10:48 AM, Richard Heck wrote:
On 01/12/2013 10:44 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
The branch, 2.0.x, has been updated.
insets/InsetCitation.cpp: In constructor
‘lyx::InsetCitation::InsetCitation(lyx::Buffer*, const
lyx::InsetCommandParams&)’:
insets/InsetCitatio
On 01/12/2013 10:44 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
The branch, 2.0.x, has been updated.
insets/InsetCitation.cpp: In constructor
‘lyx::InsetCitation::InsetCitation(lyx::Buffer*, const
lyx::InsetCommandParams&)’:
insets/InsetCitation.cpp:49:11: error: ‘class lyx::Buffer’ has n
On 12/01/2013 10:44 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
The branch, 2.0.x, has been updated.
insets/InsetCitation.cpp: In constructor
‘lyx::InsetCitation::InsetCitation(lyx::Buffer*, const
lyx::InsetCommandParams&)’:
insets/InsetCitation.cpp:49:11: error: ‘class lyx::Buffer’ has
Julien Rioux wrote:
> The branch, 2.0.x, has been updated.
insets/InsetCitation.cpp: In constructor
‘lyx::InsetCitation::InsetCitation(lyx::Buffer*, const
lyx::InsetCommandParams&)’:
insets/InsetCitation.cpp:49:11: error: ‘class lyx::Buffer’ has no member named
‘removeBiblioTempFiles’
insets/In
Le 12/01/13 07:14, Scott Kostyshak a écrit :
@@ -2760,7 +2760,7 @@ void LyXRC::write(ostream & os, bool ignore_system_lyxrc,
string const & name) c
|| sysfmt == sysend // format
not found
|| sysfmt->secon
Julien Rioux wrote:
> Should we kill the Custom submenu then?
We need to have a good alternative first. We cannot simply put all custom
insets to the top level menu, since this is too large already.
I suppose we should define multiple "anchors" in the menu where custom insets
could be assigned
On 12/01/2013 4:54 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
I think both X and Y should appear under Insert > Custom.
Agreed?
If you refer to InsetArgument: No.
All arguments should appear at the same place, namely the inset top level
menu.
Actually, I think that the "Custom" submen
Julien Rioux wrote:
> I think both X and Y should appear under Insert > Custom.
>
> Agreed?
If you refer to InsetArgument: No.
All arguments should appear at the same place, namely the inset top level
menu.
Actually, I think that the "Custom" submenu is horrible UI design. Likewise
Edit > cha
Custom InsetLayout X has an Argument Y. We have:
Insert > Custom > X, but
Insert > Y
I think both X and Y should appear under Insert > Custom.
Agreed?
Julien
Hi Tommaso,
I wanted to check the description of controls in hello-world-in.txt with the
script keytest.py.
So far, there exist some non-described controls
Sleep
Loop
RaiseLyx
.
OK, 'Sleep' was easy.
But what should 'Loop' do? At least in keytest.py there you can find:
21 matches
Mail list logo
