From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Speed commands (was: Release 6.33)
Date: Fri, 20 Nov 2009 17:09:36 +0000 [thread overview]
Message-ID: <87lji16s33.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <95E34029-6EF2-4E77-B303-37676E5FA79F@gmail.com>
At Fri, 20 Nov 2009 15:57:09 +0100,
Carsten Dominik wrote:
> This is nice, but I guess you want to stay in fast-key space.
> So
>
> ("," . (progn (org-cycle-agenda-files)
> (or (and (bolp) (org-on-heading-p))
> (outline-next-visible-heading 1))))
This is really nice and works like a charm... *except* in a very
extreme case: one of my agenda files is typically empty other than a
single top level heading. When I cycle through the agenda files, when
I land in this file, I am typically placed at the end of the file
(emacs remembers my last location). When this happens, speed keys are
no longer active and, before I know it, I have a number of ',' added
to the end of this file!
Actually, I guess this problem generalises so that it would appear
whenever the cycling takes you to a file where the current point is at
the end (or near the end) of the file so there is actually no "next"
heading? Maybe the or statement above needs another clause (which I
unfortunately cannot suggest; sorry!).
next prev parent reply other threads:[~2009-11-20 17:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 8:51 Release 6.33 Carsten Dominik
2009-11-13 15:19 ` Daniel Clemente
2009-11-13 17:48 ` Eric S Fraga
2009-11-13 18:42 ` Carsten Dominik
2009-11-13 18:48 ` Carsten Dominik
2009-11-13 19:16 ` Speed commands (was: Release 6.33) Stephan Schmitt
2009-11-13 19:30 ` Carsten Dominik
2009-11-13 20:09 ` Speed commands Stephan Schmitt
2009-11-13 20:30 ` Carsten Dominik
2009-11-14 5:03 ` Dan Davison
2009-11-14 7:51 ` Benjamin Andresen
2009-11-14 15:48 ` Dan Davison
2009-11-15 2:44 ` Dan Davison
2009-11-15 10:54 ` Benjamin Andresen
2009-11-15 13:27 ` Carsten Dominik
2009-11-17 13:20 ` J. David Boyd
2009-11-17 14:44 ` J. David Boyd
2009-11-17 19:23 ` Dan Davison
2009-11-17 19:43 ` Carsten Dominik
2009-11-18 15:09 ` Jason Dunsmore
2009-11-18 22:54 ` Carsten Dominik
2009-11-20 14:35 ` Speed commands (was: Release 6.33) Friedrich Delgado Friedrichs
2009-11-20 14:57 ` Carsten Dominik
2009-11-20 16:29 ` Friedrich Delgado Friedrichs
2009-11-20 20:55 ` Eric S Fraga
2009-11-20 17:09 ` Eric S Fraga
2009-11-20 17:09 ` Eric S Fraga [this message]
2009-11-20 18:13 ` Speed commands Stephan Schmitt
2009-11-20 20:36 ` Eric S Fraga
2009-11-20 20:35 ` Speed commands (was: Release 6.33) Raffi R
2009-11-20 23:25 ` Friedrich Delgado Friedrichs
2009-11-20 23:38 ` Friedrich Delgado Friedrichs
2009-11-13 19:41 ` Release 6.33 Dan Davison
2009-11-13 21:30 ` Carsten Dominik
2009-11-13 23:03 ` Sebastian Rose
2009-11-15 7:19 ` Carsten Dominik
2009-11-15 10:02 ` Uwe Jochum
2009-11-15 13:27 ` Carsten Dominik
2009-11-15 14:07 ` Uwe Jochum
2009-11-15 11:37 ` Sebastian Rose
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=87lji16s33.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).