From: Nathan Neff <nathan.neff@gmail.com>
To: Erik Iverson <eriki@ccbr.umn.edu>
Cc: "Dan Davison" <davison@stats.ox.ac.uk>,
emacs-orgmode@gnu.org, "Štěpán Němec" <stepnem@gmail.com>
Subject: Re: Re: [Babel] Macro for begin_src?
Date: Sat, 17 Apr 2010 09:28:51 -0500 [thread overview]
Message-ID: <r2p211769421004170728p53249256qac6e4fb8476dec6@mail.gmail.com> (raw)
In-Reply-To: <4BC9C082.6040709@ccbr.umn.edu>
[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]
On Sat, Apr 17, 2010 at 9:06 AM, Erik Iverson <eriki@ccbr.umn.edu> wrote:
>
> I'm guessing what you really want there is
>>
>> (set (make-local-variable 'yas/trigger-key) [tab])
>>
>> instead of
>>
>> > (make-variable-buffer-local 'yas/trigger-key)
>> > (setq yas/trigger-key [tab])
>>
>>
>> Hmmm.
>>
>> Do you guys un-map your TAB key so that it doesn't run org-cycle?
>> My TAB key will correctly trigger yas/insert-snippet in emacs-lisp mode.
>> However, in org-mode my TAB key is still mapped to org-cycle, even if I
>> add the org-mode hook using the code above.
>>
>> Thanks,
>> --Nate
>>
>>
> The order you do it might matter?
>
I found the problem -- it's detailed right here, and it's tailored to fix
compatibility with org-mode:
http://yasnippet.googlecode.com/svn/trunk/doc/faq.html
--Nate
[-- Attachment #1.2: Type: text/html, Size: 1446 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
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-04-17 14:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 1:18 [Babel] Macro for begin_src? Nathan Neff
2010-04-17 1:32 ` Nathan Neff
2010-04-17 2:23 ` Erik Iverson
2010-04-17 10:12 ` Eric S Fraga
2010-04-17 13:38 ` Nathan Neff
2010-04-18 1:01 ` Shelagh Manton
2010-04-18 10:44 ` Eric S Fraga
2010-04-19 0:24 ` Shelagh Manton
2010-04-19 2:06 ` Bernt Hansen
2010-04-19 8:33 ` Eric S Fraga
2010-04-19 11:05 ` Sebastian Rose
2010-04-20 9:19 ` Sébastien Vauban
2010-04-20 10:27 ` [OT] " Eric S Fraga
2010-04-20 14:48 ` Eric Schulte
2010-10-17 16:56 ` Rainer M Krug
2010-10-17 17:10 ` Eric Schulte
2010-10-18 15:02 ` Sébastien Vauban
2010-10-18 15:42 ` Dan Davison
2010-10-18 21:01 ` Sébastien Vauban
2010-10-18 16:50 ` Greg Troxel
2010-04-17 16:52 ` Matt Lundin
2010-04-18 1:55 ` Thomas S. Dye
2010-04-18 10:41 ` Eric S Fraga
2010-04-18 16:50 ` Dan Davison
2010-04-18 20:13 ` Štěpán Němec
2010-04-18 20:25 ` Eric S Fraga
2010-04-17 2:35 ` Dan Davison
2010-04-17 3:43 ` Nathan Neff
2010-04-17 3:55 ` Dan Davison
2010-04-17 11:03 ` Štěpán Němec
2010-04-17 13:56 ` Nathan Neff
2010-04-17 14:06 ` Erik Iverson
2010-04-17 14:28 ` Nathan Neff [this message]
2010-04-17 15:05 ` Eric Schulte
2010-04-17 1:34 ` Thomas S. Dye
2010-04-17 1:37 ` Bernt Hansen
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=r2p211769421004170728p53249256qac6e4fb8476dec6@mail.gmail.com \
--to=nathan.neff@gmail.com \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=eriki@ccbr.umn.edu \
--cc=stepnem@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).