From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Show/edit acme snarf buffer
Date: Fri, 29 Jun 2012 14:55:31 +0100 [thread overview]
Message-ID: <20120629145531.484fd284@vardo.ethans.dre.am> (raw)
In-Reply-To: <f1762d99e2a44b76cd1b0f80b3a4c2ed@brasstown.quanstro.net>
On Fri, 29 Jun 2012 09:15:01 -0400
erik quanstrom <quanstro@quanstro.net> wrote:
> > > Using either/both acme under Plan 9 and/or Mac OS X via plan9port, is
> > > there a "file" that can be opened in acme that displays the current
> > > contents of the acme snarf buffer? If so, is there a way to have that
> > > window automatically update when the snarf buffer changes? Basically,
> > > I'm wondering if there is a way to duplicate the functionality that
> > > was generally present in old Macintosh text editors under the show
> > > clipboard command. Finally, if this functionality is available, would
> > > it be possible that by editing the snarf buffer window to edit the
> > > contents of the snarf buffer itself (as was possible in Nisus's old
> > > editor QUED/M)?
> >
> > isn't there a snarf file in the filesystem served bu rio?
>
> it doesn't have the properties the op requested. a read at eof doesn't
> hang until the contents of the file have changed.
If manual update is acceptable he could add "Get" to the tag line.
I guess a simple polling program could be written for acme, but many
uses of the selection while you're editing the text would end up
overwriting your edit.
next prev parent reply other threads:[~2012-06-29 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 9:13 Brian Vito
2012-06-25 9:58 ` Justin Bedo
2012-06-25 10:24 ` Richard Miller
2012-06-29 8:54 ` Stephen Wiley
[not found] ` <392578302362604520.663215theswiley-me.com@reader443.eternal-sept>
2012-06-29 13:15 ` erik quanstrom
2012-06-29 13:55 ` Ethan Grammatikidis [this message]
2012-07-12 8:52 ` Brian Vito
2012-07-12 13:16 ` andrey mirtchovski
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=20120629145531.484fd284@vardo.ethans.dre.am \
--to=eekee57@fastmail.fm \
--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).