From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
Subject: Re: [PATCH] Add a different prefix for past deadlines in the agenda view
Date: Thu, 28 Feb 2013 10:21:29 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
> "Sebastien Vauban" writes:
>> Though, one question: why did you change the spacing (and, in fact, the width)
>> of the leaders?
>> -(defcustom org-agenda-scheduled-leaders '("Scheduled: " "Sched.%2dx: ")
>> +(defcustom org-agenda-scheduled-leaders '(" Scheduled: " "Sched.%3dx: ")
>> "Text preceding scheduled items in the agenda view.
>> -(defcustom org-agenda-deadline-leaders '("Deadline: " "In %3d d.: ")
>> +(defcustom org-agenda-deadline-leaders '(" Deadline: " " In %3d d.: " "%3d d. ago: ")
> For the change in "Scheduled:" and "Deadline:" it's because I think it's
> cleaner to align them on the right, like the "Sched." and "In %3d.:"
I don't mind, I customize them anyway ;-)
> For the change in the width (from 11 to 12), it's because I wanted to
> correctly display "%3d d. ago: ", not %2d d. ago: ", so that now any string
> with a warning delay more than 100 will be correctly displayed. Before, we
> allowed 100+ days for the future deadlines, but not for past scheduled items
> (i.e. they were not aligned properly.)
> I feel the change is not too intrusive.
I think the change of width can impact people who customize a bit the look of
their agenda, and rely upong *all* the leaders to be of width 11. That was the
motivation for my other patch, about clocking info (to make it go into a
Let's see how people react to that -- or if some are impacted.
next prev parent reply other threads:[~2013-02-28 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 21:58 [PATCH] Add a different prefix for past deadlines in the agenda view Sebastien Vauban
2013-02-04 22:45 ` Bastien
2013-02-27 13:56 ` Bastien
2013-02-28 8:17 ` Sebastien Vauban
2013-02-28 8:29 ` Bastien
2013-02-28 9:21 ` Sebastien Vauban [this message]
2013-02-28 9:29 ` Bastien
2013-03-24 22:12 ` Matt Lundin
2013-03-25 5:57 ` Bastien
2013-02-28 8:30 ` Bastien
2013-02-28 9:42 ` Sebastien Vauban
2013-02-28 9:48 ` Andreas Leha
2013-02-28 9:55 ` Sebastien Vauban
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).