From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Gmail vs upas
Date: Tue, 3 Dec 2019 10:52:00 +0000 [thread overview]
Message-ID: <992eb5f88d4429f95ed2dede94a3a5b7@hamnavoe.com> (raw)
In-Reply-To: <823EC81AB1DB4BFEEE9AA1FEC417CF8A@eigenstate.org>
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?
next prev parent reply other threads:[~2019-12-03 10:52 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 [this message]
2019-12-04 20:50 ` ori
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=992eb5f88d4429f95ed2dede94a3a5b7@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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).