Re: [O] bisected

2015-04-30 Thread Detlef Steuer
Am Thu, 30 Apr 2015 11:59:32 +0200 schrieb Bastien : > There was a hidden clue the commit could be problematic... > > Gregor Zattler writes: > > > First bad commit is: > > bad0409c3b86e09c4559e97d5f394356c6ccbe7f > ^^^ That must be a first look at the singularity. "The git" knows it all. I

Re: [O] bisected

2015-04-30 Thread Gregor Zattler
Hi Nicolas, * Nicolas Richard [30. Apr. 2015]: > Gregor Zattler writes: > > Sorry, no: > > From Bastien's comment, I wonder : does the following patch helps ? Yes, but see my other email: The fix in ea575950d957fcecc74ed6f53c29bb6b77e9fe26 works. Thanks, grgeor

Re: [O] bisected

2015-04-30 Thread Nicolas Richard
Gregor Zattler writes: > Sorry, no: >From Bastien's comment, I wonder : does the following patch helps ? --- /dev/fd/63 2015-04-30 13:44:20.900676564 +0200 +++ /tmp/org-src.el 2015-04-30 13:43:50.924673810 +0200 @@ -539,35 +539,36 @@ - When formatting a source code snippet for export with

Re: [O] bisected

2015-04-30 Thread Gregor Zattler
Hi Nicolas, * Nicolas Richard [30. Apr. 2015]: > Gregor Zattler writes: > > First bad commit is: > > bad0409c3b86e09c4559e97d5f394356c6ccbe7f > > Nice hash for a "bad" commit :) I didn't realise :-) > > This results in a startup error: > > Debugger entered--Lisp error: (void-variable write-

Re: [O] bisected

2015-04-30 Thread Nicolas Richard
Gregor Zattler writes: > First bad commit is: > bad0409c3b86e09c4559e97d5f394356c6ccbe7f Nice hash for a "bad" commit :) > This results in a startup error: > Debugger entered--Lisp error: (void-variable write-back) Is it related to your initial problem ? I think this specific bug was fixed

Re: [O] bisected

2015-04-30 Thread Bastien
There was a hidden clue the commit could be problematic... Gregor Zattler writes: > First bad commit is: > bad0409c3b86e09c4559e97d5f394356c6ccbe7f ^^^ !