Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 5:19 AM, Georg Baum b...@lyx.org wrote: commit 3e9e6e344ace9160f93fd882bf2243d24a069fa5 Author: Georg Baum b...@lyx.org Date: Sun Mar 1 11:16:57 2015 +0100 Replace automatic logofication with insets Previously, LyX did replace some words with typeset logos,

Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 4:19 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Scott Kostyshak wrote: ctests give a lot of errors after this commit. For example, open doc/UserGuide.lyx and try to compile. I get an undefined control sequence error and \SpecialCharNoPassThru \LaTeX no file

Re: [LyX/master] Replace automatic logofication with insets

On 03/01/2015 04:44 PM, Scott Kostyshak wrote: On Sun, Mar 1, 2015 at 5:19 AM, Georg Baum b...@lyx.org wrote: commit 3e9e6e344ace9160f93fd882bf2243d24a069fa5 Author: Georg Baum b...@lyx.org Date: Sun Mar 1 11:16:57 2015 +0100 Replace automatic logofication with insets Previously,

Re: Retina support on OS X (sponsoring?)

Note that part of the problem is that for retina support we would require Qt 5. There are a few pending issues with LyX and Qt 5, as noted here: http://www.lyx.org/trac/ticket/9215 And we keep finding more (two weeks ago, Kornel found a bug due to Qt 5: http://www.lyx.org/trac/ticket/9412). I

Re: [LyX/master] Replace automatic logofication with insets

Scott Kostyshak wrote: ctests give a lot of errors after this commit. For example, open doc/UserGuide.lyx and try to compile. I get an undefined control sequence error and \SpecialCharNoPassThru \LaTeX no file found. Thanks, this is fixed now. One day I have to study the ctest machinery, so

Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 8:41 PM, Richard Heck rgh...@lyx.org wrote: On 03/01/2015 04:44 PM, Scott Kostyshak wrote: I don't have anything in mind, I'm just curious if it is expected since I don't know off-hand of other LyX insets for which right-click is disabled. It'd probably be worth

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic landronim...@gmail.com wrote: On Sun, Mar 1, 2015 at 12:17 AM, Raymond Rogers raymond.roger...@gmail.com wrote: Hi, Thanks for the attention! I am not surprised you can't reproduce it; after all I haven't been able to either. That's the reason I

