From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] remote access to fossil console
Date: Tue, 2 Dec 2003 20:47:35 -0500 [thread overview]
Message-ID: <200312030147.hB31lZl23302@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Tue, 02 Dec 2003 22:22:34 +0100." <200312022122.hB2LMYF23396@zamenhof.cs.utwente.nl>
Axel Belinfante <Axel.Belinfante@cs.utwente.nl> writes:
>
> at the university I could use your mailing trick; I was also thinking
> about fossil use at home where I have to (want to) be kind of self-supportive
> (hence the ideas I sketched in my orevious post)
> I suppose nemo's printer approach makes sense there.
>
If you have a 9fat, I don't see why you couldn't snarf the latest score
and dump it into a file with a known name there. /n/9fat/newestsc.ore
or something.
- Dan C.
next prev parent reply other threads:[~2003-12-03 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 19:18 jmk
2003-12-02 20:51 ` Axel Belinfante
2003-12-02 21:06 ` mirtchov
2003-12-02 21:22 ` Axel Belinfante
2003-12-02 20:55 ` Russ Cox
2003-12-03 1:47 ` Dan Cross [this message]
2003-12-02 23:27 ` Geoff Collyer
2003-12-03 2:32 ` boyd, rounin
2003-12-02 21:30 David Presotto
2003-12-03 2:37 ` boyd, rounin
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=200312030147.hB31lZl23302@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/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).