From: ori@eigenstate.org
To: 9fans@hamnavoe.com, 9fans@9fans.net
Subject: Re: [9fans] Gmail vs upas
Date: Wed, 4 Dec 2019 12:50:52 -0800 [thread overview]
Message-ID: <6A11E9B13276F24F9AAEB2CA6F1BF7FF@eigenstate.org> (raw)
In-Reply-To: <992eb5f88d4429f95ed2dede94a3a5b7@hamnavoe.com>
> On the tangential subject of acme mail, I have a very infrequent bug
> where the header of a newly arrived message pops up in the position
> where the /mail/fs/mbox window used to be, some time after the mbox
> window has been adjusted by another window opening. Does anyone else
> see this? Is there a known patch on some fork which fixes it?
I haven't seen this particular redraw artifact, but I've seen other
smaller ones. Is there anything in particular that you can do to
reproduce it?
I just took a quick poke through the 9front and plan9port changes, and
I see a couple of things that should probably be cherry-picked[1], but
not anything related to artifacts.
(Also, looks like git9's git/log's filtering by path is busted.
TODO added.)
[1] some obvious bugfixes on plan9port, which should apply to 9legacy.
- 7ca1c90109e17dced4b38fbaadea9d2cf39871b7 (fix memory leak)
- 219cf22d6863a21a7378fc5481bb05bbb6edd2dc (large file fixes)
- edfe3c016fe6ef10c55f7a17aab668214ec21efc (sam issue, free str instead of free)
- 76b9347a5fa3a0970527c6ee1b97ef1c714f636b (avoid div-by-0)
- a82a8b6368274d77d42f526e379b74e79c137e26 (apply +/- only once)
- dfac95269ab7944810043fb9e78557b06ed3a767 (update tag after control event)
- fff818fe878ca5edfbac85b15e77ada2acb8ea0f (avoid inverted textselect range)
Let me know if there are others I missed.
next prev parent reply other threads:[~2019-12-04 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 15:39 Steven Stallion
2019-11-28 15:55 ` [9fans] " Steve Simon
2019-11-28 16:00 ` David du Colombier
2019-11-28 17:13 ` Steven Stallion
2019-11-28 17:37 ` kvik
2019-11-28 17:44 ` Steven Stallion
2019-11-28 18:07 ` kvik
2019-11-28 18:59 ` David du Colombier
2019-11-28 20:28 ` Steven Stallion
2019-12-02 23:27 ` ori
2019-12-03 10:52 ` Richard Miller
2019-12-04 20:50 ` ori [this message]
2019-12-04 23:02 ` Richard Miller
2019-12-03 13:54 ` Anthony Martin
2019-11-28 17:33 ` kvik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6A11E9B13276F24F9AAEB2CA6F1BF7FF@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
--cc=9fans@hamnavoe.com \
/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.
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 NNTP newsgroup(s).