From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Reminder: IWP9 papers are due on the 30th
Date: Tue, 06 Feb 2024 12:18:11 -0500 [thread overview]
Message-ID: <86A573DF1FA354B55DF2099B10C5D584@eigenstate.org> (raw)
In-Reply-To: <acbe1c37-4430-4f23-ad51-584948169f79@sciops.net>
...I forgot that I already did.
http://shithub.us/ori/Slide/HEAD/info.html
Quoth qwx@sciops.net:
> Hi all,
>
> Ori, sirjofri, imho please just post your stuff somewhere :)
> I'm personally interested in all of it regardless of whether
> or not I would end up using it, same for others I'm sure.
>
> Cheers,
> qwx
>
> Feb 4, 2024 15:49:58 ori@eigenstate.org:
>
> > I used this when presenting to the BSD user group;
> > it was quite nice.
> >
> > I also have a plan9-native version of RSC's acme
> > Slide tool, if someone is interested in that.
> >
> > Quoth phil9 <telephil9@gmail.com>:
> >> hi,
> >>
> >> I wrote a simple presentation tool last year in anticipation of IWP9
> >> so people could do their presentation directly from 9front but clearly
> >> failed to communicate about it.
> >> If there is any interest, the code is here:
> >> http://shithub.us/phil9/spit/HEAD/info.html
> >>
> >> Feel free to drop me an email if you find bugs or have any feature request.
> >>
> >> cheers,
> >> --phil
> >>
> >> On Mon, Jan 29, 2024 at 8:12 PM <ori@eigenstate.org> wrote:
> >>>
> >>> Just a reminder: Papers are due on Jan 30th,
> >>> WIPs are on Feb 12th.
> >>>
> >>> If you want to submit, but need more time, let
> >>> us know. (And thanks to those that have already
> >>> done this)
> >>>
prev parent reply other threads:[~2024-02-06 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 19:11 ori
2024-01-30 18:57 ` [9front] Update: Papers are due on Feb 12th ori
2024-02-04 14:38 ` [9front] Reminder: IWP9 papers are due on the 30th phil9
2024-02-04 14:50 ` ori
2024-02-04 17:10 ` sirjofri
2024-02-04 18:00 ` qwx
2024-02-06 17:18 ` ori [this message]
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=86A573DF1FA354B55DF2099B10C5D584@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).