emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: bisected
Date: Thu, 30 Apr 2015 12:05:05 +0200	[thread overview]
Message-ID: <87wq0u53u6.fsf@yahoo.fr> (raw)
In-Reply-To: <20150430094957.GC22882@boo.workgroup> (Gregor Zattler's message of "Thu, 30 Apr 2015 11:49:57 +0200")

Gregor Zattler <telegraph@gmx.net> 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 in :
Commit ea575950d957fcecc74ed6f53c29bb6b77e9fe26

modified   lisp/org-src.el
@@ -543,7 +543,7 @@ (define-minor-mode org-src-mode
     (org-set-local
      'header-line-format
      (substitute-command-keys
-      (if write-back
+      (if org-src--allow-write-back
 	  "Edit, then exit with \\[org-edit-src-exit] or abort with \
 \\[org-edit-src-abort]"
 	"Exit with \\[org-edit-src-exit] or abort with \

-- 
Nico

  parent reply	other threads:[~2015-04-30 10:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30  8:04 "not in sub-editing buffer" Detlef Steuer
2015-04-30  8:23 ` Bastien Guerry
2015-04-30  9:49 ` bisected (was: )Re: " Gregor Zattler
2015-04-30  9:59   ` bisected Bastien
2015-04-30 12:12     ` bisected Detlef Steuer
2015-04-30 10:05   ` Nicolas Richard [this message]
2015-04-30 10:53     ` bisected Gregor Zattler
2015-04-30 11:46       ` bisected Nicolas Richard
2015-04-30 12:08         ` bisected Gregor Zattler
2015-04-30 12:05       ` wrong test, fix works, sorry (was: Re: bisected) Gregor Zattler
2015-04-30 15:50         ` now it get's ridiculous: bug is still there (was: Re: wrong test, fix works, sorry (was: Re: bisected)) Gregor Zattler
2015-05-01  8:31 ` "not in sub-editing buffer" Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq0u53u6.fsf@yahoo.fr \
    --to=theonewiththeevillook@yahoo.fr \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).