From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Long file names
Date: Mon, 4 Nov 2002 18:14:41 +0000 [thread overview]
Message-ID: <2de58957f267de397b24fbc068dbc8e1@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 63 bytes --]
1. see lnfs(4)
2. see rc(1), particularly `.' (as a command)
[-- Attachment #2: Type: message/rfc822, Size: 1521 bytes --]
From: "athiele@charter.net"@cse.psu.edu
To: 9fans@cse.psu.edu
Subject: [9fans] Long file names
Date: Mon, 4 Nov 2002 13:13:43 -0500
Message-ID: <679fae6627e8b7863188410ec5747eff@charter.net>
I saw a post not too long ago
about working around long file paths/names
does anyone remember how to do it ?
Also is there a "source" type command
so I can reread my profile file ?
Adrian
next reply other threads:[~2002-11-04 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 18:14 Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 18:13 athiele@charter.net
2002-11-04 14:41 Skip Tavakkolian
2002-11-04 18:35 ` Adrian
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=2de58957f267de397b24fbc068dbc8e1@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).