From: Noah Evans <noah.evans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] detecting drawterm
Date: Fri, 31 Jul 2009 12:54:04 +0200 [thread overview]
Message-ID: <56a297000907310354k2a723447y665aa77d83721319@mail.gmail.com> (raw)
In-Reply-To: <df49a7370907310331g1d963e9xae025c36ca209e7b@mail.gmail.com>
/mnt/term/dev/hostdomain?
AFAIK it's always drawterm.net.
On Fri, Jul 31, 2009 at 12:31 PM, roger peppe<rogpeppe@gmail.com> wrote:
> i'm probably being stupid here, but what's a good robust way
> of detecting in $home/lib/profile that the remote connection
> is from drawterm, so that i can start rio etc?
>
> currently the best i've got is to check /mnt/term/sysname,
> but that falls down the moment i connect from a different host...
>
>
prev parent reply other threads:[~2009-07-31 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 10:31 roger peppe
2009-07-31 10:48 ` Steve Simon
2009-07-31 11:04 ` roger peppe
2009-07-31 19:31 ` Skip Tavakkolian
2009-07-31 10:54 ` Noah Evans [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=56a297000907310354k2a723447y665aa77d83721319@mail.gmail.com \
--to=noah.evans@gmail.com \
--cc=9fans@9fans.net \
/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).