From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Nail: embrace, extend, extinguish
Date: Tue, 29 Dec 2020 07:55:25 -0800 [thread overview]
Message-ID: <1F6D86AF7FEFD3EC78F1AEBBB88368C1@eigenstate.org> (raw)
In-Reply-To: <5AC33AE9143B9556254F88884E7B46FF@typed-hole.org>
Quoth julien@typed-hole.org:
> I've been using Nail daily since a few weeks and so far I can say it
> works very well.
> I have a weird behaviour though, selecting a mail in the list and
> clicking Delmesg duplicates it (in the list) with the new one marked
> for deletion.
>
> Looks like:
>
> 83/ ...
> 82/ Mail title <some@email.com>
> 82/ ∉ Mail title <some@email.com>
> 81/ ...
>
> Putting the changes only removes the marked one and the remaining one
> can't be opened.
>
> --
> julienxx
>
Does this happen consistently? This is what happens when
mesglineno() computes the incorrect line number and replaces
the wrong line.
I'm guessing that there's a message somewhere between the most
recnet message and message 82 that's somehow incrementing the
line count by 2.
would you be able to send me a dump of the mailbox flags the
next time you see this happen?
This is how I do it:
% mk mbox.acid
% acid -l mbox.acid $nailpid
acid; defn dumpmesg(n){
complex Mbox mbox;
local m, p;
p = mbox.mesg;
loop 0,n do{
m = *p;
complex Mesg m;
print("=== ", *p, " ", *(m.name\s), " flags=", m.flags\x, " state=", m.state\x, " ", *(m.subject\s), "\n");
p = p + 8;
}
}
acid; dumpmesg(100)
next prev parent reply other threads:[~2020-12-29 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 3:42 ori
2020-12-29 10:45 ` julien
2020-12-29 15:55 ` ori [this message]
2020-12-30 14:03 ` Shawn Nock
2020-12-30 17:20 ` ori
2020-12-31 4:49 ` ori
2020-12-29 10:46 ` Daniel Moch
2020-12-29 11:17 ` telephil9
2020-12-29 21:09 ` Lyndon Nerenberg
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=1F6D86AF7FEFD3EC78F1AEBBB88368C1@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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.
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).