From: sl@9front.org
To: mayuresh@kathe.in, 9fans@9fans.net, sl@9front.org
Subject: Re: [9fans] upas : without acme : possible?
Date: Thu, 29 Nov 2018 23:40:11 -0500 [thread overview]
Message-ID: <9CF7937042B138BD017824241CCF9B30@ewsd.inri.net> (raw)
In-Reply-To: b695424f28532ca7d5565b80553a67ec@kathe.in
It's not clear why you think the interface provided by upasfs(4) is captive, or why you insist acme needs to be involved at all. I'm writing this message with nedmail/marshal, connected to Plan 9 in a plain SSH terminal session -> OpenBSD -> drawterm -G. No GUI or terminal frills or frippery is involved.
sl
next reply other threads:[~2018-11-30 4:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 4:40 sl [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-30 14:22 sl
[not found] <3B648B1B56B7F372B8E8ADAE7AE3D0B3@ewsd.inri.net>
2018-11-30 4:52 ` Mayuresh Kathe
2018-11-30 3:32 sl
2018-11-30 3:53 ` Mayuresh Kathe
2018-11-29 13:44 Mayuresh Kathe
2018-11-29 14:13 ` Alexander Sychev
2018-11-29 14:34 ` Dan Cross
2018-11-29 14:57 ` Mayuresh Kathe
2018-11-29 15:58 ` Kurt H Maier
2018-11-29 16:50 ` erik quanstrom
2018-11-29 19:00 ` Steve Simon
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=9CF7937042B138BD017824241CCF9B30@ewsd.inri.net \
--to=sl@9front.org \
--cc=9fans@9fans.net \
--cc=mayuresh@kathe.in \
/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).