From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jeff Horn <jrhorn424@gmail.com>
Cc: Emacs-orgmode@gnu.org
Subject: Re: capture problem
Date: Tue, 12 Oct 2010 06:51:16 +0200 [thread overview]
Message-ID: <6413AFDF-A9D5-4934-B4C1-F54ED4703FFC@gmail.com> (raw)
In-Reply-To: <AANLkTin26d3op4jGyo1jzkWCsiteCDfhmnfhGRu8GhV0@mail.gmail.com>
Could one of you try to make a backtrace for this problem?
Thanks
- Carsten
On Oct 11, 2010, at 7:33 PM, Jeff Horn wrote:
> I get this problem frequently as well. I think it is due to capture
> trying to create a link from the kill ring (if you have a template
> that automatically creates a link of where you were or what you were
> working on for context).
>
> I just kill some text and yank it right back in place, but it puts new
> text on the kill ring, which seems to fix the problem.
>
> I think the problem arises in the first place since I use Aquamacs
> (and CUA mode), and I'm not consistent in how I kill or copy text. It
> could be that I have an image on the Mac pasteboard, and so org
> (through Aquamacs) tries to put that in my capture item template when
> I call org-capture.
>
> HTH,
> Jeff
>
> On Mon, Oct 11, 2010 at 9:45 AM, Jörg Hagmann
> <joerg.hagmann@unibas.ch> wrote:
>> Regarding capture:
>>
>> When using "cature", after having selected the template, I often
>> get the
>> message:
>> "byte-code: Capture abort: (quit pasteboard doesn't contain valid
>> data)"
>> It works again after reloading .emacs.
>> What is the problem?
>>
>> Emacs 23.2.1, recent pull.
>>
>> Thanks, Jörg
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
>
>
> --
> Jeffrey Horn
> Graduate Lecturer and PhD Student in Economics
> George Mason University
>
> (704) 271-4797
> jhorn@gmu.edu
> jrhorn424@gmail.com
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-10-12 4:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 13:45 capture problem Jörg Hagmann
2010-10-11 17:33 ` Jeff Horn
2010-10-12 4:51 ` Carsten Dominik [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-12-30 7:14 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
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=6413AFDF-A9D5-4934-B4C1-F54ED4703FFC@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jrhorn424@gmail.com \
/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).