On Apr 21, 2009, at 12:51 AM, Bernt Hansen wrote:
That would probably be better. I just copied my current setup from
discussions on the org-mode list about yasnippet.
Is there anything I can do to help make that happen?
I have added this hook, see my other message.
I guess what you can do
On Apr 21, 2009, at 12:02 AM, Eric Schulte wrote:
Maybe a list rather than a hook, say `org-cycle-actions'. Each
element
of the list could be called in the current context until one returns a
non-nil result. Something like...
(let ((pending org-cycle-actions)
finished)
(while (not fi
That would probably be better. I just copied my current setup from
discussions on the org-mode list about yasnippet.
Is there anything I can do to help make that happen?
-Bernt
Carsten Dominik writes:
> Maybe we should have a hook in org-cycle where yasnippet can
> hook into, instead of overr
Maybe a list rather than a hook, say `org-cycle-actions'. Each element
of the list could be called in the current context until one returns a
non-nil result. Something like...
(let ((pending org-cycle-actions)
finished)
(while (not finished)
(setq finished (funcall (car pending)))
So what would be the right place to call it? Which context checks
should com before the hook, and which after?
- Carsten
On Apr 20, 2009, at 11:02 PM, Eric Schulte wrote:
A hook in org-cycle could be useful aside from yasnippets. I recently
found myself writing a defadvice for org-cycle in
A hook in org-cycle could be useful aside from yasnippets. I recently
found myself writing a defadvice for org-cycle in a situation where a
hook would have been preferable. -- Eric
Carsten Dominik writes:
> Maybe we should have a hook in org-cycle where yasnippet can
> hook into, instead of ove
Maybe we should have a hook in org-cycle where yasnippet can
hook into, instead of overruling the TAB key..
- Carsten
On Apr 20, 2009, at 9:43 PM, Bernt Hansen wrote:
Nevermind. It works.
Gah. Sorry for the noise. This turns out to be my yasnippet setup
messing up the TAB key in tables.
