From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: capture problem Date: Fri, 30 Dec 2011 07:27:55 -1000 Message-ID: References: <80pqf6pfkd.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([140.186.70.92]:38359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RggFQ-0005gk-VF for emacs-orgmode@gnu.org; Fri, 30 Dec 2011 12:28:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RggFP-0007zO-Mu for emacs-orgmode@gnu.org; Fri, 30 Dec 2011 12:28:04 -0500 Received: from oproxy3-pub.bluehost.com ([69.89.21.8]:47583) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RggFP-0007zF-Fd for emacs-orgmode@gnu.org; Fri, 30 Dec 2011 12:28:03 -0500 In-Reply-To: <80pqf6pfkd.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 30 Dec 2011 10:35:46 +0100") 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: Sebastien Vauban Cc: emacs-orgmode@gnu.org "Sebastien Vauban" writes: > Hi Thomas, > > Thomas S. Dye wrote: >> I'm sometimes running into this error message when I capture: >> >> condition-case: Capture abort: (quit pasteboard doesn't contain valid data) >> >> Unfortunately, this doesn't mean anything to me. The problem arises >> after I've been working for a while, but I haven't an idea why it >> starts, or any clue to what might trigger it. >> >> I realize this isn't much to go on, and a long way from an ECM, but I >> don't know what to do. Any ideas on how to track this down will be >> appreciated. >> >> I'm using Org-mode version 7.8.02 (release_7.8.02.13.g0c09a.dirty). > > Yesterday, with yesterday's update, I've as well have had something similar: > capture refused to work, after well having worked previously -- in the same > Emacs instance --, and launched me a cryptic reason. > > Though, the reason was not the same as yours. Maybe because I'm on Windows? > > Anyway, I should have noted down the message. I just restarted Emacs then, and > did not experience any other problem with the capture process. > > I'll keep you posted otherwise. > > Best regards, > Seb Hi Seb, Yes, restarting emacs works for me too. I typically leave emacs running, though. The last 3 or 4 times I've shutdown and restarted emacs have been due to this capture problem. I'll pay closer attention and see if I can figure what might trigger it. All the best, Tom -- Thomas S. Dye http://www.tsdye.com