From: nemo@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] creating new files in acme
Date: Wed, 23 May 2001 08:17:09 +0200 [thread overview]
Message-ID: <20010523061010.5BDCD199C0@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 94 bytes --]
Appart from using B, you could start acme in /very/long
and then use relative path/names.
[-- Attachment #2: Type: message/rfc822, Size: 2009 bytes --]
From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] creating new files in acme
Date: Tue, 22 May 2001 17:26:28 -0700
Message-ID: <200105230026.f4N0QSc05792@ducky.net>
I am finding it very inconvenient to create new files in acme.
"New" creates an unnamed files. A certain project at work
requires some /very/long/path/names. It is annoying to have
to paste /very/long/path/name into the tag of each created
new file. It would be nice if New would somehow inherit the
directory from the tag of the context from which it is
executed, and create a tag like /very/long/path/name/NewFile
for the new file.
My workaround: in a "win" window, type "touch filename",
then right-click filename to bring the new empty file in.
But this feels crufty.
next reply other threads:[~2001-05-23 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 6:17 nemo [this message]
2001-05-23 20:41 ` Chris Locke
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 7:15 forsyth
2001-05-23 0:41 rob pike
2001-05-23 0:26 Mike Haertel
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=20010523061010.5BDCD199C0@mail.cse.psu.edu \
--to=nemo@gsyc.escet.urjc.es \
--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).