From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: org-refile bug Date: Thu, 18 Mar 2010 06:49:36 +0100 Message-ID: References: <87634v3g29.fsf@riotblast.dunsmor.com> <878w9rcm0f.fsf@eee.lan> <87ocin0xsl.fsf@riotblast.dunsmor.com> <87fx3yc3hr.fsf@eee.lan> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ns9j9-0008NS-4T for emacs-orgmode@gnu.org; Thu, 18 Mar 2010 03:01:07 -0400 Received: from [140.186.70.92] (port=54179 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ns9j4-0008LV-ME for emacs-orgmode@gnu.org; Thu, 18 Mar 2010 03:01:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ns9j2-0002hQ-RR for emacs-orgmode@gnu.org; Thu, 18 Mar 2010 03:01:02 -0400 Received: from ey-out-1920.google.com ([74.125.78.148]:17132) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ns9j0-0002h3-O2 for emacs-orgmode@gnu.org; Thu, 18 Mar 2010 03:00:59 -0400 Received: by ey-out-1920.google.com with SMTP id 4so147590eyg.34 for ; Thu, 18 Mar 2010 00:00:57 -0700 (PDT) In-Reply-To: <87fx3yc3hr.fsf@eee.lan> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Mikael Fornius Cc: emacs-orgmode@gnu.org On Mar 17, 2010, at 5:33 PM, Mikael Fornius wrote: > > This goes beyond my knowledge of org-remember. > > Maybe it has something to do with corrupt org-*-last-stored data if > the > last org-entry data is removed or changed? Just guessing here... > > I tried to corrupt the data myself, then did bookmark-load and > org-remember C-1 C-c C-c but then it worked. > > When looking briefly in org-remember.el I could not find any > bookmark-* > function call that looked like it was depending on its success. > > Just so you have not forgotten: did you search all your org-agenda- > files > if the entry was misplaced somewhere? > > Someone with better knowledge of org-remember then me can sort this > out? I think your analysis is correct. The bookmark-set function is always called *after* the note has been inserted at the target location. So even if it fails, the note should not disappear. Without a reproducible test case, it is difficult to do more here. - Carsten