On 9/29/12 5:51 PM, Tommaso Cucinotta wrote:
On 29/09/12 15:10, Richard Heck wrote:
Since preferences have been changed, the preference format needs to
be updated in LyXRC.cpp, and, in this case, a trivial conversion
needs to be added to prefs2prefs-prefs.py.
is this needed also in such a cas
Let me propose to rework the menus arrangement:
-) move "new window" and "close window" from the File to the View menu
-) move the Insert menu right after the Edit one, so to keep editing
actions closer to each other
-) in View menu, clearly separate entries that affect the way LyX
appears, fro
On 29/09/12 15:10, Richard Heck wrote:
Since preferences have been changed, the preference format needs to be
updated in LyXRC.cpp, and, in this case, a trivial conversion needs to
be added to prefs2prefs-prefs.py.
is this needed also in such a case, when a new preference option is
added ? Wi
Am 29.09.2012 um 17:17 schrieb Liviu Andronic :On Sat, Sep 29, 2012 at 4:18 PM, Stephan Witt wrote:Unfortunately not the display of the text in the main work area.This is my next adventure with LyX and perhaps too late for 2.0.5.It is already possible to zo
Richard Heck wrote:
> It's fine with me if changes made all about the same time get grouped
> together but, in general, we should update the format each time we change
> an LFUN.
>From what I understood all lfun related conversions to LyX 2.0 get as a
single format, so I started format version
On 09/29/2012 10:12 AM, Juergen Spitzmueller wrote:
The branch, master, has been updated.
- Log -
commit c9f9107a7fd481ed8c1f4e9ada54976184254b4e
Author: Juergen Spitzmueller
Date: Sat Sep 29 16:12:31 2012 +0200
Fix issues
On 09/29/2012 01:19 PM, Pavel Sanda wrote:
Pavel Sanda wrote:
Jürgen Spitzmüller wrote:
All these need prefs2prefs changes (else, custom shortcuts will break).
Thanks for reminder. P
Richard, prefs2prefs_lfuns.py does not have any format structure. Is it OK
just to add these?
I guess we have
On 09/29/2012 10:18 AM, Stephan Witt wrote:
Am 29.09.2012 um 16:08 schrieb Richard Heck :
Is this safe for 2.0.5?
Yes, it's save and should be done.
OK, please backport, then.
rh
Pavel Sanda wrote:
> Jürgen Spitzmüller wrote:
> > All these need prefs2prefs changes (else, custom shortcuts will break).
>
> Thanks for reminder. P
Richard, prefs2prefs_lfuns.py does not have any format structure. Is it OK
just to add these?
Pavel
diff --git a/lib/scripts/prefs2prefs_lfuns.py
Jürgen Spitzmüller wrote:
> All these need prefs2prefs changes (else, custom shortcuts will break).
Thanks for reminder. P
Am Samstag 29 September 2012, 18:07:19 schrieb Pavel Sanda:
> The branch, master, has been updated.
>
> - Log -
>
> commit 541828ebf50876780d90766d84ba01246440c9be
> Author: Pavel Sanda
> Date: Sat Sep 29 18:06:42 2012 +0200
>
>
Am Samstag, 29. September 2012 um 18:26:19, schrieb Pavel Sanda
> Kornel Benko wrote:
> > As I see it, it _is_ used inside frontends/qt4. But at least in cmake build
> > is is rebuilt if it does not exist.
>
> What's the point of maintaining such beast if it can be (re)created? P
Kill it.
Kornel Benko wrote:
> As I see it, it _is_ used inside frontends/qt4. But at least in cmake build
> is is rebuilt if it does not exist.
What's the point of maintaining such beast if it can be (re)created? P
Am Samstag, 29. September 2012 um 18:10:53, schrieb Kornel Benko
> Am Samstag, 29. September 2012 um 17:33:22, schrieb Pavel Sanda
>
> > Pavel Sanda wrote:
> > > Pavel Sanda wrote:
> > > > commit a72b75c50cd2017f37115af4da83502a47418db5
> > > > Author: Pavel Sanda
> > > > Date: Sat Sep 29 17
Hi,
break-paragraph-keep-layout is LFUN outdated for a long time,
we still have it in these manuals:
lib/doc/de/UserGuide.lyx
lib/doc/eu/Customization.lyx
lib/doc/eu/Customization.lyx
lib/doc/sk/UserGuide.lyx
For more info see http://www.lyx.org/trac/changeset/20846/lyxsvn .
If you are maintaine
Am Samstag, 29. September 2012 um 17:21:22, schrieb Pavel Sanda
> The branch, master, has been updated.
>
> - Log -
>
> commit 4083bcb62bb54ae66a53bae4aa6d1961cb315dc2
> Author: Pavel Sanda
> Date: Sat Sep 29 17:21:05 2012 +0200
Am Samstag, 29. September 2012 um 17:33:22, schrieb Pavel Sanda
> Pavel Sanda wrote:
> > Pavel Sanda wrote:
> > > commit a72b75c50cd2017f37115af4da83502a47418db5
> > > Author: Pavel Sanda
> > > Date: Sat Sep 29 17:16:52 2012 +0200
> > >
> > > Proper naming for tab-group-close.
> > >
> > >
Pavel Sanda wrote:
> Pavel Sanda wrote:
> > commit a72b75c50cd2017f37115af4da83502a47418db5
> > Author: Pavel Sanda
> > Date: Sat Sep 29 17:16:52 2012 +0200
> >
> > Proper naming for tab-group-close.
> >
> > diff --git a/development/qmake/Resources.qrc
> > b/development/qmake/Resources.qr
Pavel Sanda wrote:
> commit a72b75c50cd2017f37115af4da83502a47418db5
> Author: Pavel Sanda
> Date: Sat Sep 29 17:16:52 2012 +0200
>
> Proper naming for tab-group-close.
>
> diff --git a/development/qmake/Resources.qrc b/development/qmake/Resources.qrc
> index 13262b5..0707698 100644
> ---
On Sat, Sep 29, 2012 at 4:18 PM, Stephan Witt wrote:
> Unfortunately not the display of the text in the main work area.
> This is my next adventure with LyX and perhaps too late for 2.0.5.
>
It is already possible to zoom the text in the main work area. Doesn't
this suffice?
Liviu
Am 29.09.2012 um 16:08 schrieb Richard Heck :
>
> Is this safe for 2.0.5?
Yes, it's save and should be done.
It improves the display of system drawn text.
Open file dialog or Source preview e. g.
Unfortunately not the display of the text in the main work area.
This is my next adventure with LyX
On 09/28/2012 06:18 PM, Tommaso Cucinotta wrote:
The branch, master, has been updated.
- Log -
commit 4985015e8939df78a8d29c31aa04bc28caa3a47f
Author: Tommaso Cucinotta
Date: Sat Sep 15 23:37:55 2012 +0100
Now LyX closes t
On Sat, Sep 29, 2012 at 6:37 AM, André Pönitz
wrote:
> On Sat, Sep 29, 2012 at 04:53:00AM -0400, Scott Kostyshak wrote:
>> I have been thinking about compiler warnings because of the recent
>> discussion here:
>> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg175099.html
>>
>> >From that t
On Sat, Sep 29, 2012 at 04:53:00AM -0400, Scott Kostyshak wrote:
> I have been thinking about compiler warnings because of the recent
> discussion here:
> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg175099.html
>
> >From that thread, I have the understanding that some developers think
>
Le 29 sept. 2012 à 11:02, Jürgen Spitzmüller a écrit :
> Richard Heck wrote:
>>> Is there a (VERY simple) way to fix that, or must I wait for an update?
>>
>> I believe this is being fixed for 2.0.5. Stephan?
>
> Only in trunk, apparently:
> http://www.lyx.org/trac/changeset/99e53ffce04337cc50
Richard Heck wrote:
> > Is there a (VERY simple) way to fix that, or must I wait for an update?
>
> I believe this is being fixed for 2.0.5. Stephan?
Only in trunk, apparently:
http://www.lyx.org/trac/changeset/99e53ffce04337cc50c9cfbdb900e66064d450ed/lyxgit
Would be worth backporting, I suppose
I have been thinking about compiler warnings because of the recent
discussion here:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg175099.html
>From that thread, I have the understanding that some developers think
it's important to fix warnings, although not if it is risky. I don't
have mu
27 matches
Mail list logo