From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Release 6.33 Date: Fri, 13 Nov 2009 22:30:32 +0100 Message-ID: <025CD576-0BC4-4561-8771-B2F09809228B@uva.nl> References: <87aayqfh8a.wl%ucecesf@ucl.ac.uk> <8D1991FE-E04A-41DF-8919-C72E4EA9AFF1@uva.nl> <87vdhe1abc.fsf@stats.ox.ac.uk> 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 1N93j9-0001bv-8A for emacs-orgmode@gnu.org; Fri, 13 Nov 2009 16:30:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N93j4-0001ac-HI for emacs-orgmode@gnu.org; Fri, 13 Nov 2009 16:30:42 -0500 Received: from [199.232.76.173] (port=57172 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N93j4-0001aZ-Bz for emacs-orgmode@gnu.org; Fri, 13 Nov 2009 16:30:38 -0500 Received: from pony.ic.uva.nl ([145.18.40.181]:39427) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N93j3-0002V2-Tf for emacs-orgmode@gnu.org; Fri, 13 Nov 2009 16:30:38 -0500 In-Reply-To: <87vdhe1abc.fsf@stats.ox.ac.uk> 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: Dan Davison Cc: Emacs-orgmode mailing list On Nov 13, 2009, at 8:41 PM, Dan Davison wrote: > Carsten Dominik writes: > >> On Nov 13, 2009, at 6:48 PM, Eric S Fraga wrote: >> >>> At Fri, 13 Nov 2009 09:51:11 +0100, >>> Carsten Dominik wrote: >>>> >>>> here are the Changes in the latest release 6.33. Emacs 23.2, >>>> when it >>> >>> [...] >>> >>>> Speed commands at the start of a headline >>>> ========================================== >>> >>> Excellent addition! This makes org-mode even /more/ usable on >>> systems >>> with very small keyboards (like smartphones etc). I'd been using >>> viper-mode to have single key movement in org-mode buffers but >>> you've >>> not only made this possible but have completely exceeded my >>> requirements through all the extra commands available (clocking in, >>> etc.). Fantastic! > > > Me too, this looks great. I think it's going to have me learning > lots of > org commands that I hadn't got round to learning before. My first > questions: > > n outline-next-visible-heading > p outline-previous-visible-heading > f org-forward-same-level > b org-backward-same-level > > It would be nice if I could keep tapping these, safe in the knowledge > that I would remain within the world of speed-commands. Hi Dan, this is an important point, and it now works like this. > However, they > can all 'fall off the edge' and start inserting characters. If that > behaviour is critical to org-mode when calling the functions directly, > is it nevertheless worth considering making the behaviour slightly > different for speed commands? I.e. e.g. make 'n' refuse to do anything > if there is no next visible heading. (I suppose that could be done > with > new optional args to org-[f/b]-same-level (I don't know about > outline-[n/p]-visible-heading; would that be a suitable situation for > defadvice?)) > > Secondly, is it worth considering expanding the speed-command zone to > include any position in the leading asterisks (perhaps even in the > TODO > keyword, seeing as this is non-default behaviour)? Well, I am not comfortable with this, so I don't want to put this in as a standard option. But you can now set `org-use-speed- commands' to a predicate function that tests for appropriate location. Let us know if you have a good one, maybe I will put it in anyway. - Carsten