From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Bastien <bastienguerry@googlemail.com>, emacs-orgmode@gnu.org
Subject: Re: Re: C-u C-c C-x C-j to directly jump to the task with there is just one?
Date: Wed, 22 Apr 2009 06:19:09 +0200 [thread overview]
Message-ID: <E0FF9973-ABEE-475D-B445-E97C4E6F4249@gmail.com> (raw)
In-Reply-To: <87r5zl97j1.fsf@gollum.intra.norang.ca>
On Apr 21, 2009, at 8:38 PM, Bernt Hansen wrote:
> One problem with that might be if people (including me) use C-c C-x
> C-j
> to see if the clock is running :)
>
> I've mapped F11 = C-c C-x C-j so I just hit that key all the time. If
> it beeps and says 'no active clock' then I know I have to start the
> clock on something. Jumping to the last clocked item when no clock is
> running will change that behaviour (although I'm not sure that's
> really
> bad) I could (and probably should) just get in the habit of looking
> at
> the modeline instead :)
Yes, maybe. Or use a special function that tests for
(marker-buffer org-clock-marker)
I would even think a function to test for the clock without going
there might be better for this purpose - because you will not always
want to go there just for checking....
- Carsten
>
> -Bernt
>
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Apr 21, 2009, at 7:22 PM, Bernt Hansen wrote:
>>
>>> The current task [c] and the first task [1] are always the same
>>> aren't
>>> they? So using '1' for that already works.
>>>
>>> Maybe a better solution is to make it work without the prefix? Go
>>> to
>>> the current clocking task and if there is none then go to the last
>>> clocked task (if you can find it) otherwise issue the error we get
>>> now:
>>> "org-clock-goto: No active clock"
>>>
>>> That way you can just do C-c C-x C-j with no prefix and you are on
>>> the
>>> last clocked task (whether it is clocking now or not.)
>>
>> This does make sense, and I have done it like this.
>>
>> Bastien, is this to your liking as well?
>>
>> Thanks.
>>
>> - Carsten
>>
>>>
>>> I don't see how adding RET for the menu which means the same as [1]
>>> will
>>> really help.
>>>
>>> -Bernt
>>>
>>>
>>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>>
>>>> How about making RET an alias for either the task
>>>> currently being clocked, or the most recently clocked
>>>> one, or the default task, first one of this sequence
>>>> that exists?
>>>>
>>>> Hmmm, not sure if this really makes a difference....
>>>>
>>>> - Carsten
>>>>
>>>>
>>>> On Apr 21, 2009, at 3:33 PM, Bernt Hansen wrote:
>>>>
>>>>> Bastien <bastienguerry@googlemail.com> writes:
>>>>>
>>>>>> When the list of recent tasks only has one item, would it make
>>>>>> sense to
>>>>>> directly jump to it? Or maybe people use `C-u C-c C-x C-j' as a
>>>>>> way to
>>>>>> check what has been done (without jumping to the task)?
>>>>>
>>>>> For the prefix only it would probably be okay to just jump there
>>>>> if
>>>>> there is only a single match. I've seen cases where there is the
>>>>> same
>>>>> match for 3 entries (d - default clock task, i-interrupted task,
>>>>> and
>>>>> c-current task (or [1] current task if you are not clocking now
>>>>> but
>>>>> that
>>>>> never happens for me) I guess we could ignore the current,
>>>>> default,
>>>>> and
>>>>> interrupted tasks and only consider what is in the recent list.
>>>>>
>>>>> I use this to change tasks I'm clocking (F11 = C-c C-x C-j). I
>>>>> occasionally use it with the prefix to jump to a task I was
>>>>> recently
>>>>> clocking. I don't think my list is ever empty since I save it
>>>>> between
>>>>> Emacs restarts and my org-clock-history is set at 35.
>>>>>
>>>>> I do sometimes use 'q' to bail out of the list without doing
>>>>> anything
>>>>> (since 'q' is never a valid selection key but I should probably
>>>>> just
>>>>> use
>>>>> C-g instead) -- I go to clock something else in and then change my
>>>>> mind
>>>>> and find a new task to clock in elsewhere.
>>>>>
>>>>> I would not want the default behaviour to change if you are
>>>>> selecting a
>>>>> task to clock. I'm okay with directly jumping for the prefix only
>>>>> case.
>>>>>
>>>>> -Bernt
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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-04-22 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 12:55 C-u C-c C-x C-j to directly jump to the task with there is just one? Bastien
2009-04-21 13:33 ` Bernt Hansen
2009-04-21 16:16 ` Carsten Dominik
2009-04-21 17:22 ` Bernt Hansen
2009-04-21 18:34 ` Carsten Dominik
2009-04-21 18:38 ` Bernt Hansen
2009-04-22 4:19 ` 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=E0FF9973-ABEE-475D-B445-E97C4E6F4249@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bastienguerry@googlemail.com \
--cc=bernt@norang.ca \
--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).