From mboxrd@z Thu Jan 1 00:00:00 1970 From: Noah Slater Subject: Re: Problem with org-clock-display Date: Thu, 17 Apr 2014 13:53:33 +0200 Message-ID: References: <874n1s74bm.fsf@bzg.ath.cx> <8761m82orj.fsf@bzg.ath.cx> <87eh0wqiyt.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0158bbdcc03db704f73baeca Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41520) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Waksw-00085d-Ht for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 07:53:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Waksp-0005tL-OV for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 07:53:42 -0400 Received: from mail-yh0-x229.google.com ([2607:f8b0:4002:c01::229]:35908) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Waksp-0005t8-IJ for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 07:53:35 -0400 Received: by mail-yh0-f41.google.com with SMTP id i57so237233yha.28 for ; Thu, 17 Apr 2014 04:53:35 -0700 (PDT) In-Reply-To: <87eh0wqiyt.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org --089e0158bbdcc03db704f73baeca Content-Type: text/plain; charset=ISO-8859-1 Ah, sorry. So what I mean is, if you have a long list of lines like this: * A 5:10 ... * B 8:40 ... * C 2:50 ... Then it is a bit tricky to see what time is clocked for, say, B. It is easy above because there are only three nodes. But if you have 20 nodes, it gets tricky. So my thinking was that previously the "...................." bits helped to guide your eye across. But I am not so sure, you know. Because if you have 20 of those in a row, it's not really helping much. * A ........................................................... 5:10 ... * B ........................................................... 8:40 ... * C ........................................................... 2:50 ... Again, this is easy when you just have three. But you have 20 in a row, it's hard to follow. So my idea was to use something like ln-line (thanks!) to show you where you are. Then I can just navigate around the nodes, and it is obvious what time matches up to what node. Bit I'm wondering if you have any better ideas. Or, given the readability problems, it makes sense to display the "..............." bits by default. (Though I am not sure that they are actually much more readable.) This is one of the reasons I suggested an alternative approach: do not align the times to the right at all, just stick them right next to the node titles, like so: * Apple 5:10 ... * Bananas 8:40 ... * Carrots 2:50 ... As you can see, the times wont line up then, but matching them to the node titles is easy. On 17 April 2014 13:43, Bastien wrote: > Noah Slater writes: > > > Now I need to solve the problem of being able to tie the node to the > > clock-display. (If there's a big list, then it's hard to visually > > match them.) > > I'm not really sure what you mean by "tie the node to the clock-display". > > > I think I recall a minor mode that highlighted the current line your > > point is on. > > M-x hl-line-mode RET > > > That would fix it. But then, it would be nice if that > > worked with my mouse too. > > > > Any ideas? > > > > I think unless there's an obvious way to solve this, that it might > > actually make sense to have the "......." bit visible by default, and > > provide an option to turn it off for people who don't mind the way it > > looks. > > > > Thoughts? > > The dots have been removed, so really not sure what we are talking > about :) But if you want to make the folding three dots "..." be > displayed differently, that's hard -- and I don't think it's worth > the time. > > -- > Bastien > --089e0158bbdcc03db704f73baeca Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Ah, sorry.

So what I mean is, if you ha= ve a long list of lines like this:

* A =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A05:10 ...
* B =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A08:40 ...
* C =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02:50 ...
<= br>
Then it is a bit tricky to see what time is clocked for, say,= B.

It is easy above because there are only three = nodes. But if you have 20 nodes, it gets tricky.

So my thinking was that previously the "..........= .........." bits helped to guide your eye across. But I am not so sure= , you know. Because if you have 20 of those in a row, it's not really h= elping much.

* A ...................................................= ........ 5:10 ...
* B ...........................................= ................ 8:40 ...
* C ...............................= ............................ 2:50 ...

Again, this is easy when you just have three. But= you have 20 in a row, it's hard to follow.

So= my idea was to use something like ln-line (thanks!) to show you where you = are. Then I can just navigate around the nodes, and it is obvious what time= matches up to what node.

Bit I'm wondering if you have any better ideas.

Or, given the readability problems, it makes sense to= display the "..............." bits by default. (Though I am not = sure that they are actually much more readable.)

This is one of the reasons I suggested an alternative a= pproach: do not align the times to the right at all, just stick them right = next to the node titles, like so:

* Apple 5:10 ...=
* Bananas 8:40 ...
* Carrots 2:50 ...

As you can see, the times wont line up then, but matching them to the no= de titles is easy.


On 17 April 2014 13:43, Bastien <bzg@gnu.org> wrote:
Noah Slater <nsl= ater@tumbolia.org> writes:

> Now I need to solve the problem of being able to tie the node to the > clock-display. (If there's a big list, then it's hard to visua= lly
> match them.)

I'm not really sure what you mean by "tie the node to the cl= ock-display".

> I think I recall a minor mode that highlighted the current line your > point is on.

M-x hl-line-mode RET

> That would fix it. But then, it would be nice if that
> worked with my mouse too.
>
> Any ideas?
>
> I think unless there's an obvious way to solve this, that it might=
> actually make sense to have the "......." bit visible by def= ault, and
> provide an option to turn it off for people who don't mind the way= it
> looks.
>
> Thoughts?

The dots have been removed, so really not sure what we are talking about :) =A0But if you want to make the folding three dots "..." = be
displayed differently, that's hard -- and I don't think it's wo= rth
the time.

--
=A0Bastien

--089e0158bbdcc03db704f73baeca--