From: Carsten Dominik <dominik@science.uva.nl>
To: Daniel Clemente <n142857@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Move point to next-line after clocking in
Date: Wed, 11 Feb 2009 15:11:00 +0100 [thread overview]
Message-ID: <8510630D-C164-4BA6-924D-87481E94ADF0@uva.nl> (raw)
In-Reply-To: <87ocxfm76f.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1132 bytes --]
Fixed, thanks.
- Carsten
On Feb 7, 2009, at 1:17 AM, Daniel Clemente wrote:
>
> Hi.
> Consider a file with 2 lines:
>
> ------------------
> **** heading
>
> ------------------
>
> Place the cursor at line 2 (where you can type). Then use C-c C-x C-
> i to start a clock.
> You have now 3 lines:
>
> ------------------
> **** heading
> CLOCK: [2009-02-07 sáb 01:06]
>
> ------------------
>
> However, the cursor is still placed at line 2, like before. I think
> it would be more useful if it were moved to line 3 so that you can
> start writing right away, just as before.
> This saves you the C-n needed to move again to a blank line.
>
> I don't know if other actions would also benefit from this, for
> instanc clocking in for a second time (thus adding a properties
> block). It's probably not needed.
>
>
> Thanks,
> Daniel with org 6.20g
>
>
> _______________________________________________
> 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
[-- Attachment #1.2: Type: text/html, Size: 1488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
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
prev parent reply other threads:[~2009-02-11 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 0:17 Move point to next-line after clocking in Daniel Clemente
2009-02-11 14:11 ` Carsten Dominik [this message]
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=8510630D-C164-4BA6-924D-87481E94ADF0@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@gmail.com \
/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).