From: David Hogan dhog@plan9.cs.su.oz.au
Subject: remote device access
Date: Sat, 29 Apr 1995 02:54:22 -0400 [thread overview]
Message-ID: <19950429065422.HeMK2CCcCq_Qtz2oyMzq5EqiIkFzmP6F6lLEmCUzZaY@z> (raw)
>>i prefer the notation to be distinct. when what's going on is
>>fundamentally nasty, it is polite to say so; hence #c.
>
>My concern is that it pretends to be in file system space, while it
>really isn't (you can't ls/cp/rm/etc. it).
I dunno, ls '#c' works for me!
>E.g. in Plan9, I can't have a file
>called #c (there goes emacs ... hm ... :-).
Well, actually you can, but you have to be careful how you reference it. ie,
echo foo >'./#c'
next reply other threads:[~1995-04-29 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-29 6:54 David [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-29 6:51 David
1995-04-29 6:09 serge
1995-04-28 21:39 serge
1995-04-28 16:04 rob
1995-04-28 8:26 forsyth
1995-04-28 6:52 Boyd
1995-04-28 0:18 serge
1995-04-27 8:29 forsyth
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=19950429065422.HeMK2CCcCq_Qtz2oyMzq5EqiIkFzmP6F6lLEmCUzZaY@z \
--to=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).