On Wed, May 23, 2012 at 8:52 PM, Richard Heck wrote:
> I agree with you generally here. The conversion, like for export, should be
> done in a temporary directory, if only because the importer could, in
> principle, create all kinds of garbage in the original directory. Then the
One thing is that
Currently I'm really short on time.
I'd vote for keeping the "traditional" behavior and add the optional argument
"set" for internal API use.
This has to be used by the context menu code.
Stephan
Am 23.05.2012 um 20:59 schrieb Ronen Abravanel:
> So, which one of the suggestions should I implem
So, which one of the suggestions should I implement?
On Mon, May 7, 2012 at 1:39 PM, Ronen Abravanel wrote:
> If there are only few such commands, the 1st options seems best.
> If there are many, the last..
>
> Ronen
>
>
> On Wed, May 2, 2012 at 11:58 AM, Jean-Marc Lasgouttes
> wrote:
>
>> Le 2
On 05/22/2012 02:45 AM, Scott Kostyshak wrote:
I've only tried this for importing .tex and .csv files but whenever I
import them LyX automatically saves the resulting lyx file. In some
cases, this is exactly what I want to do but I was surprised because
in my experience usually an import functi
On 05/23/2012 03:21 AM, Scott Kostyshak wrote:
LyX hangs if a converter fails. I can reproduce this in current trunk
by opening a new document and putting \foo in an ERT box and trying to
view or export to pdflatex.
git bisect led me here:
288c1e0faad85d4b0f17e366cb5c44473a133957
Can't repro
On 05/23/2012 05:19 AM, Enrico Forestieri wrote:
On Wed, May 23, 2012 at 08:13:20AM +0200, Vincent van Ravesteijn wrote:
Op 23-5-2012 2:28, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
commit 0a33374c0d8125e27666fe513506fb6069df453c
Author: Vincent van Ravesteijn
Date: Wed May 23 01:31
On Wed, May 23, 2012 at 08:13:20AM +0200, Vincent van Ravesteijn wrote:
> Op 23-5-2012 2:28, Pavel Sanda schreef:
> >Vincent van Ravesteijn wrote:
> >>commit 0a33374c0d8125e27666fe513506fb6069df453c
> >>Author: Vincent van Ravesteijn
> >>Date: Wed May 23 01:31:43 2012 +0200
> >>
> >> Fix bug
If autogen.sh completes successfully, it outputs "run ./configure ; make". I do
not think this is good advice because what if configure has an error? The
"make" command will still run.
I suggest:
<> [autogen.patch]
because upon successful exit, configure tells you to run make and make install.
Le 23/05/2012 01:51, Vincent van Ravesteijn a écrit :
I don't understand what the problem is. If the patch modifying
src/Undo.cpp was committed. Then doing "git add src/Undo.cpp && git
commit --amend" will merge the new changes in the previous commit. If
you had done other commits in between, you
