From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [BUG] org-clock-in menu scrolls off the top of the window
Date: Tue, 09 Apr 2013 09:36:31 +0200 [thread overview]
Message-ID: <861uak88ao.fsf@somewhere.org> (raw)
In-Reply-To: 8738v0h9fw.fsf@norang.ca
Hi Bernt Hansen,
Bernt Hansen wrote:
> "Sebastien Vauban" writes:
>> Bernt Hansen wrote:
>>> Another change I've noticed in master is the display of the clocking
>>> task menu when doing
>>>
>>> C-u M-x org-clock-in
>>>
>>> I've reduced my clocking menu items a bit due to screen size changes and
>>> not being able to see the items that scroll off the top of the screen
>>> (normally the most recent items are the ones I'm looking for but on
>>> small screens the menu scrolls up and I can't see the recent items).
>>>
>>> My current setting is (setq org-clock-history-length 23)
>>>
>>> My menu for clock-in tasks currently runs 1-9,A-N and starts with the
>>> "Current Clocking Task" on line 1. I have a widescreen monitor in
>>> windows and the bottom half of the menu is blank when the screen splits
>>> horizontally to display the clock in menu -- it seems to be centered
>>> near the last item in the list but this scrolls the default and
>>> interrupted clocking task entries off the top of the screen.
>>>
>>> There is no way to scroll this menu that I am aware of.
>>>
>>> The buffer *Clock Task Select* has
>>>
>>> ,----
>>> | Default Task
>>> | [d] Organize Organization
>>> | The task interrupted by starting the last one
>>> | [i] Organize Organization
>>> | Current Clocking Task
>>> | [c] SomeProject TODO SomeTask
>>> | Recent Tasks
>>> | [1] SomeProject TODO SomeTask
>>> | [2] Organize Organization
>>> | [3] refile TODO foo
>>> | ...
>>> | [N] refile SomeOtherRefileTask
>>> `----
>>>
>>> but it scrolls with C-u M-x org-clock-in so it looks like this
>>>
>>> ,----
>>> | Current Clocking Task
>>> | [c] SomeProject TODO SomeTask
>>> | Recent Tasks
>>> | [1] SomeProject TODO SomeTask
>>> | [2] Organize Organization
>>> | [3] refile TODO foo
>>> | ...
>>> | [N] refile SomeOtherRefileTask
>>> | ... <lots of blank lines>
>>> `----
>>
>> As your data is not that true, I can't tell from what you show, but another
>> thing that I've seen (in my config) is that many tasks are duplicated, hence
>> the list is much longer that needed.
>>
>> Do you see that as well in your case?
>>
>> For example, it seems to me that (in the second screen) item 1 is redundant
>> with item c. In the first screen, items d, i and 2 seem redundant, while items
>> c and 1 seem also redundant.
>
> The data has been modified but the duplication isn't new. The only tasks I
> renamed were 'SomeTask' and 'SomeOtherRefileTask'. I used capture to create
> foo as a temporary task (which I subsequently deleted). The actual task list
> came from projects at my work.
>
> Duplicated tasks in my displayed menu are really duplicated and as far as I
> know that behaviour hasn't changed.
>
> If there is a default, and current task (all the same) then [d], [c], and
> [1] will all be identical. The default task is only displayed when a default
> clocking task is identified (which is always for me). [c] may not be that
> useful to display since we can just quit and leave the clock alone.
>
> Personally I like the duplication in the history list (it's a true view of
> what was clocked in recently)
Personally, I would find it clearer to see every task at most once, be it as
"default", "interrupted" or in the list. So, the interrupted task wouldn't be
duplicated in the list. But I can understand that this is a question of taste.
Something which is not a question of taste, IMHO, is that items are sometimes
duplicated within the 1..N list: I have, for example,
--8<---------------cut here---------------start------------->8---
Recent Tasks
[1] Read emails
[2] Organize work
[3] Organize work
[4] Prepare meeting
--8<---------------cut here---------------end--------------->8---
Items 2 and 3 are the same one -- I don't have "Organize work" duplicated
within my agenda files. I don't understand why it's duped in there. Ever
observed this as well?
> The main thing I'm reporting is all the whitespace now at the bottom of the
> screen since the list is artificially scrolled up. I used to be able to
> determine exactly what fit in the list so I set my history length
> appropriately.
I know that item duplication is a side-question, but it does consume real
screen estate...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-04-09 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 18:40 [BUG] org-clock-in menu scrolls off the top of the window Bernt Hansen
2013-04-07 19:38 ` Sebastien Vauban
2013-04-08 23:46 ` Bernt Hansen
2013-04-09 7:36 ` Sebastien Vauban [this message]
2013-04-12 11:41 ` Bernt Hansen
2013-04-13 8:24 ` Bastien
2013-04-09 17:41 ` Bastien
2013-04-11 21:06 ` Bernt Hansen
2013-04-12 15:57 ` Bastien
2013-04-14 11:32 ` Bernt Hansen
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=861uak88ao.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).