From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fletcher Charest Subject: Re: Agenda items refer to the wrong headline Date: Wed, 9 Apr 2014 16:36:22 +0200 Message-ID: References: <87y4zggeb8.fsf@gmail.com> <87lhvfgnto.fsf@gmail.com> <87r456sj9a.fsf@alphaville.bos.redhat.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b3a896c46451004f69d06ae Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59972) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXtc4-0003lR-5j for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 10:36:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WXtbz-0004OW-Vg for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 10:36:28 -0400 Received: from mail-wi0-x22b.google.com ([2a00:1450:400c:c05::22b]:42726) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXtbz-0004NB-PW for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 10:36:23 -0400 Received: by mail-wi0-f171.google.com with SMTP id q5so9010359wiv.10 for ; Wed, 09 Apr 2014 07:36:22 -0700 (PDT) In-Reply-To: <87r456sj9a.fsf@alphaville.bos.redhat.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nick Dokos Cc: emacs-orgmode@gnu.org --047d7b3a896c46451004f69d06ae Content-Type: text/plain; charset=ISO-8859-1 Nick, you say you could not reproduce the bug using version 8.2.5h-667-g971dc4, but you did with version 8.2.5h-888-g798bb8d. Just out of curiosity: does the '888' in '8.2.5h-888-g798bb8d' is a number that is incremented chronologically? If this is correct (I'm not familiar with this at all), FWIW, the bug was not caused only by the patch '8.2.5h-888-g798bb8d', since I observed it also with version 8.2.5h-94-g91175a. FC On Wed, Apr 9, 2014 at 3:52 PM, Nick Dokos wrote: > Nick Dokos writes: > > > > > Starting from release_8.2.5h-888-g798bb8d (this was latest as of this > > morning) and reverting the above commit fixes Fletcher's problem. > > > > Just to be clear: I'm *not* advocating that the commit be reverted. > I used the revert just to confirm that something in that patch caused > the problem that Fletcher observed. > > Nick > > > --047d7b3a896c46451004f69d06ae Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Nick, you say you could not reproduce the = bug using version 8.2.5h-667-g971dc4, but you did with version 8.2.5h-888-g= 798bb8d. Just out of curiosity: does the '888' in '8.2.5h-888-g= 798bb8d' is a number that is incremented chronologically? If this is co= rrect (I'm not familiar with this at all), FWIW, the bug was not caused= only by the patch '8.2.5h-888-g798bb8d', since I observed it also = with version 8.2.5h-94-g91175a.

FC


On Wed, Apr 9, 2014 at 3:52 PM, Nick Dokos <<= a href=3D"mailto:ndokos@gmail.com" target=3D"_blank">ndokos@gmail.com&g= t; wrote:
Nick Dokos <ndokos@gmail.com> writes:

>
> Starting from release_8.2.5h-888-g798bb8d (this was latest as of this<= br> > morning) and reverting the above commit fixes Fletcher's problem.<= br> >

Just to be clear: I'm *not* advocating that the commit be reverte= d.
I used the revert just to confirm that something in that patch caused
the problem that Fletcher observed.

Nick



--047d7b3a896c46451004f69d06ae--