emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: bisected
Date: Thu, 30 Apr 2015 12:53:04 +0200	[thread overview]
Message-ID: <20150430105304.GD22882@boo.workgroup> (raw)
In-Reply-To: <87wq0u53u6.fsf@yahoo.fr>

Hi Nicolas,
* Nicolas Richard <theonewiththeevillook@yahoo.fr> [30. Apr. 2015]:
> Gregor Zattler <telegraph@gmx.net> 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-back)
> Is it related to your initial problem ?

I don't know.  It appeared while git bisecting.

> I think this specific bug was fixed in :
> Commit ea575950d957fcecc74ed6f53c29bb6b77e9fe26

Sorry, no: 
GNU Emacs (i686-pc-linux-gnu, GTK+ Version 3.14.5) of
2015-04-27 on boo Org-mode version 8.3beta (release_8.3beta-1097-gea5759 @ /home/grfz/src/org-mode/lisp/)       

and emacs invoked with -Q I cannot save a modified file with ^x ^s
but when I leave emacs:

emacs -Q -nw /tmp/tempfile

change buffer, do ^x ^s.

Thanks for looking into this, Gregor

  reply	other threads:[~2015-04-30 10:53 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   ` bisected Nicolas Richard
2015-04-30 10:53     ` Gregor Zattler [this message]
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:

  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=20150430105304.GD22882@boo.workgroup \
    --to=telegraph@gmx.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).