> Le 28 mars 2014 à 00:37, Richard Heck a écrit :
>
>> On 03/27/2014 07:15 PM, Vincent van Ravesteijn wrote:
>> Hi all,
>>
>> Do we want to setup the fixedinbranch, and fixedintrunk status for tickets.
>> This means, we don't have to work with the keywords any longer. Then, you
>> will hav
Am 28.03.2014 00:15, schrieb Vincent van Ravesteijn:
And we can also have more meaningful roadmap overviews.
I implemented this locally, so it is really possible to do.
Shall we investigate further ?
+1
regards Uwe
Am 28.03.2014 00:13, schrieb Vincent van Ravesteijn:
1282 characters. Not extremely large mine was almost as large.
Poser! ;-)
Uwe
On 27/03/14 12:36, Tommaso Cucinotta wrote:
> Ok, fantastic, I must have forgotten :-)! Indeed, it seems lyxfind.cpp is
> the major caller. I'll try to
> merge the functionality of the two methods, preserving the interface for
> other callers. As a by product effect, I should be able to fix #7987,
On 03/27/2014 07:37 PM, Richard Heck wrote:
On 03/27/2014 07:15 PM, Vincent van Ravesteijn wrote:
Hi all,
Do we want to setup the fixedinbranch, and fixedintrunk status for
tickets. This means, we don't have to work with the keywords any
longer. Then, you will have the following actions:
On 03/27/2014 07:15 PM, Vincent van Ravesteijn wrote:
Hi all,
Do we want to setup the fixedinbranch, and fixedintrunk status for
tickets. This means, we don't have to work with the keywords any
longer. Then, you will have the following actions:
And we can also have more meaningful roadmap
Hi all,
Do we want to setup the fixedinbranch, and fixedintrunk status for
tickets. This means, we don't have to work with the keywords any
longer. Then, you will have the following actions:
And we can also have more meaningful roadmap overviews.
Uwe Stöhr schreef op 28-3-2014 0:11:
Am 28.03.2014 00:04, schrieb Vincent van Ravesteijn:
Hmm. you should have mentioned that to the reporters in bug #8570 ;).
I did not think that this is be the problem.
While looking at the bug again now I see that
http://www.lyx.org/trac/ticket/8570#commen
Am 28.03.2014 00:04, schrieb Vincent van Ravesteijn:
Hmm. you should have mentioned that to the reporters in bug #8570 ;).
I did not think that this is be the problem.
While looking at the bug again now I see that
http://www.lyx.org/trac/ticket/8570#comment:13
has an extremely large PATH.
How
Uwe Stöhr schreef op 28-3-2014 0:02:
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
To solve your MiKTeX recognition error, can you please send me the
content of your registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment "Path"
Well, I assur
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
To solve your MiKTeX recognition error, can you please send me the content of
your registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
"Path"
Well, I assure you that miktex is in the path
I wa
Uwe Stöhr schreef op 27-3-2014 22:20:
To solve your MiKTeX recognition error, can you please send me the
content of your registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment "Path"
Well, I assure you that miktex is in the path, but I've debugged t
Am 27.03.2014 16:57, schrieb Vincent van Ravesteijn:
That's weird.. 6 days ago you closed bug #8570 "Lyx Full Bundle 2.0.5.1
can't detect MikTeX installation", where at least 5 users complained that
the installer couldn't find MikTeX. You closed it with resolution
"worksforme".
Because I never
Am 27.03.2014 09:11, schrieb Vincent van Ravesteijn:
One path with miktex, and if I start a command prompt and type latex, it
starts.
That is good.
p.s. do you also have TeXLive installed?
No.
Also good.
I have problems to get the nsi script to compile, so it makes debugging
somewhat h
Hi Guys,
thanks for this - I've tried making the changes and then compiling for
windows, but I failed miserably (I am no techie), I could not get the
software to compile. Some folks tried
to help, but I guess it was too complicated to do this remotely.
I will be waiting with hope and patience
On Wed, Mar 26, 2014 at 11:23 PM, Uwe Stöhr wrote:
> Am 26.03.2014 22:21, schrieb Vincent van Ravesteijn:
>
> Do you have MiKTeX in your PATH?
>>>
>>
>> Yes, and it is in the "Path" entry.
>>
>> Can you install LyX 2.0.7? This installer uses the same MiKTeX search
>>> routine as the installer f
On 03/27/2014 09:04 AM, Jean-Marc Lasgouttes wrote:
Hello,
This small patch avoids installing the misnamed and useless files
lyxNONE.desktop, lyxNONE.svg when using windows and macosx packaging
with autotools.
I intend to commit it to 2.2-satging. It could maybe go to 2.1.x too.
Feel free
2014-03-27 14:27 GMT+01:00 Vincent van Ravesteijn :
> Note that this is not a string change in l7n sense (see discussion in
>> #9045)
>>
> #9054
>
> Too late I guess...
>
Yeah, I suppose. It is not possible to "amend" commit messages, or is it?
Jürgen
>
> Vincent
>
On Thu, Mar 27, 2014 at 2:25 PM, Juergen Spitzmueller wrote:
> commit 200f1ca37bf79ffc82cd402a9fd23237e621917c
> Author: Juergen Spitzmueller
> Date: Thu Mar 27 14:25:30 2014 +0100
>
> Re-enable translation of pdfpages help text (works around #9045)
>
#9054
>
> Note that this is not
Le 24/03/14 16:31, Richard Heck a écrit :
On 03/24/2014 11:26 AM, Jean-Marc Lasgouttes wrote:
Richard, I think we want that for 2.1.x eventually. In what branch do
you want me to commit it?
If it's intended for 2.1.x, then it should go into 2.1.1-staging. I think.
Done.
JMarc
Hello,
This small patch avoids installing the misnamed and useless files
lyxNONE.desktop, lyxNONE.svg when using windows and macosx packaging
with autotools.
I intend to commit it to 2.2-satging. It could maybe go to 2.1.x too.
JMarc
>From 26623fbe65e53c40aea3606bc450818526a6305d Mon Sep 17
On 27/03/14 10:53, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
>> On Thu, Mar 27, 2014 at 11:41 AM, Pavel Sanda wrote:
>>
>>> Vincent van Ravesteijn wrote:
Tommasso, I don't want to spoil the fun, but I think you introduced
>>>
>>> :))
>>>
>>
>> ... and Pavel committed it, so you migh
Vincent van Ravesteijn wrote:
> On Thu, Mar 27, 2014 at 11:41 AM, Pavel Sanda wrote:
>
> > Vincent van Ravesteijn wrote:
> > > Tommasso, I don't want to spoil the fun, but I think you introduced
> >
> > :))
> >
>
> ... and Pavel committed it, so you might share some fun together.
yes, i can re
On Thu, Mar 27, 2014 at 11:41 AM, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > Tommasso, I don't want to spoil the fun, but I think you introduced
>
> :))
>
... and Pavel committed it, so you might share some fun together.
Vincent
Vincent van Ravesteijn wrote:
> Tommasso, I don't want to spoil the fun, but I think you introduced
:))
On Thu, Mar 27, 2014 at 10:29 AM, Jean-Marc Lasgouttes
wrote:
> Le 27/03/14 09:17, Tommaso Cucinotta a écrit :
>
> Anyone remembers what major difference among these two sets of methods,
>> from Paragraph and Inset?
>>
>> Paragraph::stringify() and asString() look like almost identical, with
>> t
On Thu, Mar 27, 2014 at 10:58 AM, Benjamin Piwowarski wrote:
> Just my two cents here - I don't want to reheat the debate - but I find it
> confusing just for one reason, terminology : the 2.2-staging branch is, at
> least for me, the develop branch (where all new commits should happen), and
> the
Am Mittwoch, 26. März 2014 um 21:55:59, schrieb Vincent van Ravesteijn
> Kornel Benko schreef op 26-3-2014 21:28:
> >
> > Am Mittwoch, 26. März 2014 um 21:08:42, schrieb Vincent van Ravesteijn
> >
> >
> > > Kornel Benko schreef op 26-3-2014 20:59:
> >
> > >
> >
> > > > diff --git a/CMakeLists.t
Just my two cents here - I don’t want to reheat the debate - but I find it
confusing just for one reason, terminology : the 2.2-staging branch is, at
least for me, the develop branch (where all new commits should happen), and
then the different branches (master = 2.1, 2.1.1-staging) are managed
Le 27/03/14 09:17, Tommaso Cucinotta a écrit :
Anyone remembers what major difference among these two sets of methods, from
Paragraph and Inset?
Paragraph::stringify() and asString() look like almost identical, with the
difference that
the former goes for Inset::plaintext(), and it doesn't det
On Thu, Mar 27, 2014 at 4:58 AM, Paola Manzini
wrote:
> Hi guys,
>
> first of all thanks for your efforts, it does look great! However I am still
> frustrated in using it on my device with a high resolution screen (Windows),
> as the icons are too small (the problem that I highlighted here:
> http
Am 27.03.2014 um 09:13 schrieb Pavel Sanda :
> Stephan Witt wrote:
>> No, a new bug would be better. Applying the patch improves the situation
>> only a little bit. There is more work to be done with these locking issues.
>
> Will you file the bug?
Yes, I'll do it.
Stephan
Anyone remembers what major difference among these two sets of methods, from
Paragraph and Inset?
Paragraph::stringify() and asString() look like almost identical, with the
difference that
the former goes for Inset::plaintext(), and it doesn't detect deleted text, the
latter uses
Inset::toStrin
Stephan Witt wrote:
> No, a new bug would be better. Applying the patch improves the situation
> only a little bit. There is more work to be done with these locking issues.
Will you file the bug?
P
On Wed, Mar 26, 2014 at 11:23 PM, Uwe Stöhr wrote:
>
>
> I'm now too busy doing other LyX stuff to be able do debug the installer.
>> Maybe later.
>>
>
> Just look in your PATH what the path containing "miktex" is. Maybe there
> are even 2 paths containing "miktex". Check if every path containi
On Thu, Mar 27, 2014 at 4:23 AM, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
> >> That was my first idea. But we no more have filename in our hands so
> most
> >> we can output
> >> is something like "can't unlock file". You prefer this?
> >
> > Well, at least we will know that this triggers
Am 27.03.2014 um 08:46 schrieb Pavel Sanda :
> Georg Baum wrote:
>> Stephan Witt wrote:
>>
>>> Am 24.01.2014 um 19:05 schrieb Pavel Sanda :
>>>
Stephan Witt wrote:
> I've played a little bit with SVN and LyX and there are IMO some issues
> when locking is enabled.
>
> 1. Wh
Georg Baum wrote:
> Stephan Witt wrote:
>
> > Am 24.01.2014 um 19:05 schrieb Pavel Sanda :
> >
> >> Stephan Witt wrote:
> >>> I've played a little bit with SVN and LyX and there are IMO some issues
> >>> when locking is enabled.
> >>>
> >>> 1. When a file isn't locked the file is not writable. O
38 matches
Mail list logo
