From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: capture problem
Date: Fri, 06 Jan 2012 09:33:10 +0100 [thread overview]
Message-ID: <80aa61nsc9.fsf@somewhere.org> (raw)
In-Reply-To: m11urdzth9.fsf@tsdye.com
Hi Thomas,
Thomas S. Dye wrote:
> "Sebastien Vauban"
> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> 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.
>
> I'm still running into this error. I've found that I don't have to stop
> emacs and restart. All I have to do is copy a bit of text and then run
> capture. This seems to work every time. Presumably, the text copy
> causes the pasteboard to contain valid data. I still don't know how the
> pasteboard gets invalid data in the first place.
FYI, I never got that problem again... and I'm still capture, not particularly
less or more than before. I don't know what that means...
The fact is that I'm updating Org every day or so. Could it have been fixed in
the meanwhile? Do you update that often as well?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-01-06 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 7:14 capture problem Thomas S. Dye
2011-12-30 9:07 ` Nick Dokos
2011-12-30 9:35 ` Sebastien Vauban
2011-12-30 17:27 ` Thomas S. Dye
2012-01-05 22:15 ` Thomas S. Dye
2012-01-06 8:33 ` Sebastien Vauban [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-11 13:45 Jörg Hagmann
2010-10-11 17:33 ` Jeff Horn
2010-10-12 4:51 ` Carsten Dominik
2010-10-12 4:55 ` Jeff Horn
2010-10-17 6:18 ` Carsten Dominik
2010-10-20 5:19 ` Jeff Horn
2010-10-20 5:20 ` Jeff Horn
2010-10-20 6:02 ` Jeff Horn
2010-10-20 6:05 ` Carsten Dominik
2010-10-20 6:45 ` Jeff Horn
2010-10-20 6:08 ` Noorul Islam K M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80aa61nsc9.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).