* Re: [SPAM] [9fans] watch command
@ 2005-04-19 6:47 YAMANASHI Takeshi
0 siblings, 0 replies; 3+ messages in thread
From: YAMANASHI Takeshi @ 2005-04-19 6:47 UTC (permalink / raw)
To: 9fans
> let us say i just saved an intermediate version of a.c while doing a
> bigger change. then the above script will kick mk process that is neither
> needed nor useful.
sounds reasonable. I wonder what was the experience in the original
watch command about intermediate modifications...
In my case, I might be going to just ignore the mk error messages
for such mk run. :)
--
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [SPAM] [9fans] watch command
2005-04-19 12:03 ` [SPAM] " vdharani
@ 2005-04-19 14:52 ` Ronald G. Minnich
0 siblings, 0 replies; 3+ messages in thread
From: Ronald G. Minnich @ 2005-04-19 14:52 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
On Tue, 19 Apr 2005 vdharani@infernopark.com wrote:
> >
> > Whenever a.c and b.c are changed, a text will appear on the ctl file.
> > Thus, you can do something like:
> > % while(){read /n/watch/ctl; mk}
> >
> i dont think it will work.
>
> let us say i just saved an intermediate version of a.c while doing a
> bigger change. then the above script will kick mk process that is neither
> needed nor useful. the same is the case when i save a.c but i need to
> change 10 other files to reflect the change in all relevant files.
>
the specific example may not be useful but ... you have no idea how many
times people want this stuff.
But what about a file that the server can provide that provides info about
metadata changes, i.e. you are reading a
/srv/fsstatus
and as things change you get twstat messages?
ron
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [SPAM] [9fans] watch command
2005-04-19 6:17 YAMANASHI Takeshi
@ 2005-04-19 12:03 ` vdharani
2005-04-19 14:52 ` Ronald G. Minnich
0 siblings, 1 reply; 3+ messages in thread
From: vdharani @ 2005-04-19 12:03 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
> I read about "watch" command in the mpx paper (*) and thought
> it's interesting. The paper mentions the commandline:
> watch fig1.pic | pic | troff | proof
> and the pipe line runs whenever fig1.pic is modified.
> Does anyone have a similar program in his pocket?
>
> (*) hget http://cm.bell-labs.com/cm/cs/doc/83/mpx.ps.gz | gunzip | page
>
>
> I'm thinking of writing a file server (watchfs) which will serve:
> /n/watch/ctl
> /n/watch/data/a.c
> /n/watch/data/b.c
>
> Whenever a.c and b.c are changed, a text will appear on the ctl file.
> Thus, you can do something like:
> % while(){read /n/watch/ctl; mk}
>
i dont think it will work.
let us say i just saved an intermediate version of a.c while doing a
bigger change. then the above script will kick mk process that is neither
needed nor useful. the same is the case when i save a.c but i need to
change 10 other files to reflect the change in all relevant files.
thanks
dharani
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-04-19 14:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-04-19 6:47 [SPAM] [9fans] watch command YAMANASHI Takeshi
-- strict thread matches above, loose matches on Subject: below --
2005-04-19 6:17 YAMANASHI Takeshi
2005-04-19 12:03 ` [SPAM] " vdharani
2005-04-19 14:52 ` Ronald G. Minnich
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).