SSL Certificates

Hi, all, I've renewed our SSL certificates and thought I'd at least better explain how it's done. I've set up a very primitive ACME client for doing this, which is found at /home/rgheck/letsencrypt.sh/. The account key can be found there, too. To renew the certificates, you just have to do:

Re: Problem with key shortcuts on 2.2 with qt-5.5

On Mon, Mar 07, 2016 at 01:40:45PM +, José Matos wrote: > On Saturday, March 05, 2016 01:05:30 AM Scott Kostyshak wrote: > > I don't understand, are read-review and 2016 file names? Or they are > > just text in a buffer? > > > > Scott > > read-review and 2016 are file names. My problem is

Re: xcolor conflict with beamer article?

On Sat, Mar 05, 2016 at 01:42:15PM -0500, Scott Kostyshak wrote: > When using beamer article I get an error if I try to add the color > purple to some text: > > \fi > > The package xcolor has already been loaded with options: > [] > There has now been an attempt to load it with options

Re: [patch] fix a problem with autorepeat cursor keys

Dear Andreas Thank you very much for coming up already with a solution to your problem. I would not be surprised that this portion of code is buggy, because querying hasPendingEvents() inside a thread is already a weird way to decide to drop an event. Your patch looks simple but would need to

Re: [patch] fix a problem with autorepeat cursor keys

Uwe Stöhr writes: > Am 07.03.2016 um 02:13 schrieb Andreas Amann: > > > The attached patch against the current master branch fixes the problem >> for me. It first processes all events which are not caused by user >> input, and only if this does not clear the event queue

Re: LyX 2.2.0

On Mon, Mar 07, 2016 at 04:51:38PM -0600, Brian Williamson wrote: > Hello, > > I am curious about potentially testing LyX 2.2.0. If this is possible, please > let me know. Thank you. > > Kind regards, > Brian Williamson Hi Brian, we have installers for Mac and Windows here:

Re: [patch] fix a problem with autorepeat cursor keys

Am 07.03.2016 um 02:13 schrieb Andreas Amann: > The attached patch against the current master branch fixes the problem for me. It first processes all events which are not caused by user input, and only if this does not clear the event queue proceeds to drop the current event. Many thanks

Re: int64 compiler warnings

Am 07.03.2016 um 22:27 schrieb Georg Baum: > - The wanted type is always 64bit => use boost::int64_t for signed values and boost::uint64_t for unsigned values (MSVC does not have std::int64_t or ::it64_t, at least not in the 2010 version) Many thanks for having a look. MSVC 2015 has this:

LyX 2.2.0

Hello, I am curious about potentially testing LyX 2.2.0. If this is possible, please let me know. Thank you. Kind regards, Brian Williamson

Re: Features request glossaries package support

Elad Denenberg wrote: > Glossaries is a very helpful package that can be used with or instead of > nomencl. The greatest advantages it holds over nomencl are: > 1. When using acronyms it allows for the expanded long version of the > acronym in first use, then the short version in all other places.

Re: int64 compiler warnings

Jean-Marc Lasgouttes wrote: > Le 07/03/2016 13:21, Alex Vergara Gil a écrit : >> Best way for this is to use native int as integer variables and you >> forget about it, this works even on windows, so instead of int use >> long and thats it: http://en.cppreference.com/w/cpp/language/types > > In

Re: Cursor position regression (?) in master

On Mon, Mar 07, 2016 at 12:08:04PM +0100, Jean-Marc Lasgouttes wrote: > Le 05/03/2016 17:54, Scott Kostyshak a écrit : > >I can reproduce the following on master but not in 2.1.x: > > > >1. open mwe.21.lyx > >2. place the cursor just to the right of the character "4" > >3. press ctrl + return > >

Re: Is "make distcheck" failure a blocker?

On Mon, Mar 07, 2016 at 11:36:08AM +0100, Jean-Marc Lasgouttes wrote: > Le 07/03/2016 06:14, Scott Kostyshak a écrit : > >But setting --enable-monolithic-build to "no" leads to all of the > >commands passing. > > I would just advise to avoid this option for distcheck, then :) We do not > have to

Re: Problem with key shortcuts on 2.2 with qt-5.5

On Saturday, March 05, 2016 01:05:30 AM Scott Kostyshak wrote: > I don't understand, are read-review and 2016 file names? Or they are > just text in a buffer? > > Scott read-review and 2016 are file names. My problem is not that we try to assign a key shortcut to access those files but that we

Re: int64 compiler warnings

Le 07/03/2016 13:59, Jean-Marc Lasgouttes a écrit : Le 07/03/2016 13:21, Alex Vergara Gil a écrit : Best way for this is to use native int as integer variables and you forget about it, this works even on windows, so instead of int use long and thats it:

Re: int64 compiler warnings

Le 07/03/2016 13:21, Alex Vergara Gil a écrit : Best way for this is to use native int as integer variables and you forget about it, this works even on windows, so instead of int use long and thats it: http://en.cppreference.com/w/cpp/language/types In this case one would want a 64 bit type,

Re: int64 compiler warnings

Best way for this is to use native int as integer variables and you forget about it, this works even on windows, so instead of int use long and thats it: http://en.cppreference.com/w/cpp/language/types 2016-03-07 11:58 GMT+01:00, Jean-Marc Lasgouttes : > Le 07/03/2016 04:14,

Re: Cursor position regression (?) in master

Le 05/03/2016 17:54, Scott Kostyshak a écrit : I can reproduce the following on master but not in 2.1.x: 1. open mwe.21.lyx 2. place the cursor just to the right of the character "4" 3. press ctrl + return On master, the cursor does not go to the position where the next letter will be drawn.

Re: int64 compiler warnings

Le 07/03/2016 04:14, Uwe Stöhr a écrit : Although it is not pressing, I tried to compile LyX as 64bit application and this works, except of one error I just reported. There are of course some compiler warnings. Fixing them is of course also not pressing but maybe it is worth it to do it now for

Re: Is "make distcheck" failure a blocker?

Le 07/03/2016 06:14, Scott Kostyshak a écrit : But setting --enable-monolithic-build to "no" leads to all of the commands passing. I would just advise to avoid this option for distcheck, then :) We do not have to test all possibilities here (the monolithic option is used for preparing the