Guillaume Munch wrote:
> Actually yes I am documenting a new rule, but it isn't mine. The new
> rule requires a LFUN format increment and a LyX format increment
Do you have by chance link to LFUN format increment discussion at hand?
(I have no clue what is meant by LFUN format number). P
Compiling lyX 2.2.dev gives me this error because the ReplaceValues.py
cannot yet handle the origin unavailable tag:
Generating de/Customization.lyx
Traceback (most recent call last):
File "D:/LyXGit/Master/development/cmake/doc/ReplaceValues.py",
line 55, in
Am 11.01.2016 um 16:20 schrieb Kornel Benko:
Done.
Thanks Kornel.
For master I will wait until Uwe added the docs waiting for being processed.
I just updated the files there so you can go ahead. I'll take care of
your changes when committing the Spanish files that are work in progress.
On Mon, Jan 11, 2016 at 06:12:01PM +, Guillaume Munch wrote:
> the LyX format. There is an agreement from Georg, Jean-Marc and Richard;
> and I did not see any opposition to this rule during the discussion of
> this requirement for my patch.
Please go ahead then. Thanks for being so careful.
Am 11.01.2016 um 21:22 schrieb Georg Baum:
I don't know whether he got them from you or directly from the original
download pages, but this does not matter. What matters is that you get a
consistent build and eliminate possible errors if you use these sources (by
enabling the 3RDPARTY_BUILD
On Mon, Jan 11, 2016 at 12:45:11AM +0100, Uwe Stöhr wrote:
> My question: what is the plan for LyX 2.2.0: Do we release with Qt 5.6 or
> not? Should I try out its beta version?
My opinion is that we should only use Qt 5.6 for the final LyX 2.1
release if we use Qt 5.6beta for LyX 2.1beta1. From
Am Dienstag, 12. Januar 2016 um 00:25:37, schrieb Uwe Stöhr
> Am 11.01.2016 um 23:50 schrieb Kornel Benko:
>
> > it is -DLYX_3RDPARTY_BUILD=ON added to the call to cmake.
>
> I tried this but it won't work.
>
> What I did now is:
> - delete everything from CMake (cache)
> - run
Am 12.01.2016 um 00:25 schrieb Uwe Stöhr:
GuiBibtex.cpp
..\..\..\..\src\frontends\qt4\GuiApplication.cpp(134): fatal error
C1083: Datei (Include) kann nicht geöffnet werden: "QWinMime": No such
file or directory
[D:\LyXGit\Master\compile-2010\src\frontends\qt4\frontend_qt.vcxproj]
This is
On Mon, Jan 11, 2016 at 06:28:02PM +, Guillaume Munch wrote:
> Le 09/01/2016 00:15, Scott Kostyshak a écrit :
> >
> >Does any one view an issue as a beta blocker?
>
> The situation with the parbreak separator is not good and I would see
> changing its symbol and fixing the insertion of an
Am Montag, 11. Januar 2016 um 23:37:12, schrieb Uwe Stöhr
> Am 11.01.2016 um 21:22 schrieb Georg Baum:
>
> > I don't know whether he got them from you or directly from the original
> > download pages, but this does not matter. What matters is that you get a
> > consistent build
Am Montag, 11. Januar 2016 um 23:21:08, schrieb Uwe Stöhr
> Am 11.01.2016 um 16:20 schrieb Kornel Benko:
>
> > Done.
>
> Thanks Kornel.
>
> > For master I will wait until Uwe added the docs waiting for being processed.
>
> I just updated the files there so you can go ahead.
Am 11.01.2016 um 23:50 schrieb Kornel Benko:
it is -DLYX_3RDPARTY_BUILD=ON added to the call to cmake.
I tried this but it won't work.
What I did now is:
- delete everything from CMake (cache)
- run Cmake from scratch
This way found bugs:
* for hunspell_include_dir I get this path:
Am 11.01.2016 um 20:44 schrieb Georg Baum:
welcome back and a happy new year!
Thanks. The same to you.
As I wrote in the "questions" mail: I am pretty sure that using the sources
in 3rdparty instead of the precompiled binary dependencies will result in a
better build and less work. Please
On Mon, Jan 11, 2016 at 10:12:19PM +0100, Kornel Benko wrote:
> Am Montag, 11. Januar 2016 um 21:08:17, schrieb Georg Baum
>
> > Guenter Milde wrote:
> >
> > > In normal inter-release development times, I think it is too restricting
> > > to insist on tested
Am Montag, 11. Januar 2016 um 11:14:30, schrieb Jean-Marc Lasgouttes
> Le 11/01/2016 11:07, Pavel Sanda a écrit :
> > Kornel Benko wrote:
> >> This all is getting more and more confusing. Too complicated (at least for
> >> me)
> >
> > You edit document.
> > You decide to use
Georg Baum wrote:
> Guillaume Munch wrote:
>
> > I agree that the current situation regarding \output_change and
> > \tracking_change is bad and should be fixed. I gave what I think is the
> > proper solution, taking into account the debate that was on the list.
> > The patch is very simple (see
Jean-Marc Lasgouttes wrote:
> Le 07/01/2016 06:10, Pavel Sanda a écrit :
>> The way to reproduce:
>> my keyboard autorepeat:
>> 1.xset r rate 300 180
>> 2. launch lyx & tutorial & fullscreen
>> 3. hold right arrow key until you get to the end of the
>> first page and then left arrow until you
Le 08/01/2016 22:30, Georg Baum a écrit :
It will never be possible to detect every compiler and lib combination
correctly (otherwise the switches to override the automatism would not be
needed). This is a rare combination, so it is not too important IMHO.
The patch is definitely better than
Le 08/01/2016 22:39, Georg Baum a écrit :
Jean-Marc Lasgouttes wrote:
The following patch fixes compilation for me with clang and libc++ (with
autotools I set CXX="clang++ --stdlib=libc++").
This is a workaround to https://llvm.org/bugs/show_bug.cgi?id=24137
to be fixed in 3.7.1 or 3.8.0.
Am Montag, 11. Januar 2016 um 01:38:28, schrieb Pavel Sanda
> Georg Baum wrote:
> > Guillaume Munch wrote:
> >
> > > I agree that the current situation regarding \output_change and
> > > \tracking_change is bad and should be fixed. I gave what I think is the
> > > proper solution,
Le 11/01/2016 10:59, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
I reproduce the svg you sent for 2.2, since it is not so large either :)
More important is - can you reproduce the behaviour? It's pretty clear on my
machine without trying any special conditions, just high repeat rate of
Kornel Benko wrote:
> This all is getting more and more confusing. Too complicated (at least for me)
You edit document.
You decide to use git.
You set up the look/behaviour things your care about ('Is CT ON/OFF')
You freeze those settings so working with git is less annoying.
.. and sometimes
Le 11/01/2016 11:07, Pavel Sanda a écrit :
Kornel Benko wrote:
This all is getting more and more confusing. Too complicated (at least for me)
You edit document.
You decide to use git.
You set up the look/behaviour things your care about ('Is CT ON/OFF')
You freeze those settings so working
Guillaume Munch wrote:
> I understand this idea of "freezing" the setting, in order to set a
> custom value on opening. The current approach I have in mind is to read
> and save to a per-user-per-document (cursor-location-like) setting when
> save_user_preferences is false, so that the value on
On Thu, Jan 07, 2016 at 01:48:59PM -0800, Pavel Sanda wrote:
> Georg Baum wrote:
> > Pavel Sanda wrote:
> >
> > > Scott Kostyshak wrote:
> > >>
> > >> Can you reproduce now?
> > >
> > > Nope. Smells like automake/autoconf versions. What is your config?
> >
> > These versions produce the error
Am Montag, 11. Januar 2016 um 21:08:17, schrieb Georg Baum
> Guenter Milde wrote:
>
> > In normal inter-release development times, I think it is too restricting
> > to insist on tested regression-free patches.
>
> I can only recommend to try to always work like
Guillaume Munch wrote:
> I replace stored alignment and spacing values with computed values, only
> in the case of specific grids under discussion (Eqnarray, AMS...). Thus,
> defaultColAlign() can still make sense in the future for grids that rely
> on stored alignment and spacing, and I do not
Uwe Stöhr wrote:
> Am 10.01.2016 um 22:21 schrieb Scott Kostyshak:
>
>> G1. Not a question but a prerequisite IMHO: The 2.2.0 release should also
>> build the prerequisite from the sources Peter added, using exactly the
>> same compiler as is used to build LyX.
>
> It seems the sources Peter
Jean-Marc Lasgouttes wrote:
> What is BTW the reason why you skip recordUndo in these cases?
My understanding is that these changes do not modify the document if
store_user_prefs is false, and therefore nothing can be undone.
Georg
Le 11/01/2016 20:30, Georg Baum a écrit :
Jean-Marc Lasgouttes wrote:
What is BTW the reason why you skip recordUndo in these cases?
My understanding is that these changes do not modify the document if
store_user_prefs is false, and therefore nothing can be undone.
Yes. BTW this
Am 11.01.2016 um 12:01 schrieb Kornel Benko :
>
> Am Montag, 11. Januar 2016 um 11:14:30, schrieb Jean-Marc Lasgouttes
>
>> Le 11/01/2016 11:07, Pavel Sanda a écrit :
>>> Kornel Benko wrote:
This all is getting more and more confusing. Too complicated
Le 08/01/2016 23:22, Guillaume Munch a écrit :
Thank you, waiting for Jean-Marc's opinion then.
A few comments on the patches. I was not able to apply them using "git
am" I am not sure how they were produced.
0001:
* fix the log title (.sh, not .py)
0002:
* be careful to update the
Le 09/01/2016 00:50, Richard Heck a écrit :
On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:
Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.
Fine with me, and I see the same warnings.
I ran the
On 2016-01-08, Scott Kostyshak wrote:
Dear Scott,
> In the future, I would prefer for the test output not to change (i.e.
> no planning of subsequent cleanup patches). Everything should be done
> in one patch.
I don't think a cleanup patch is ever planned ;-)
In the current pre-release time,
On 01/11/2016 05:10 AM, Jean-Marc Lasgouttes wrote:
>
> At some time, I convinced my self that there is as much time spent in
> toolbar updates than in painting itself. The reason is (would be) that
> it uses BufferParams::isExportable which does a full graph search in
> converters for each icon
Le 11/01/2016 18:12, Richard Heck a écrit :
On 01/11/2016 05:10 AM, Jean-Marc Lasgouttes wrote:
At some time, I convinced my self that there is as much time spent in
toolbar updates than in painting itself. The reason is (would be) that
it uses BufferParams::isExportable which does a full
> Below is a review of the broken links.
>
> > Error url: "http://www.tex.ac.uk/cgi-bin/texfaq2html;
> > lib/doc/de/UserGuide.lyx:u46086
> > lib/doc/es/UserGuide.lyx:u47069
> > lib/doc/fr/UserGuide.lyx:u48670
> > lib/doc/ja/UserGuide.lyx:u39540
> > lib/doc/UserGuide.lyx:u46528
>
> If
Le 10/01/2016 23:56, Guillaume Munch a écrit :
Some questions on the second patch:
1/ can OUTPUT_CHANGES be toggled for a read-only document if user prefs
are not stored?
No. Currently one cannot enable "output changes" on a
read-only document (on 2.1.5dev). If you think that this is a bug,
Le 11/01/2016 16:33, Guillaume Munch a écrit :
Thus the per-user approach encompasses a wider set of use-cases,
overlaps less with the current behaviour, and is simpler to explain and
understand. Moreover, storing always the same value "false" is similar
to what is done in LibreOffice's
Am Montag, 11. Januar 2016 um 15:41:21, schrieb jeanpierre.chret...@free.fr
>
> > Below is a review of the broken links.
>
> >
> > > Error url: "http://www.tex.ac.uk/cgi-bin/texfaq2html;
> > > lib/doc/de/UserGuide.lyx:u46086
> > > lib/doc/es/UserGuide.lyx:u47069
> > >
Le 11/01/2016 10:14, Jean-Marc Lasgouttes a écrit :
Le 11/01/2016 11:07, Pavel Sanda a écrit :
Kornel Benko wrote:
This all is getting more and more confusing. Too complicated (at
least for me)
You edit document.
You decide to use git.
You set up the look/behaviour things your care about
Le 09/01/2016 00:15, Scott Kostyshak a écrit :
Does any one view an issue as a beta blocker?
The situation with the parbreak separator is not good and I would see
changing its symbol and fixing the insertion of an empty environment
before with Enter (described at the beginning of
Le 08/01/2016 22:26, Scott Kostyshak a écrit :
On Fri, Jan 08, 2016 at 11:06:04PM +0100, Georg Baum wrote:
Guillaume Munch wrote:
Also, because it took me a while to
figure out where the bind and ui format was defined. Nothing was
documented. (Is there a maintainer for Development.lyx who
Jean-Marc Lasgouttes wrote:
> I ran the extract.sh script, and have a 3MB commit. Is that to be
> expected? It compiles without warning (using a small additional fix).
>
> Shall I just push it? Does someone want to see it or have a go at it?
The few times I did run that script it worked fine.
Guillaume Munch wrote:
> Le 10/01/2016 19:08, Georg Baum a écrit :
>>
>> You don't need to do anything in tex2lyx besides writing the new
>> parameter with a default value as you did in the patch.
>
> I mean it for the tests, as I have no familiarity with the latter.
This is easy: How to update
Guillaume Munch wrote:
> Thus the per-user approach encompasses a wider set of use-cases,
> overlaps less with the current behaviour, and is simpler to explain and
> understand. Moreover, storing always the same value "false" is similar
> to what is done in LibreOffice's corresponding feature
Guenter Milde wrote:
> In normal inter-release development times, I think it is too restricting
> to insist on tested regression-free patches.
I can only recommend to try to always work like that. I know it does not
sound convincing (you really have to try it out), but I made the experience
Jean-Marc Lasgouttes wrote:
> Le 10/01/16 22:17, Guillaume Munch a écrit :
>> Since you have gotten a +1 from somebody else, sure. I was not so sure
>> myself, so I wanted to offer an alternative that was sure to be safe. I
>> think this will have to be done nevertheless, so I am going to keep it
Hi Uwe,
welcome back and a happy new year!
Uwe Stöhr wrote:
> I can compile LyX 2.2dev with
> - Qt 4.8.7 and MSVC 2010
> - Qt 5.5.1 and MSVC 2013 (the resulting build has problems I already
> reported in December, but the compilation itself works)
>
> But if I use
> - Qt 5.5.1 and MSVC 2010
>
49 matches
Mail list logo