Re: [PATCH] Output of en- and em-dashes

On Sat, Mar 18, 2017 at 03:06:09PM +0100, Guillaume Munch wrote: > Le 18/03/2017 à 14:59, Enrico Forestieri a écrit : > > On Wed, Mar 15, 2017 at 06:12:51PM +0100, Enrico Forestieri wrote: > > > > > > Apparently, nobody has a preference, so I am going to commit the > > > second patch, i.e., the

Re: [PATCH] Output of en- and em-dashes

On 2017-03-18, Enrico Forestieri wrote: > On Sat, Mar 18, 2017 at 03:06:09PM +0100, Guillaume Munch wrote: ... >> > I think we have to make do with the ugly zero-space inset. >> Or special/invisible unicode characters could be made visible by changing >> the character before painting. >

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #107

On Fri, 17 Mar 2017 at 21:10, Jean-Marc Lasgouttes wrote: > Le 15/03/2017 à 12:12, Kornel Benko a écrit : > > Probably some automake failure. Using old > ./src/support/tests/dummy_functions.o in the build dir. > > Removing that file, it will be rebuild with > > make

Re: Crash in File-Open

On Sat, Mar 18, 2017 at 08:26:05AM +0100, Kornel Benko wrote: > Yes, this is sufficient. > If you want to switch more often, you should create a script. > I have a symbolic link, /usr/BUILD/BuildQt, pointing to the correct QT. > And in /etc/ld.so.conf.d/qt5.conf the first line reads >

Re: [PATCH] Output of en- and em-dashes

On Wed, Mar 15, 2017 at 06:12:51PM +0100, Enrico Forestieri wrote: > > Apparently, nobody has a preference, so I am going to commit the > second patch, i.e., the one using a zero-width space character. On second thoughts, I am not sure this is the best choice. I just verified that this character

Re: [PATCH] Output of en- and em-dashes

Le 18/03/2017 à 14:59, Enrico Forestieri a écrit : On Wed, Mar 15, 2017 at 06:12:51PM +0100, Enrico Forestieri wrote: Apparently, nobody has a preference, so I am going to commit the second patch, i.e., the one using a zero-width space character. On second thoughts, I am not sure this is the

Re: Crash in File-Open

On Sat, Mar 18, 2017 at 06:09:32PM +0100, Enrico Forestieri wrote: > On Sat, Mar 18, 2017 at 12:54:44PM -0400, Scott Kostyshak wrote: > > > > What is the difference between the following two (the second removes the > > prepended "env")? > > > > env LD_LIBRARY_PATH=/path/to/mylibs prog > >

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #107

On 18 March 2017 at 16:46, Christian Ridderström wrote: > Christian, does the check start from a fresh tree? If you do 'make >> clean' and the rules have changed, it might be that some .o files remain >> at the wrong place >> > > I think most CI jobs are configured to start from a

Re: [patch] Fix color when branch name has a space

On Sat, Mar 18, 2017 at 05:49:30PM +0100, Jean-Marc Lasgouttes wrote: > Le 18/03/2017 à 17:02, Scott Kostyshak a écrit : > > On Tue, Mar 14, 2017 at 01:01:23AM -0400, Scott Kostyshak wrote: > > > > > I have a patch and it seems to work well. I want to clean it up before > > > posting. I will post

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #108

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/108/-- [...truncated 1127 lines...] CXX insets/InsetGraphicsParams.o CXX insets/InsetGraphics.o CXX insets/InsetHyperlink.o CXX

Re: [PATCH] Output of en- and em-dashes

On Sat, Mar 18, 2017 at 03:41:20PM +, Guenter Milde wrote: > On 2017-03-18, Enrico Forestieri wrote: > > On Sat, Mar 18, 2017 at 03:06:09PM +0100, Guillaume Munch wrote: > > ... > > >> > I think we have to make do with the ugly zero-space inset. > > >> Or special/invisible unicode

Re: Crash in File-Open

On Sat, Mar 18, 2017 at 11:56:25AM -0400, Scott Kostyshak wrote: > On Sat, Mar 18, 2017 at 08:26:05AM +0100, Kornel Benko wrote: > > > Yes, this is sufficient. > > If you want to switch more often, you should create a script. > > I have a symbolic link, /usr/BUILD/BuildQt, pointing to the

Re: Crash in File-Open

On Sat, Mar 18, 2017 at 12:54:44PM -0400, Scott Kostyshak wrote: > > What is the difference between the following two (the second removes the > prepended "env")? > > env LD_LIBRARY_PATH=/path/to/mylibs prog This works whatever your shell. > and > > LD_LIBRARY_PATH=/path/to/mylibs prog

Re: Crash in File-Open

On Sat, Mar 18, 2017 at 05:43:10PM +0100, Enrico Forestieri wrote: > On Sat, Mar 18, 2017 at 11:56:25AM -0400, Scott Kostyshak wrote: > > > On Sat, Mar 18, 2017 at 08:26:05AM +0100, Kornel Benko wrote: > > > > > Yes, this is sufficient. > > > If you want to switch more often, you should create a

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #109

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/109/-- [...truncated 1127 lines...] CXX insets/InsetGraphicsParams.o CXX insets/InsetGraphics.o CXX insets/InsetHyperlink.o CXX

Re: CI+Coverity (was: Re: Working on CI job that runs automated tests)

On 7 March 2017 at 11:23, Jean-Marc Lasgouttes wrote: > Hi Christian, > > The next natural step could be to use your CI stuff to update our coverity > builds: > https://scan.coverity.com/projects/4164 > > Currently the build are submitted by hand by Liviu or recently by

Re: [patch] Fix color when branch name has a space

On Tue, Mar 14, 2017 at 01:01:23AM -0400, Scott Kostyshak wrote: > I have a patch and it seems to work well. I want to clean it up before > posting. I will post it again for review because even though it seems to > work well, I wonder if there is a cleaner way of doing it. I will post > a cleaned

Re: [patch] Fix color when branch name has a space

Le 18/03/2017 à 17:02, Scott Kostyshak a écrit : On Tue, Mar 14, 2017 at 01:01:23AM -0400, Scott Kostyshak wrote: I have a patch and it seems to work well. I want to clean it up before posting. I will post it again for review because even though it seems to work well, I wonder if there is a

Re: Crash in File-Open

Am Samstag, 18. März 2017 um 00:23:10, schrieb Scott Kostyshak > On Wed, Mar 15, 2017 at 03:47:31PM +0100, Kornel Benko wrote: > > Am Samstag, 11. März 2017 um 22:29:58, schrieb Kornel Benko > > > Am Samstag, 11. März 2017 um 14:47:37, schrieb Scott Kostyshak