From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: fix notmuch-show-update-tags to support duplicate files
Date: Sun, 06 Nov 2022 16:08:44 +0200 [thread overview]
Message-ID: <y38m6ja.737nfk-too@iki.fi> (raw)
In-Reply-To: <874jvdxplq.fsf@tethera.net>
On Sat, Nov 05 2022, David Bremner wrote:
> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>
>> Is this getting too complex (well, we may have other stuff with
>> similar complexity there ;/) ?
>>
>> Is there any better solutions ?
>
> I want to try redrawing the whole headerline. It should be more robust
> against headerline format changes, but replacing the headerline has its
> own complexities. I guess once I get something working, we can compare.
I agree -- there should be one (1) function that takes care of drawing
the headerline. this could get ouf-of-control easier when done different
ways in places far, far away...
now that I think of it, narrowing may not bring any advantage, but function
which writes headerline to current (point) -- when doing initial drawing
nothing has to be done beforehand, in case of updating, first delete line
and then redraw...
Tomi
next prev parent reply other threads:[~2022-11-06 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 21:26 [PATCH] emacs: fix notmuch-show-update-tags to support duplicate files Tomi Ollila
2022-11-05 17:45 ` David Bremner
2022-11-06 14:08 ` Tomi Ollila [this message]
2022-11-11 21:48 ` [PATCH 1/3] emacs/show: use plist to pass message info to n-s-insert-headerline David Bremner
2022-11-11 21:48 ` [PATCH 2/3] emacs/show: add optional orig-tags argument to n-s-i-headerline David Bremner
2022-11-11 21:48 ` [PATCH 3/3] emacs/show: use n-s-i-headerline to update tags David Bremner
2022-11-13 18:11 ` Tomi Ollila
2022-11-15 11:59 ` David Bremner
2022-11-15 14:01 ` Tomi Ollila
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=y38m6ja.737nfk-too@iki.fi \
--to=tomi.ollila@iki.fi \
--cc=david@tethera.net \
--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).