From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] rewrite gateway
Date: Sat, 29 Jan 2022 15:40:01 -0800 [thread overview]
Message-ID: <A608062BE5092F1CC9F12736D9C70A02@gmail.com> (raw)
In-Reply-To: <5E2CFE7F0D34E3CD03F6902FB308D936@felloff.net>
Quoth cinap_lenrek@felloff.net:
> it looks to me like the arguments of that ioproc are corrupted.
>
> i'v taken a look at acme mail, and iowrite is only used
> as a callback for a Bio buffer (procwr), which should have
> a maximum buffer capacity of 8K + UTFman+1, so having
> ~800k write size should be impossible.
>
> also note how the file descriptor is -1?
>
> very odd.
>
> you can maybe put a debug print in /sys/src/cmd/upas/Mail/win.c:^procwr
>
> i'm not acme user, lemme see if i can reproduce it on a 386 build.
>
> --
> cinap
Could you give an example of how to use mail command line. The manpage still confuses me.
When I select the number of the message 3: r
to reply it changes the color of the sreen and throws me into marshal mode. Ctrl-D doesn't
exctly work for me i'm using an Apple Keyboard so it seems fn+ Delete breaks me out.
After which I"m not sure what command to run to send mail. It appears easy to delete a message
but replying proves confusing. y key gives me a command error. So I'm obviously doing
something wrong. Also not sure of the args to use. Seems acme Mail is the lazy way that I
rely on at the moment.
next prev parent reply other threads:[~2022-01-30 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 0:52 thinktankworkspaces
2022-01-28 19:07 ` cinap_lenrek
2022-01-28 21:10 ` thinktankworkspaces
2022-01-28 21:22 ` ori
2022-01-28 23:04 ` thinktankworkspaces
2022-01-29 13:14 ` hiro
2022-01-29 14:18 ` cinap_lenrek
2022-01-29 20:50 ` cinap_lenrek
2022-01-29 23:29 ` thinktankworkspaces
2022-01-29 23:40 ` thinktankworkspaces [this message]
2022-01-30 12:14 ` cinap_lenrek
2022-01-30 16:16 ` ori
2022-01-30 23:01 ` thinktankworkspaces
2022-01-29 14:29 ` cinap_lenrek
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=A608062BE5092F1CC9F12736D9C70A02@gmail.com \
--to=thinktankworkspaces@gmail.com \
--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).