From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giacomo M Subject: Re: Get to next NEXT headline with one key Date: Fri, 07 Mar 2014 17:23:12 +0100 Message-ID: <5319F270.10605@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60737) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLxYP-0000Aa-QT for emacs-orgmode@gnu.org; Fri, 07 Mar 2014 11:23:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLxYK-00024m-En for emacs-orgmode@gnu.org; Fri, 07 Mar 2014 11:23:21 -0500 Received: from mail-ea0-x232.google.com ([2a00:1450:4013:c01::232]:56425) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLxYK-00024a-8F for emacs-orgmode@gnu.org; Fri, 07 Mar 2014 11:23:16 -0500 Received: by mail-ea0-f178.google.com with SMTP id a15so2416208eae.23 for ; Fri, 07 Mar 2014 08:23:15 -0800 (PST) Received: from [192.168.228.178] ([212.189.161.135]) by mx.google.com with ESMTPSA id l42sm8316689eew.19.2014.03.07.08.23.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Mar 2014 08:23:14 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org (typo in my previous email: s/to Matt/to John/) Il 07/03/2014 15:44, Oleh ha scritto: > If you're feeling adventurous, you can try my new minor mode: > https://github.com/abo-abo/worf. Thank you, Oleh! Just tried it, and I think it has several convenient features. > And commands work from start of #+... as well. Like this one. > Here's how I've implemented the functionality that you want: > > "j"/"k" are bound move down/up just like in vim, but they move by > headings or #+ markers. > But "K" can change their behavior temporarily: it will prompt you for > a char that corresponds to a keyword: > t - TODO > d - DONE > n - NEXT > c - CANCELLED > > After a keyword is set, "j"/"k" will move by this keyword instead, > until any command other than "j"/"k" is issued (for instance "m", > which reveals heading). After that "j"/"k" will return to their > regular behavior. > Question: is there a particular reason for restricting keyword j/k movement only to - headlines at lower/equal levels (I get stuck in the subtree with the first NEXT)? - visible headlines (I miss folded NEXT entries)? Still eventually I would like to pack those "Knjm" keys into just one key to replicate what is done by Matt my-org-next-next() function. > And if you're trying out the mode, make sure to try "g" and "h" - those > are my two favorites. `helm` and `ace-jump-mode` respectively are required > in order for these commands to work. I'm planning to add the package to MELPA, > so the dependencies would be downloaded automatically, but I don't want to add > it until I've assigned all the alphanumeric keys:) I didn't know ace-jump-base... it really made my day! And yes, g and h can be quite useful. Do you think that the selection procedure of *helm* could be compatible with sth like ace-jump-line-mode? The problem then will be to find a good keyword also for activating the ace commands. I think this is a good step towards the ultimate keystroke-minimizing editing environment... it's just a thousand key-bindings-to-memorize away, but I can see it!