Re: [LyX/master] Introduce "inverted" branch insets: These are branches whose content is output when a branch is NOT activated. Fixes bug #7698.

On Sun, Aug 07, 2016 at 09:29:31PM -0400, Richard Heck wrote: > On 08/07/2016 03:24 PM, Scott Kostyshak wrote: > > On Tue, Jul 12, 2016 at 05:57:41AM +0200, Richard Heck wrote: > >> commit 5df323a0dd564f00c5ab085a3570957ad76b21d3 > >> Author: Richard Heck > >> Date: Mon Jul 11

Re: Should the author of a file format change update the file format of docs in master?

On 08/07/2016 08:00 PM, Scott Kostyshak wrote: > When making a file format change, we currently have instructions for the > author of the file format change to update the file format of the docs. > > [snip] > > Also, I wonder if updating the file format is annoying to document > maintainers

Re: [LyX/master] Introduce "inverted" branch insets: These are branches whose content is output when a branch is NOT activated. Fixes bug #7698.

On 08/07/2016 03:24 PM, Scott Kostyshak wrote: > On Tue, Jul 12, 2016 at 05:57:41AM +0200, Richard Heck wrote: >> commit 5df323a0dd564f00c5ab085a3570957ad76b21d3 >> Author: Richard Heck >> Date: Mon Jul 11 23:56:32 2016 -0400 >> >> Introduce "inverted" branch insets: These

Should the author of a file format change update the file format of docs in master?

When making a file format change, we currently have instructions for the author of the file format change to update the file format of the docs. The following excerpt is in Development.lyx in Section 2.3: Update LyX's .lyx documentation files to the new format. The developer who makes the

Re: QFile::remove: Empty or null file name

On Sun, Aug 07, 2016 at 08:42:30AM +0100, Jean-Pierre Chrétien wrote: > Le 06/08/2016 à 16:36, Scott Kostyshak a écrit : > > To reproduce, open the Embedded Objects manual and compile to PDF. I get > > the following warnings in the terminal: > > > > QFile::remove: Empty or null file name > >

Re: [LyX/master] Use call_once to ensure something is only called once

On Sun, Aug 07, 2016 at 05:37:25PM +0100, Guillaume Munch wrote: > > Then I tried the cygwin one, and it reported "thread model: win32". And > I could not manage to activate the posix threading model. I also found > that mingw itself relies on winpthreads internally whatever the version, > so

Re: [LyX/master] Introduce "inverted" branch insets: These are branches whose content is output when a branch is NOT activated. Fixes bug #7698.

On Tue, Jul 12, 2016 at 05:57:41AM +0200, Richard Heck wrote: > commit 5df323a0dd564f00c5ab085a3570957ad76b21d3 > Author: Richard Heck > Date: Mon Jul 11 23:56:32 2016 -0400 > > Introduce "inverted" branch insets: These are branches whose content > is output when a

Re: [LyX/master] Use call_once to ensure something is only called once

Le 07/08/2016 à 17:05, Enrico Forestieri a écrit : On Sun, Aug 07, 2016 at 04:18:13PM +0200, Enrico Forestieri wrote: On Sun, Aug 07, 2016 at 01:10:49PM +0100, Guillaume Munch wrote: That being said, if we want to make any use of the and headers in the future we need the posix version (in

Re: [LyX/master] Use call_once to ensure something is only called once

On Sun, Aug 07, 2016 at 04:18:13PM +0200, Enrico Forestieri wrote: > On Sun, Aug 07, 2016 at 01:10:49PM +0100, Guillaume Munch wrote: > > > > That being said, if we want to make any use of the and > > headers in the future we need the posix version (in the current state of > > MinGW). The

Re: [LyX/master] Use call_once to ensure something is only called once

On Sun, Aug 07, 2016 at 01:10:49PM +0100, Guillaume Munch wrote: > > That being said, if we want to make any use of the and > headers in the future we need the posix version (in the current state of > MinGW). The better thing to do would be to ask the cygwin people to > distribute it. I am not

Re: [LyX/master] Use call_once to ensure something is only called once

Le 07/08/2016 à 04:01, Enrico Forestieri a écrit : On Sat, Aug 06, 2016 at 03:39:19PM +0100, Guillaume Munch wrote: call_once.cpp: #include static std::once_flag flag; int main() { std::call_once(flag, [](){ return; }); return 0; } Thanks for the test case. I used it to fix this issue

Re: C++ "good practices" regarding constifying a function parameter?

On 06/08/2016 21:58, Guillaume Munch wrote: But I agree that new move functionality in C++11 is really nice and I know that I have to unlearn the good practice I learned so many years ago in order to use them efficiently. The issue with c++11 move semantics is that it is an addition of a big

Insert->Special Character->Protected Hyphen requires amsmath package

(sorry for the mistyping of the subject line in my previous post) Hello, I happened to check that splash.lyx compiled correctly in French. As I found a wrongly justified line, I tried to correct this by inserting a Insert->Special Character->Protected Hyphen, which is not the correct solution

Re: QFile::remove: Empty or null file name

Le 06/08/2016 à 16:36, Scott Kostyshak a écrit : To reproduce, open the Embedded Objects manual and compile to PDF. I get the following warnings in the terminal: QFile::remove: Empty or null file name QFile::remove: Empty or null file name QFile::remove: Empty or null file name Did you