On Fri, Oct 14, 2016 at 07:16:36PM +0200, Jean-Marc Lasgouttes wrote:
> Le 14/10/2016 à 17:51, Scott Kostyshak a écrit :
> > Any thoughts?
>
> I would propose instead to use the helpers getArg and getLongArg in
> FuncRequest. Two possibilities:
>
> lyx_name = cmd.getArg(0);
> x11_name =
On 2016-10-14, Scott Kostyshak wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> On Fri, Oct 14, 2016 at 03:36:11PM +, Guenter Milde wrote:
>> For the end-user the difference is:
>> * with "no", there is a safeguard against relying on additional packages
>> without real
Am 13.10.2016 um 19:04 schrieb Richard Heck:
On 10/12/2016 07:33 PM, Uwe Stöhr wrote:
are my final ones ready to be put on ftp.lyx.org.
Thanks, I've got them and will plan to do the release tomorrow,
probably, or Saturday.
Hi Richard,
Daniel gave me the feedback that my installer
Am 14.10.2016 um 08:30 schrieb racoon:
Could you please give it a try and report if this fixes
http://www.lyx.org/trac/ticket/10017
Awesome. Yes, now I can actually open menus with the primary mouse
button and open more than one sub menu.
Many thanks for testing. So this new installer
Am 14.10.2016 um 17:36 schrieb Guenter Milde:
For the documentation people, the difference is:...
Hi Scott and Günter,
convinced, so fine with me to change everything to automatic. Please
commit directly if the tests were passed to branch (when it is open
again) and master (please keep
On 14.10.2016 17:14, racoon wrote:
On 13.10.2016 10:46, Guillaume Munch wrote:
Le 12/10/2016 à 20:02, racoon a écrit :
On 10.10.2016 17:49, Richard Heck wrote:
Here:
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.2/
Please prepare binaries.
I am on 2.2.2 now. There is something strange
On 13.10.2016 22:28, Kornel Benko wrote:
Am Donnerstag, 13. Oktober 2016 um 15:22:30, schrieb Richard Heck
On 10/13/2016 03:17 PM, racoon wrote:
On 13.10.2016 21:13, Richard Heck wrote:
On 10/13/2016 02:31 PM, racoon wrote:
Hi,
I think I could solve
Hi,
How do I update my local copy to the current master?
In git gui I tried
Fetch from > origin
But this seems not to work. I can now type any git command line commands
using
Repository > Git Bash
So I am even happy about command line commands on how to update to the
current master.
These are really low hanging fruit:
Image files are suboptimally compressed.
Using both
(just examples, there may be better ways or programs)
imgopt
https://github.com/kormoc/imgopt
for raster images and
SVG-Cleaner
https://sourceforge.net/projects/svgcleaner/
for the vector images
I get the
On Fri, Oct 14, 2016 at 02:10:18PM +0200, racoon wrote:
> Thanks. Unfortunately, the final step "git pull" gives me this:
>
> There is no tracking information for the current branch.
> Please specify which branch you want to merge with.
> See git-pull(1) for details.
>
> git pull
>
> If
On Fri, Oct 14, 2016 at 03:22:09PM +0200, Jean-Marc Lasgouttes wrote:
> Le 07/10/2016 à 03:48, Scott Kostyshak a écrit :
> > > I don't know much about layout nesting, but my first reaction is that I
> > > agree with you regarding the expected behavior.
> >
> > Did we figure out what the correct
On Fri, Oct 14, 2016 at 03:20:07AM +0200, Uwe Stöhr wrote:
> Am 14.10.2016 um 00:43 schrieb Scott Kostyshak:
>
> > Does the attached .lyx file work for you?
>
> This fixes one of the 3 bugs we are facing here. But how did you manage to
> get rid of \beginL?
I deleted the number "4", then
On 10/14/2016 10:01 AM, racoon wrote:
> On 14.10.2016 15:50, Scott Kostyshak wrote:
>> On Fri, Oct 14, 2016 at 02:10:18PM +0200, racoon wrote:
>>> Thanks. Unfortunately, the final step "git pull" gives me this:
>>>
>>> There is no tracking information for the current branch.
>>> Please specify
Any thoughts?
Scott
From dfd265bbcb4c00d06ddd064fa64da5000ebc5cb2 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak
Date: Fri, 14 Oct 2016 10:41:11 -0400
Subject: [PATCH] Fix color when branch name has a space
The argument to set-color is " ", where in the
case of branches is
On Fri, Oct 14, 2016 at 01:21:17AM +0200, Uwe Stöhr wrote:
> Am 07.10.2016 um 19:01 schrieb Scott Kostyshak:
>
> OK, if all test are passed, we don't risk anything. the question is however,
> if this is really necessary. Setting a package to no or to automatic does
> not change anything since if
On 13.10.2016 10:46, Guillaume Munch wrote:
Le 12/10/2016 à 20:02, racoon a écrit :
On 10.10.2016 17:49, Richard Heck wrote:
Here:
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.2/
Please prepare binaries.
I am on 2.2.2 now. There is something strange happening when I *replace*
stuff from
On 2016-10-13, Uwe Stöhr wrote:
> Am 07.10.2016 um 19:01 schrieb Scott Kostyshak:
Dear Uwe,
>> My proposal is to change everything in all .lyx files to "Automatic".
>> Then run the ctests to see which exports start failing and revert the
>> changes to those corresponding documents.
> OK, if all
On Fri, Oct 14, 2016 at 03:36:11PM +, Guenter Milde wrote:
> For the end-user the difference is:
>
> * with "no", there is a safeguard against relying on additional packages
> without real need -> less dependencies when compiling the docs.
Wouldn't this be a LyX bug if we rely on an
Le 14/10/2016 à 15:57, Scott Kostyshak a écrit :
On Fri, Oct 14, 2016 at 03:15:29PM +0200, Jean-Marc Lasgouttes wrote:
Am I right that it should be "register" instead?
Yes.
Amusingly, `register' is a reserved word in C++ (even though it is
deprecated).
Any idea of what I could use
On Fri, Oct 14, 2016 at 03:15:29PM +0200, Jean-Marc Lasgouttes wrote:
> Am I right that it should be "register" instead?
Yes.
Note here and in the future though that I only have knowledge of English
(USA).
Scott
signature.asc
Description: PGP signature
On Fri, Oct 14, 2016 at 04:37:21PM +0200, Jean-Marc Lasgouttes wrote:
> Le 14/10/2016 à 15:57, Scott Kostyshak a écrit :
> > On Fri, Oct 14, 2016 at 03:15:29PM +0200, Jean-Marc Lasgouttes wrote:
> > > Am I right that it should be "register" instead?
> >
> > Yes.
>
> Amusingly, `register' is a
On 14.10.2016 15:50, Scott Kostyshak wrote:
On Fri, Oct 14, 2016 at 02:10:18PM +0200, racoon wrote:
Thanks. Unfortunately, the final step "git pull" gives me this:
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for
Le 14/10/2016 à 15:57, Scott Kostyshak a écrit :
On Fri, Oct 14, 2016 at 03:15:29PM +0200, Jean-Marc Lasgouttes wrote:
Am I right that it should be "register" instead?
Yes.
Note here and in the future though that I only have knowledge of English
(USA).
Google tends to think that this is
On 10/14/2016 12:48 PM, Scott Kostyshak wrote:
> On Mon, Oct 10, 2016 at 04:24:45PM +0200, Richard Heck wrote:
>> commit 3fe8c04274b0cbc16577965207b4d98aec58d0cd
>> Author: Richard Heck
>> Date: Mon Oct 10 10:24:08 2016 -0400
>>
>> Fix monolithic build.
> Is this needed for
On 15.10.2016 00:12, racoon wrote:
On 14.10.2016 17:14, racoon wrote:
On 13.10.2016 10:46, Guillaume Munch wrote:
Le 12/10/2016 à 20:02, racoon a écrit :
On 10.10.2016 17:49, Richard Heck wrote:
Here:
ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.2/
Please prepare binaries.
I am on
On 14.10.2016 00:43, Uwe Stöhr wrote:
Am 11.10.2016 um 00:50 schrieb racoon:
Which Qt version will be used for LyX 2.2.2? Qt 5.6.2 is around the
corner (possibly next week). Any chance on a binary with that version? I
am so annoyed by the menus (http://www.lyx.org/trac/ticket/10017). And
the
Le 14/10/2016 à 17:51, Scott Kostyshak a écrit :
Any thoughts?
I would propose instead to use the helpers getArg and getLongArg in
FuncRequest. Two possibilities:
lyx_name = cmd.getArg(0);
x11_name = cmd.getLongArg(1);
This will do what you want, at the price of a badly defined syntax: it
On Mon, Oct 10, 2016 at 04:24:45PM +0200, Richard Heck wrote:
> commit 3fe8c04274b0cbc16577965207b4d98aec58d0cd
> Author: Richard Heck
> Date: Mon Oct 10 10:24:08 2016 -0400
>
> Fix monolithic build.
Is this needed for master also?
Scott
signature.asc
Description: PGP
I'm not part of the development team; however, my thoughts:
Command-line wise from the LyX directory, check your settings to make sure
they are to the right place with with
git remote -v
Once satisfied (and with any of your changes stashed or committed), try
git checkout master
git fetch
git
Thanks. Unfortunately, the final step "git pull" gives me this:
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull
If you wish to set tracking information for this branch you can do so with:
Am I right that it should be "register" instead?
JMarc
Le 07/10/2016 à 03:48, Scott Kostyshak a écrit :
I don't know much about layout nesting, but my first reaction is that I
agree with you regarding the expected behavior.
Did we figure out what the correct behavior for this is?
Please try that and tell me whether it works for you.
JMarc
32 matches
Mail list logo