9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] winclear in p9p
Date: Tue, 31 Oct 2006 10:06:02 -0800	[thread overview]
Message-ID: <19DE8459-C68C-4B7C-9686-0EA1F6005DBD@telus.net> (raw)
In-Reply-To: <88a477560610310922j6c5ed52dg6327ab6587479977@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Looking at this briefly, I discovered that the p9p version of acme  
doesn't make available body/addr/ctl/event of the current selected  
window.  So the straightforward "substitute 9p commands" fails.

What is the correct way for a script to discover the ID of the acme  
window it was run from?  I could trap the command in the plumber and  
add the id as a parameter, but that's rather intrusive.

Paul

On 31-Oct-06, at 9:22 AM, Matthias Teege wrote:

> Moin,
>
> I've found
>
> fn winclear {
> 	echo -n Edit ,d > /dev/acme/body
> 	echo -n /Edit ,d/ > /dev/acme/addr
> 	echo -n 'dot=addr' > /dev/acme/ctl
> 	cat /dev/acme/addr | awk '{printf("MX%s %s\n", $1, $2)}' > /dev/ 
> acme/event
> }
>
> in the wiki but how do I clear a win in Plan 9 ports? To be accurate I
> need to replace some text in the middle of the body and it would be
> nice, if I can avoid a tempfile.
>
> Many thanks
> Matthias

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFR5CLpJeHo/Fbu1wRAqS+AKCvwJhWvDn5Z+Yenu8NHEqv1h0WNQCeOzyC
1nvalZ6Jy7nFD3jnzAsz/BY=
=w0ot
-----END PGP SIGNATURE-----


  reply	other threads:[~2006-10-31 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 17:22 Matthias Teege
2006-10-31 18:06 ` Paul Lalonde [this message]
2006-10-31 18:56   ` Russ Cox
2006-11-09 20:17 ` Russ Cox
2006-11-10 13:54   ` David Leimbach
2006-11-10 14:17   ` David Leimbach
2006-11-11  0:35     ` Arvindh Rajesh Tamilmani

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=19DE8459-C68C-4B7C-9686-0EA1F6005DBD@telus.net \
    --to=plalonde@telus.net \
    --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).