From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200204031547.g33Flx326078@copernicus.cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] finding acme window id from shell script?
In-reply-to: Your message of "Wed, 03 Apr 2002 15:58:06 +0100."
             <20020403145516.4284F199D5@mail.cse.psu.edu>
References: <20020403145516.4284F199D5@mail.cse.psu.edu>
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed,  3 Apr 2002 17:47:58 +0200
Topicbox-Message-UUID: 726327d0-eaca-11e9-9e20-41e7f4b1d025

> > id=`{grep $% /mnt/acme/index | awk '{print $1}'} ,  or so
>
> that's not entirely accurate as it's quite possible to have have
> different acme windows with the same tag file, either deliberately
> (via Zerox) or accidentally (by typing).

Agreed. Your $acmewin is better in that respect.
Or e.g. a file /mnt/acme/id , or...

> while we're on the subject of shell scripts for acme, here's a little
> shell script i wrote years ago to show me what changes i'd made to a
> file within acme.
> it's a testament to the resilience of the file-style interface that it
> has remained unchanged (and working) throughout all the changes to
> acme (e.g. alef->C) that have taken place in the meantime. the
> modification date on the script is March 1999.


Nice! (both the script, and the resilience of the file-style interface)

Axel.