emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: BUG: Navigating table to change fields
Date: Mon, 20 Apr 2009 15:02:18 -0700	[thread overview]
Message-ID: <m2tz4jdlw5.fsf@gmail.com> (raw)
In-Reply-To: <0F844E46-FB8E-4118-9034-E7A9C12168EE@gmail.com> (Carsten Dominik's message of "Mon, 20 Apr 2009 23:09:20 +0200")

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)))
    (setq pending (cdr pending))))

If the existing org-cycle actions (fold headline, org-cycle-table,
etc...) were implemented using the list then users could have the
options of putting their actions before or after (after being good if
say they have a very expensive check which shouldn't be run every time
tab is hit).

Does that sound appropriate? -- Eric

Carsten Dominik <carsten.dominik@gmail.com> writes:

> 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 situation where a
>> hook would have been preferable. -- Eric
>>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> 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. :/  It works fine for a minimal
>>>> emacs
>>>> test.
>>>>
>>>> -Bernt
>>>>
>>>> Bernt Hansen <bernt@norang.ca> writes:
>>>>
>>>>> Okay I think this is a bug.  If I traverse the table FORWARDS with
>>>>> TAB
>>>>> and type it inserts in front of the field that is there.  If I
>>>>> traverse
>>>>> it BACKWARDS with S-TAB it clears the field when I type.
>>>>>
>>>>> This seems inconsistent (and I really like the blank the field as
>>>>> soon
>>>>> as you type behaviour)
>>>>>
>>>>> -Bernt
>>>>>
>>>>>
>>>>> Bernt Hansen <bernt@norang.ca> writes:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Did the user interface for tables change recently?  When I TAB
>>>>>> between
>>>>>> fields in a table entering anything normally blanks out the field
>>>>>> and
>>>>>> replaces it with whatever new I am typing.
>>>>>>
>>>>>> Today it always seems to insert in front of whatever is already
>>>>>> there.
>>>>>>
>>>>>> I'm just wondering if this was an intentional change or if it's a
>>>>>> bug.
>>>>>> I didn't notice anything in the release notes about this (but
>>>>>> maybe I
>>>>>> just missed it).
>>>>>>
>>>>>> -Bernt
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Emacs-orgmode mailing list
>>>>>> Remember: use `Reply All' to send replies to the list.
>>>>>> Emacs-orgmode@gnu.org
>>>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Emacs-orgmode mailing list
>>>>> Remember: use `Reply All' to send replies to the list.
>>>>> Emacs-orgmode@gnu.org
>>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>
>>>>
>>>> _______________________________________________
>>>> Emacs-orgmode mailing list
>>>> Remember: use `Reply All' to send replies to the list.
>>>> Emacs-orgmode@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Remember: use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-04-20 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 18:11 Table changes - entering new fields Bernt Hansen
2009-04-20 18:17 ` BUG: Navigating table to change fields (was: Table changes - entering new fields) Bernt Hansen
2009-04-20 19:43   ` BUG: Navigating table to change fields Bernt Hansen
2009-04-20 20:35     ` Carsten Dominik
2009-04-20 21:02       ` Eric Schulte
2009-04-20 21:09         ` Carsten Dominik
2009-04-20 22:02           ` Eric Schulte [this message]
2009-04-21  7:44             ` Carsten Dominik
2009-04-20 22:51       ` Bernt Hansen
2009-04-21  7:51         ` 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=m2tz4jdlw5.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=carsten.dominik@gmail.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).