From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: FR: Tap stops in org-capture templates
Date: Mon, 15 Nov 2010 06:54:10 -0600 [thread overview]
Message-ID: <20101115125410.GC3139@x201> (raw)
In-Reply-To: <1FB1A49B-5FD5-48CD-A9FC-94FC751DA41F@gmail.com>
On Mon, Nov 15, 2010 at 07:51:52AM +0100, Carsten Dominik wrote:
>
> On Nov 15, 2010, at 12:53 AM, Russell Adams wrote:
>
> >I reviewed the org-manual for capture, and noticed that we don't have
> >a way to specify tab stops. I use yasnippet all the time to enter
> >information, and I can tab from field to field.
> >
> >Can capture do the same?
>
> Hi Russel,
>
> can't you just use a yasnippet in a capture buffer?
>
> - Carsten
Certainly, if that's the preferred method.
Given that, I'm trying to get yasnippet to trigger via elisp when
capture creates the new buffer.
A template of "\n\ncontact%(yas/expand)" fails with:
condition-case: Capture abort: (wrong-type-argument char-or-string-p nil)
And a template of:
"\n\n%(yas/expand-snippet (yas/template-content (yas/get-template-by-uid 'org-mode \"contact\")))"
fails with:
condition-case: Capture template `c': The kill is not a (set of) tree(s) - please use <S-insertchar> to yank anyway
Anyone more familiar with elisp that can give me some insight?
Thanks.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2010-11-15 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 23:53 FR: Tap stops in org-capture templates Russell Adams
2010-11-15 6:51 ` Carsten Dominik
2010-11-15 12:54 ` Russell Adams [this message]
2010-11-15 13:01 ` Carsten Dominik
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=20101115125410.GC3139@x201 \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.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).