From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: [BUG] crash while ping-ponging between back-to-back footnotes. Date: Wed, 29 Jun 2011 18:22:22 +0530 Message-ID: <81sjqsby0p.fsf@gmail.com> References: <81hb78n9i8.fsf@gmail.com> <87tyb8bz3t.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:35709) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbuG4-00021d-Vb for emacs-orgmode@gnu.org; Wed, 29 Jun 2011 08:52:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QbuG3-0000TB-Jq for emacs-orgmode@gnu.org; Wed, 29 Jun 2011 08:52:44 -0400 Received: from mail-pz0-f41.google.com ([209.85.210.41]:33173) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbuG3-0000T5-8N for emacs-orgmode@gnu.org; Wed, 29 Jun 2011 08:52:43 -0400 Received: by pzk4 with SMTP id 4so1039327pzk.0 for ; Wed, 29 Jun 2011 05:52:42 -0700 (PDT) In-Reply-To: <87tyb8bz3t.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 29 Jun 2011 14:28:54 +0200") 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: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Hello, > > Jambunathan K writes: > >> Summary: Sample org file down below also doubles up as bug report. >> >> * Sample >> >> Add footnote-1 using C-c C-x f [fn:1][fn:2] >> >> * Footnotes >> >> [fn:1] This is footnote-1. Jump back to the text by mouse-clicking the >> footnote link. Once you jump back, immediately create another >> footnote reference using C-c C-x f. >> >> [fn:2] This footnote-2. Try jumping back to text by mouse-clicking >> this fn-2 link. Note the following message on the screen "if: Cannot >> find reference of footnote fn:2". Stack trace is attached.. > > [...] > > Did you try it with git head? I can't reproduce it. Confirming that this is a bogus bug report for master repo. (I think I was seeing this issue on ngz) > Regards,