From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] acme Put doesn't save
Date: Wed, 4 Mar 2009 09:34:26 -0500 [thread overview]
Message-ID: <2772b418c31186cdd12c944173fda946@quanstro.net> (raw)
In-Reply-To: <138575260903040610u4950702es60d0e5c0f78503f2@mail.gmail.com>
On Wed Mar 4 09:12:08 EST 2009, uair00@gmail.com wrote:
> While learning some of acme's basic commands I was also shocked by
> this, and I agree with Ruda that executing a Put with a non-existent
> file (e.g. '/home/ruda/a' ;-) should save the contents of the window
> in that file.
this isn't true. if you click on New and then type something
for a filename you will notice that the tag line box becomes
filled and then click on Put, the file *will* be saved, even if the
file does not exist.
if on the other hand you try to modify the name of a directory
listing frame, the tag line box is not filled. this is a hint
that you're doing something wrong. also there is no Put option.
this is a bigger hint that you're doing something wrong.
the reason that directories behave differently is that in acme
programs are allowed to take over a window. while the directory
listing is built in, it operates on the same principle, and it does
not make sense to write a directory through acme's interface.
- erik
next prev parent reply other threads:[~2009-03-04 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 13:09 erik quanstrom
2009-03-04 14:10 ` hugo rivera
2009-03-04 14:34 ` erik quanstrom [this message]
2009-03-04 14:57 ` hugo rivera
2009-03-04 15:18 ` roger peppe
2009-03-06 10:48 ` Rudolf Sykora
2009-03-06 11:12 ` Robert Raschke
2009-03-08 0:57 ` yy
2009-03-08 1:02 ` yy
2009-03-09 8:05 ` Rudolf Sykora
2009-03-09 12:22 ` Rudolf Sykora
2009-03-09 13:23 ` Rudolf Sykora
2009-03-04 15:19 ` Rudolf Sykora
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 11:44 Rudolf Sykora
2009-03-04 12:21 ` yy
2009-03-04 12:32 ` Rudolf Sykora
2009-03-04 13:25 ` yy
2009-03-04 12:28 ` roger peppe
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=2772b418c31186cdd12c944173fda946@quanstro.net \
--to=quanstro@quanstro.net \
--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).