Re: [LyX/master] Fix plaintext output of dashes (bug #3647)

Scott Kostyshak wrote: I think lyx2lyx converts some cases it should not. To reproduce an error, do the following: 1. In a LyX with a previous format (any commit before this one) start a new document and go to Insert Label and put a--b and press OK. 2. Save the document. 3. Open the

Re: [patches] Improve error reporting and log parsing

Scott Kostyshak wrote: On Fri, Feb 27, 2015 at 4:27 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Enrico Forestieri wrote: My vote is for a warning and an output produced in any case. If latex produces an output, that output has to be shown, IMO. Having the possibility of looking at

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 9:00 AM, Scott Kostyshak skost...@lyx.org wrote: On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic landronim...@gmail.com wrote: On Sun, Mar 1, 2015 at 12:17 AM, Raymond Rogers raymond.roger...@gmail.com wrote: Hi, Thanks for the attention! I am not surprised you can't

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 3:11 AM, Liviu Andronic landronim...@gmail.com wrote: My point was, though, that lyx2.2 should *only* be used in contained, non-production environments mostly for testing purposes. Put differently, don't trust your critical work files to bleeding-edge code... unless you

Re: #9436: Lyx 2.2 Left/Right arrow keys

On 03/01/2015 03:11 AM, Liviu Andronic wrote: On Sun, Mar 1, 2015 at 9:00 AM, Scott Kostyshak skost...@lyx.org wrote: On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic landronim...@gmail.com wrote: On Sun, Mar 1, 2015 at 12:17 AM, Raymond Rogers raymond.roger...@gmail.com wrote: Hi, Thanks for

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 3:05 PM, Raymond Rogers raymond.roger...@gmail.com wrote: On 03/01/2015 03:11 AM, Liviu Andronic wrote: On Sun, Mar 1, 2015 at 9:00 AM, Scott Kostyshak skost...@lyx.org wrote: On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic landronim...@gmail.com wrote: On Sun, Mar

Re: [LyX/master] Replace automatic logofication with insets

On 03/01/2015 09:00 PM, Scott Kostyshak wrote: On Sun, Mar 1, 2015 at 8:41 PM, Richard Heck rgh...@lyx.org wrote: On 03/01/2015 04:44 PM, Scott Kostyshak wrote: I don't have anything in mind, I'm just curious if it is expected since I don't know off-hand of other LyX insets for which

Re: Patch for automake 1.15

On 03/01/2015 01:48 PM, Ian Wilder wrote: On compiling master on OS X 10.10 with current macports, autogen.sh balks at automake 1.15. I updated autogen.sh to accept 1.15 and it seems to work, but I’m no expert. Here’s the patch if it’s useful. Yes, thanks. We always have to update this

Re: [LyX/master] Fix plaintext output of dashes (bug #3647)

On Sun, Mar 1, 2015 at 4:57 AM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Scott Kostyshak wrote: I think lyx2lyx converts some cases it should not. To reproduce an error, do the following: 1. In a LyX with a previous format (any commit before this one) start a new document and go to

Patch for automake 1.15

On compiling master on OS X 10.10 with current macports, autogen.sh balks at automake 1.15. I updated autogen.sh to accept 1.15 and it seems to work, but I’m no expert.Here’s the patch if it’s useful. -- ian bump_automake_version.diff Description: Binary data

Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 5:19 AM, Georg Baum b...@lyx.org wrote: commit 3e9e6e344ace9160f93fd882bf2243d24a069fa5 Author: Georg Baum b...@lyx.org Date: Sun Mar 1 11:16:57 2015 +0100 Replace automatic logofication with insets Previously, LyX did replace some words with typeset logos,

Re: [patches] Improve error reporting and log parsing

On Sun, Mar 1, 2015 at 5:08 AM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Scott Kostyshak wrote: On Fri, Feb 27, 2015 at 4:27 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Enrico Forestieri wrote: My vote is for a warning and an output produced in any case. If latex produces

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic wrote: > On Sun, Mar 1, 2015 at 12:17 AM, Raymond Rogers > wrote: >> Hi, >> Thanks for the attention! I am not surprised you can't reproduce it; after >> all I haven't been able to either. That's

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 9:00 AM, Scott Kostyshak wrote: > On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic wrote: >> On Sun, Mar 1, 2015 at 12:17 AM, Raymond Rogers >> wrote: >>> Hi, >>> Thanks for the attention! I am not

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 3:11 AM, Liviu Andronic wrote: > My point was, though, that lyx2.2 should *only* be used in contained, > non-production environments mostly for testing purposes. Put > differently, don't trust your critical work files to bleeding-edge > code...

Re: [LyX/master] Fix plaintext output of dashes (bug #3647)

Scott Kostyshak wrote: > I think lyx2lyx converts some cases it should not. To reproduce an > error, do the following: > > 1. In a LyX with a previous format (any commit before this one) start > a new document and go to Insert > Label and put "a--b" and press OK. > 2. Save the document. > 3.

Re: [patches] Improve error reporting and log parsing

Scott Kostyshak wrote: > On Fri, Feb 27, 2015 at 4:27 PM, Georg Baum > wrote: >> Enrico Forestieri wrote: >> >>> My vote is for a warning and an output produced in any case. >>> If latex produces an output, that output has to be shown, IMO. >>> Having the

Re: #9436: Lyx 2.2 Left/Right arrow keys

On 03/01/2015 03:11 AM, Liviu Andronic wrote: On Sun, Mar 1, 2015 at 9:00 AM, Scott Kostyshak wrote: On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic wrote: On Sun, Mar 1, 2015 at 12:17 AM, Raymond Rogers wrote: Hi,

Re: #9436: Lyx 2.2 Left/Right arrow keys

On Sun, Mar 1, 2015 at 3:05 PM, Raymond Rogers wrote: > > On 03/01/2015 03:11 AM, Liviu Andronic wrote: >> >> On Sun, Mar 1, 2015 at 9:00 AM, Scott Kostyshak wrote: >>> >>> On Sun, Mar 1, 2015 at 2:14 AM, Liviu Andronic >>>

Re: [LyX/master] Fix plaintext output of dashes (bug #3647)

On Sun, Mar 1, 2015 at 4:57 AM, Georg Baum wrote: > Scott Kostyshak wrote: > >> I think lyx2lyx converts some cases it should not. To reproduce an >> error, do the following: >> >> 1. In a LyX with a previous format (any commit before this one) start >> a new

Patch for automake 1.15

On compiling master on OS X 10.10 with current macports, autogen.sh balks at automake 1.15. I updated  autogen.sh to accept 1.15 and it seems to work, but I’m no expert.Here’s the patch if it’s useful. -- ian bump_automake_version.diff Description: Binary data

Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 5:19 AM, Georg Baum wrote: > commit 3e9e6e344ace9160f93fd882bf2243d24a069fa5 > Author: Georg Baum > Date: Sun Mar 1 11:16:57 2015 +0100 > > Replace automatic logofication with insets > > Previously, LyX did replace some words with

Re: [patches] Improve error reporting and log parsing

On Sun, Mar 1, 2015 at 5:08 AM, Georg Baum wrote: > Scott Kostyshak wrote: > >> On Fri, Feb 27, 2015 at 4:27 PM, Georg Baum >> wrote: >>> Enrico Forestieri wrote: >>> My vote is for a warning and an output produced in any case.

Re: [LyX/master] Replace automatic logofication with insets

Scott Kostyshak wrote: > ctests give a lot of errors after this commit. For example, open > doc/UserGuide.lyx and try to compile. I get an undefined control > sequence error and "\SpecialCharNoPassThru \LaTeX no file found". Thanks, this is fixed now. One day I have to study the ctest machinery,

Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 4:19 PM, Georg Baum wrote: > Scott Kostyshak wrote: > >> ctests give a lot of errors after this commit. For example, open >> doc/UserGuide.lyx and try to compile. I get an undefined control >> sequence error and "\SpecialCharNoPassThru \LaTeX

Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 5:19 AM, Georg Baum wrote: > commit 3e9e6e344ace9160f93fd882bf2243d24a069fa5 > Author: Georg Baum > Date: Sun Mar 1 11:16:57 2015 +0100 > > Replace automatic logofication with insets > > Previously, LyX did replace some words with

Re: Retina support on OS X (sponsoring?)

Note that part of the problem is that for retina support we would require Qt 5. There are a few pending issues with LyX and Qt 5, as noted here: http://www.lyx.org/trac/ticket/9215 And we keep finding more (two weeks ago, Kornel found a bug due to Qt 5: http://www.lyx.org/trac/ticket/9412). I

Re: [LyX/master] Replace automatic logofication with insets

On 03/01/2015 04:44 PM, Scott Kostyshak wrote: On Sun, Mar 1, 2015 at 5:19 AM, Georg Baum wrote: commit 3e9e6e344ace9160f93fd882bf2243d24a069fa5 Author: Georg Baum Date: Sun Mar 1 11:16:57 2015 +0100 Replace automatic logofication with insets

Re: [LyX/master] Replace automatic logofication with insets

On Sun, Mar 1, 2015 at 8:41 PM, Richard Heck wrote: > On 03/01/2015 04:44 PM, Scott Kostyshak wrote: >> I don't have >> anything in mind, I'm just curious if it is expected since I don't >> know off-hand of other LyX insets for which right-click is disabled. > > > It'd probably

Re: [LyX/master] Replace automatic logofication with insets

On 03/01/2015 09:00 PM, Scott Kostyshak wrote: On Sun, Mar 1, 2015 at 8:41 PM, Richard Heck wrote: On 03/01/2015 04:44 PM, Scott Kostyshak wrote: I don't have anything in mind, I'm just curious if it is expected since I don't know off-hand of other LyX insets for which

Re: Patch for automake 1.15

On 03/01/2015 01:48 PM, Ian Wilder wrote: On compiling master on OS X 10.10 with current macports, autogen.sh balks at automake 1.15. I updated autogen.sh to accept 1.15 and it seems to work, but I’m no expert. Here’s the patch if it’s useful. Yes, thanks. We always have to update this