master closed today at 22h00 UTC for 2.3.0alpha1

Dear all, As discussed [1], the current plan is to release alpha1 on Saturday. Please do not make any commits to master today after 22h00 UTC until master is open again. Between now and 22h00 UTC, please only make commits that: (1) are very safe and (2) you are confident do not break any

Re: SIGSEGV on luatex export #2

On Thu, Apr 20, 2017 at 11:48:12PM -0400, Scott Kostyshak wrote: > > $1 = (const lyx::support::FileName &) @0x3559560: { > > _vptr.FileName = 0x38ca7d0, > > d = 0x0 > > } > > What information does this tell you? I guess that 0x38ca7d0 is a memory > address of the pointer? Ah so the idea is

Re: CopyrightYear is the correct command name in acmsiggraph-0.92.layout

On Thu, Feb 16, 2017 at 07:06:48PM +0100, Jean-Pierre Chrétien wrote: > Happily, ACM decided to shift to the sole acmart.cls class for all their > publications as Jürgen pointed out (see also > https://www.tug.org/tug2016/slides/veytsman.pdf), and made very recently all > their old class files

Re: [LyX/master] lyx2lyx/lyx_2_2.py: correct reversion of boxes

On Fri, Apr 21, 2017 at 01:05:44AM +0200, Uwe Stöhr wrote: > El 19.04.2017 a las 06:58, Scott Kostyshak escribió: > > > > lyx2lyx/lyx_2_2.py: correct reversion of boxes > > > > git bisect suggests that this commit broke the test > > > >export/doc/Math_lyx21 > > > > Uwe, can you take a

Re: Should LaTeX output from command line be equivalent to GUI?

On Wed, Mar 01, 2017 at 03:10:23PM -0500, Scott Kostyshak wrote: > On Wed, Mar 01, 2017 at 07:05:36PM +0100, Jean-Marc Lasgouttes wrote: > > Le 01/03/2017 à 18:42, Scott Kostyshak a écrit : > > > > It gives me the following output: > > > > > > > > 8548c8548 > > > > <

design patterns used in LyX

Dear all, I would like to improve my understanding of programming and C++ in a way that will help me understand LyX's code better. I'm wondering if: (1) studying design patterns is a reasonable way to achieve that goal (2) what the best way to do that would be (3) which design patterns we

#9841: use Qt's session management?

Please see http://www.lyx.org/trac/ticket/9841 Guillaume proposed to use Qt's session management, which would simplify things. Does anyone have an opinion? I'm not sure if Guillaume would have the time and interest to implement this for 2.3.0, but at least we could make a decision now. Scott

#10400: keyboard shortcut for document settings?

Should we have a keyboard shortcut for document settings, as proposed at http://www.lyx.org/trac/ticket/10400 ? There is a proposal to use ctrl + p, which is now free because we got rid of print. I agree a shortcut would be nice. I have mixed feelings about the particular shortcut ctrl + p,

#10469: patch for putting LyX window on top on Windows

Dear all, I am wondering if we should include racoon's patch at #10469. It can be seen here: http://www.lyx.org/trac/attachment/ticket/10469/0001-Fix-for-10469.patch I would propose that we include it with an OS guard for Windows only for the setWindowState line. I'm not sure anyone

compile-time Qt checks

Anyone interested in using the tool described here to find bugs in our Qt-related code? https://www.kdab.com/uncovering-32-qt-best-practices-compile-time-clazy/ Scott signature.asc Description: PGP signature

Re: Is anyone planning to test TL 2017 pre-test?

On Mon, Apr 10, 2017 at 12:22:26AM -0400, Scott Kostyshak wrote: > Dear all, > > Is anyone planning to test TL 2017 pretest? It begins 16 April [1]. I am > planning to install it and run all of our export tests. Some will surely > fail. And then it will be a question of whether we need to change

Re: SIGSEGV on luatex export #2

On Thu, Apr 20, 2017 at 07:59:05PM +0200, Kornel Benko wrote: > Am Donnerstag, 20. April 2017 um 13:02:32, schrieb Scott Kostyshak > > > On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote: > > > On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote: > >

Re: [LyX/master] special character "allowbreak" (ZWSP), fileformat change

On Thu, Apr 20, 2017 at 11:29:55PM +0200, Günter Milde wrote: > commit f5ac0580ff8f4f1fd34d792f7952fb05d182e162 > Author: Günter Milde > Date: Mon Mar 6 14:49:30 2017 +0100 > > special character "allowbreak" (ZWSP), fileformat change > > New special character to

proper way to check inclusion among DocIterator ?

Hi, is there an easy way to check whether a DocIterator d is positioned within two others a and b ? (that is, going through the document using forwardPos(), one encounters a, then d, then b). AFAIU, DocIterator::operator() just compares nesting levels, but no pos() nor pit() etc. Thanks,

Re: [patch] for LyX 2.2.3 - box reversion lyx2lyx

El 17.04.2017 a las 05:30, Uwe Stöhr escribió: the attached patch fixes several box reversion issues in lyx2lyx. Scott could verify that the conversion to LyX 2.1.x works now as expected. Hi Richard, this patch fixed some issues but Math.lyx uncovered an issue that I introduced with this

Re: [LyX/master] lyx2lyx/lyx_2_2.py: correct reversion of boxes

El 19.04.2017 a las 06:58, Scott Kostyshak escribió: lyx2lyx/lyx_2_2.py: correct reversion of boxes git bisect suggests that this commit broke the test export/doc/Math_lyx21 Uwe, can you take a look? At first I don't understand why I don't get any error or warning when doing lyx

Re: [coverity again] missing move constructors

Le 08/04/2017 à 23:05, Jean-Marc Lasgouttes a écrit : Also, I do not understand this (I know it is the same as the old code) +explicit Inset(Inset const &) : buffer_(0) {} What is this good for? The semantics look quite broken to me. Is this even used? (I guess we should make it private to

New warnings in master

../../src/insets/InsetSpecialChar.cpp: In member function ‘virtual lyx::docstring lyx::InsetSpecialChar::toolTip(const lyx::BufferView&, int, int) const’: ../../src/insets/InsetSpecialChar.cpp:92:9: warning: enumeration value ‘LDOTS’ not handled in switch [-Wswitch] switch (kind_) {

Re: SIGSEGV on luatex export #2

On 20/04/2017 22:28, Guillaume MM wrote: The attached fixes it for me. for me as well, pushed, thanx :-)! T.

Re: [LyX/master] BufferParams: get rid of the HSpace class for mathindent as requested by JMarc

El 20.04.2017 a las 23:17, Uwe Stöhr escribió: I have seen your changes but now LyX has no longer the GlueLength ability as you noted. Sorry. This ability was not in LyX. glue lengths are not allowed as parameter of \setspace. So having HSpace there was indeed never necessary. thanks and

Re: [LyX/master] BufferParams: get rid of the HSpace class for mathindent as requested by JMarc

El 20.04.2017 a las 18:11, Jean-Marc Lasgouttes escribió: I turns out that I committed it by mistake. Please complain if something is wrong. I did in my previous mail and just put in a fix for the error I get. thanks for your work and regards Uwe

Re: [LyX/master] BufferParams: get rid of the HSpace class for mathindent as requested by JMarc

El 19.04.2017 a las 11:58, Jean-Marc Lasgouttes escribió: HSpace is a class that contains a GlueLength, a complex class that handles subleties of a length like 1cm-2mm+3mm. Is that "just a string" to you?? "1cm-2mm+3mm" is a string to me, yes. I did not need the special features of the

Re: beamer editing

Le 20/04/2017 à 23:10, Edwin Leuven a écrit : On 20 Apr 2017, at 22:47, Guillaume MM wrote: At the time I reviewed your patch and pointed out regressions of the new behaviour: . i don’t see any of those regressions Strange,

Re: beamer editing

On 20 Apr 2017, at 22:47, Guillaume MM wrote: > > At the time I reviewed your patch and pointed out regressions of the new > behaviour: . i don’t see any of those regressions (unless i misunderstood you) > I also suggested to

Re: beamer editing

Le 20/04/2017 à 09:40, Edwin Leuven a écrit : hello, quite some time ago i complained about editing frame content in lyx basic frame content is indented and has a standard environment a new line however removes the indent and resets the standard environment to frame to continue editing one

Re: beamer editing

On 20 Apr 2017, at 10:08, Jürgen Spitzmüller wrote: > Am Donnerstag, den 20.04.2017, 09:40 +0200 schrieb Edwin Leuven: >> quite some time ago i complained about editing frame content in lyx >> >> … >> i think the desired/expected behavior is that preserves the >> identing and

Re: Qt terminal message "path is empty"

Le 18/04/2017 à 08:10, Scott Kostyshak a écrit : I've been getting the following message on recent master: QFileSystemWatcher::removePath: path is empty One way to trigger it is to have two different LyX instances open, write "hello" in one of them and select it and copy it and paste it in

Re: SIGSEGV on luatex export #2

Le 20/04/2017 à 19:02, Scott Kostyshak a écrit : On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote: On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote: A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so I guess it's a different bug: 1.

Re: SIGSEGV on luatex export #2

Am Donnerstag, 20. April 2017 um 13:02:32, schrieb Scott Kostyshak > On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote: > > On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote: > > > A 2nd SIGSEGV, involving similar actions, but the crash happens

Re: SIGSEGV on luatex export #2

On 20/04/2017 19:02, Scott Kostyshak wrote: My bisect lead to 244de5d2 but I'm not confident in the bisect (for some revisions I could reproduce once and then not a separate time. I always cleared the cache each time but still had mixed results). When git bisect narrowed in on the commits

templates handling

Dear LyXers, background reading for the "reorganize templates folder" ticket, I found an interesting statement in the Customization guide (5.2.4 Creating templates): Templates are created just like usual documents: using LyX. The only difference is that usual documents contain all possible

Re: SIGSEGV on luatex export #2

On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote: > On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote: > > A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so > > I guess it's a different bug: > > 1. clear your ~/.lyx-trunk/cache/* > > 2.

Re: [LyX/master] BufferParams: get rid of the HSpace class for mathindent as requested by JMarc

Le 19/04/2017 à 18:15, Jean-Marc Lasgouttes a écrit : The attached patches (1) revert your patch and (2) use a Length object instead of HSpace (as well as rename variables with the shorter mathindent name). If it is OK with you I will commit these, and then commit a change to make the

Re: make distcheck: cannot remove '../../po/lyx.pot'

On Thu, Apr 20, 2017 at 04:57:00PM +0200, Jean-Marc Lasgouttes wrote: > Le 01/07/2016 à 03:44, Scott Kostyshak a écrit : > > > I just tried 1.15 with Ubuntu 15.10 and I do get the same error. The > > > mystery remains. > > > > I still see this with current master and Ubuntu 16.04. > > > > Does

Re: make distcheck: cannot remove '../../po/lyx.pot'

Le 01/07/2016 à 03:44, Scott Kostyshak a écrit : I just tried 1.15 with Ubuntu 15.10 and I do get the same error. The mystery remains. I still see this with current master and Ubuntu 16.04. Does the following work for anyone on current master? git reset --hard && git clean -xdf &&

Re: Re-organizing templates and examples folders (#8715)

Am 20.04.2017 um 14:27 schrieb Helge Hafting : > > Den 11. april 2017 19:05, skrev Guenter Milde: > >> * Under Linux, the local templates are in ~/.lyx/templates >> I have set this as my templates path in Tools>Settings and >> in this dir a symlink to the standard

Re: Re-organizing templates and examples folders (#8715)

Den 11. april 2017 19:05, skrev Guenter Milde: * Under Linux, the local templates are in ~/.lyx/templates I have set this as my templates path in Tools>Settings and in this dir a symlink to the standard templates. Nice trick - but user friendliness ought to be the default. When

Re: Re-organizing templates and examples folders (#8715)

On 2017-04-11, Guenter Milde wrote: > On 2017-04-06, Scott Kostyshak wrote: >> There is a proposal to reorganize templates and examples folders. If we >> do want to do it, I think that soon would be a good time. >> To take a look at the proposal, check out: >>

Re: SIGSEGV on luatex export #2

On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote: > A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so > I guess it's a different bug: > 1. clear your ~/.lyx-trunk/cache/* > 2. start LyX, new doc > 3. type "info-insert icon whatevernonsense" > > => LyX

Re: beamer editing

Am Donnerstag, den 20.04.2017, 09:40 +0200 schrieb Edwin Leuven: > hello, > > quite some time ago i complained about editing frame content in lyx > > basic frame content is indented and has a standard environment > > a new line however removes the indent and resets the standard > environment

beamer editing

hello, quite some time ago i complained about editing frame content in lyx basic frame content is indented and has a standard environment a new line however removes the indent and resets the standard environment to frame to continue editing one has to re-ident and reset the environment,

Re: SIGSEGV on luatex export #2

A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so I guess it's a different bug: 1. clear your ~/.lyx-trunk/cache/* 2. start LyX, new doc 3. type "info-insert icon whatevernonsense" => LyX SIGNAL CAUGHT dialog with std::bad_alloc. T. On 20/04/2017 09:03,

SIGSEGV on luatex export

Hi, I'm seeing a SIGSEGV in the bug-export-latex-in.txt autotest [1]. Albeit the test doesn't fail, I'm clearly seeing on screen that LyX is showing the SIGSEGV dialog. Trying a manual repro, it doesn't seem to happen, but running it in the autotests it does happen all the times. Anyone might