emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Orgmode] Re: Bug (?) in org-capture


From: Robert Goldman
Subject: [Orgmode] Re: Bug (?) in org-capture
Date: Thu, 14 Oct 2010 10:14:57 -0500
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4

On 10/14/10 Oct 14 -9:40 AM, Robert Goldman wrote:
> I was trying to experiment for the first time using org-capture together
> with w3m today, and I get an error.
> 
> I invoke org-capture, and was pleased to find that it built me a buffer
> just fine, and made an org link for the URL of the w3m buffer.  So far,
> so good.
> 
> Unfortunately, when I try to save the buffer, either with C-c C-c or C-c
> C-w, I get an error.
> 
> The error is in org-capture-bookmark-last-stored-position.  Here:
> 
> (defun org-capture-bookmark-last-stored-position ()
>   "Bookmark the last-captured position."
>   (let* ((where (org-capture-get :position-for-last-stored 'local))
>     ....)
> 
> WHERE gets bound to NIL, the return of ORG-CAPTURE-GET, causing an error.
> 
> I'm quite prepared to believe that I have this horribly misconfigured,
> since I really didn't configure it at all, but it's disappointing that
> the buffer creation works so well without configuration, but leaves me
> in this pickle.  It's also disappointing that the refile command doesn't
> work --- any chance of hacking it so that it does something sensible (I
> was thinking involving interactive selection) when org-capture is not
> yet configured?
> 
> AFAICT the direct cause of the error is that org-capture-current-plist
> is NIL, and the 'local spec in this call means that we consult that
> instead of org-capture-plist.
> 
> At this point my ability to understand the code peters out, and I'm
> afraid I don't have anything useful to say.

Sorta never mind --- I figured out what the problem was.  Somehow the
default file for org-capture was ~/org//notes.org not ~/org/notes.org,
so there was really a "file not found" error here.

So this is, in a sense, user error.

That said, if it's not too much trouble, maybe reporting a file not
found error for this would be more helpful than crashing in this way.

On the other hand, this might be tricky to find and handle, so maybe
it's not worth the trouble.

best,
r



reply via email to

[Prev in Thread] Current Thread [Next in Thread]