From: Carsten Dominik <carsten.dominik@gmail.com>
To: Julien Danjou <julien@danjou.info>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-agenda: rewrite mode-line
Date: Mon, 13 Dec 2010 15:49:56 +0100 [thread overview]
Message-ID: <DCA72AFA-A8D8-4A5F-B09A-AA4A75D17EC0@gmail.com> (raw)
In-Reply-To: <87ipyyizxw.fsf@keller.adm.naquadah.org>
XEmacs users, please read this.
On Dec 12, 2010, at 7:55 PM, Julien Danjou wrote:
> On Sun, Dec 12 2010, Carsten Dominik wrote:
>
>> what is the purpose of this patch, why is it needed?
>> I generally will not accept patches that lack this information.
>
> Sorry, it seems quite obvious to me.
Hi Julien,
even if it is more or less obvious on closer
study, I am trying to create a useful history of
the project by providing additional information
at commit time. And knowing the intend of the author
speeds up classifying and judging the patch very much.
I have not spent some 20 Minutes looking at it and
writing to you and looking at it again....
The patch looks good to me, I am planning to accept
it after studying it closer.
Does anyone know if :eval in the mode line specification
is XEmacs compatible?
- Carsten
>
> The purpose is to stop trying to guess where to call the function to
> `org-agenda-set-mode-name' whenever one of the value change used in
> that
> function changes.
>
> This is probably one of the reason why :eval property has been
> invented,
> I guess. :-)
>
> --
> Julien Danjou
> ❱ http://julien.danjou.info
- Carsten
next prev parent reply other threads:[~2010-12-13 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 15:41 [PATCH] org-agenda: rewrite mode-line Julien Danjou
2010-12-12 8:32 ` Carsten Dominik
2010-12-12 18:55 ` Julien Danjou
2010-12-13 14:49 ` Carsten Dominik [this message]
2010-12-21 7:36 ` Carsten Dominik
2010-12-21 8:53 ` Michael Sperber
2011-01-21 9:25 ` Carsten Dominik
2011-03-04 22:09 ` Bastien
2011-03-05 10:12 ` Michael Sperber
2011-03-05 10:50 ` Bastien
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=DCA72AFA-A8D8-4A5F-B09A-AA4A75D17EC0@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=julien@danjou.info \
/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).