From: Damien Cassou <damien.cassou@gmail.com>
To: Mark Walters <markwalters1009@gmail.com>
Cc: notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: [PATCH v2] emacs: display tags in notmuch-show with links
Date: Thu, 15 Nov 2012 16:42:12 +0100 [thread overview]
Message-ID: <CA+y5ggj8QFGuxQpFXfnf_sc5hwLYOT3zoXJ6tm0zvpF45YLR2A@mail.gmail.com> (raw)
In-Reply-To: <878va4xson.fsf@qmul.ac.uk>
On Wed, Nov 14, 2012 at 1:41 PM, Mark Walters <markwalters1009@gmail.com> wrote:
> On the loading library issues I defer to Adam and Tomi.
I think they are right and I will try to make my code do something
good by default and do something better if header-button is detected.
> I do have a couple of comments on the current version
> though. First the patch is very big. I would prefer it split into
> several pieces
do you want me to send totally separate emails or do you want me to
send 1 discussion of multiple emails (with 0/4, 1/4, 2/4,...) ?
> something like:
>
> 1) Add tags to the headerline but not clickable
makes perfect sense
> 2) Add the header-button library if appropriate
I will try the other approach of not embedding the library in notmuch
> 3) Add notmuch-tagger and change headerline to buttonize the tags
makes perfect sense. The patch will buttonize the links if
header-button is present and nothing otherwise.
> 4) Add the tests.
ok
+ 5) Add buttons to tags in the body
>> +(defun notmuch-tagger-present-tags (tags &optional headerline)
>> + "Return a property list which nicely presents all TAGS.
>> +
>> +If HEADERLINE is non-nil the returned list will be ready for
>> +inclusion in the buffer's header-line. HEADERLINE must be nil in
>> +all other cases."
>
> I find it odd to say what it returns if HEADERLINE is non-nil and then
> say otherwise HEADERLINE must be nil. Could you say what it returns in
> the nil case? Something along them lines of
>
> "if HEADERLINE is non-nil the returned will be ready for inclusion in
> the buffer's header-line (i.e., will use header-buttons if
> available). Otherwise it returns a list?? ready for inclusion in a
> buffer."
thank you for the comment, I will fix it and propose new patches
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
next prev parent reply other threads:[~2012-11-15 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 16:41 [PATCH v2] emacs: display tags in notmuch-show with links Damien Cassou
2012-11-14 2:03 ` Ethan Glasser-Camp
2012-11-15 15:09 ` Damien Cassou
2012-11-14 12:41 ` Mark Walters
2012-11-15 15:42 ` Damien Cassou [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-18 19:18 Damien Cassou
2012-11-18 22:59 ` Ethan Glasser-Camp
2012-11-19 0:10 ` Aaron Ecay
2012-11-20 4:23 ` Austin Clements
2012-11-20 4:50 ` Ethan
2012-11-22 18:11 ` Damien Cassou
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+y5ggj8QFGuxQpFXfnf_sc5hwLYOT3zoXJ6tm0zvpF45YLR2A@mail.gmail.com \
--to=damien.cassou@gmail.com \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).