From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Shift-Arrow Pass Through for windmove? Date: Sun, 25 Apr 2010 09:08:01 +0200 Message-ID: <791B9A5D-B71B-4B5A-B933-D321DE7485F8@gmail.com> References: <87633jb57w.wl%ded-law@ddoherty.net> <87ochaqhau.fsf@gmx.de> <5BE40E2F-2FB3-4010-9C68-8D66E351BED7@gmail.com> <87zl0tpxig.fsf@gmx.de> <87y6gdkyoh.fsf@gmx.de> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O5vx9-0002SP-BY for emacs-orgmode@gnu.org; Sun, 25 Apr 2010 03:08:31 -0400 Received: from [140.186.70.92] (port=42091 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O5vwq-0002Ql-GX for emacs-orgmode@gnu.org; Sun, 25 Apr 2010 03:08:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O5vwk-0005aj-FD for emacs-orgmode@gnu.org; Sun, 25 Apr 2010 03:08:09 -0400 Received: from mail-ew0-f214.google.com ([209.85.219.214]:52732) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O5vwj-0005a1-0w for emacs-orgmode@gnu.org; Sun, 25 Apr 2010 03:08:05 -0400 Received: by ewy6 with SMTP id 6so3671228ewy.32 for ; Sun, 25 Apr 2010 00:08:03 -0700 (PDT) In-Reply-To: <87y6gdkyoh.fsf@gmx.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastian Rose Cc: "Daniel E. Doherty" , "emacs-orgmode@gnu org" On Apr 24, 2010, at 11:05 AM, Sebastian Rose wrote: > Carsten Dominik writes: >> On Apr 24, 2010, at 1:19 AM, Sebastian Rose wrote: >> >>> Carsten Dominik writes: >>>> On Apr 23, 2010, at 6:12 PM, Sebastian Rose wrote: >>>> >>>>> Daniel E. Doherty writes: >>>>>> All, >>>>>> >>>>>> I make *very* frequent use of the shift-arrow keys to move from >>>>>> window >>>>>> to window inside emacs via windmove. It is probably the most >>>>>> frequent >>>>>> key combination I access. >>>>>> >>>>>> Anyway, is there a way to make org-mode friendlier to it by >>>>>> passing the >>>>>> key along whenever org-mode would otherwise throw an error. For >>>>>> example, when not on a heading, when in the agenda, and >>>>>> wherever else? >>>>>> >>>>>> I really like Carsten's use of the arrow keys for structure >>>>>> editing and >>>>>> don't want to lose that, just whenever org-mode can't make use >>>>>> of the >>>>>> keys. >>>>>> >>>>>> Regards, >>>>> >>>>> >>>>> >>>>> And here all the arrow keys. >>>>> >>>>> It's somewhat inelegant, since you always need to keep track of >>>>> new >>>>> useful org-bindings. >>>>> >>>>> I would find an org-internal solution helpfull too. I use >>>>> windmove. >>>> >>>> I have now added >>>> >>>> (defvar org-shiftup-hook nil >>>> "Hook for functions attaching themselves to `S-up'. >>>> See `org-ctrl-c-ctrl-c-hook' for more information.") >>>> (defvar org-shiftdown-hook nil >>>> "Hook for functions attaching themselves to `S-down'. >>>> See `org-ctrl-c-ctrl-c-hook' for more information.") >>>> (defvar org-shiftleft-hook nil >>>> "Hook for functions attaching themselves to `S-left'. >>>> See `org-ctrl-c-ctrl-c-hook' for more information.") >>>> (defvar org-shiftright-hook nil >>>> "Hook for functions attaching themselves to `S-right'. >>>> See `org-ctrl-c-ctrl-c-hook' for more information.") >>>> >>>> But I do not intend to attach specific functionality like >>>> windmove to them, >>>> and I'd like to reserve the possibility to make S-cursor do >>>> something >>>> in Org in more contexts. >>>> >>>> Hope this still helps. >>> >>> This could be perfect!!! >>> >>> But wouldn't the hook need to be called at the end of (e.g.) >>> `org-shiftright'? >>> >>> I want to use windmove as the last resort, as does the OP: >>> >>> >>> - (t (org-shiftselect-error)))) >>> + (t (if org-shiftright-hook >>> + ((run-hook-with-args-until-success 'org-shiftright-hook)) >>> + (org-shiftselect-error)))) >>> >>> ;; end of org-shiftright ($otpional arg) OK, I have now 4 more hooks org-shiftup-final-hook org-shiftdown-final-hook org-shiftleft-final-hook org-shiftright-final-hook They will run *before* Org is trying to support shift-select. I do not think i makes sense to run the after.... - Carsten >>> >>> >>> >>> Otherwise we would loose the org-mode specific functions. >>> >>> We want to >>> >>> 1. try to do somehing org-specific (if org-headline-p ....) >>> 2. else run the hook (i.e. windmove in this case) >>> 3. error only if 1. and 2. failed >>> >>> >>> We do use windmove but at the same time we do _not_ want to loose >>> all >>> those shift-right... features to come ;) >> >> Well, the idea is hat these hooks *can* overrule what org-mode >> wants to do, >> so whatever you put into the hook needs to decide if it wants to >> apply. >> >> We could add *another* hook at the end... > > > OK - I would love to use that one then. I could stick with my > functions > otherwise. > > Overruling is easily done, but to use windmove as a last resort could > not even be done using `ad-add-advice' because of the > > (t (org-shiftselect-error)) > > > > Sebastian - Carsten