9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme
Date: Wed, 20 Mar 2002 06:58:36 +0000	[thread overview]
Message-ID: <20020320070411.4BE6A19A82@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

as rob says, you can control that effect, but it's perhaps worth noting that
with acme, because each frame carries its own directory with it, it's quite
common to have one big acme window set up once and edit everything from everywhere in it.
remake in any given directory by typing mk (once for all) in the tag of that frame
and clicking it with button 2.  when using rio windows as well, perhaps
to develop or debug a graphics application, files are sent for editing using the B
command (it's documented with sam(1) but because it uses the plumber, it
will send files to acme too if that's what you're using).

using it that way, i find that acme thoughtfully keeps track of all the things i am doing,
at various stages of interruption; on the other hand, it conveniently offers email in
the same environment, which can lead to further interruption (but it's still highly
convenient).


[-- Attachment #2: Type: message/rfc822, Size: 2352 bytes --]

To: <9fans@cse.psu.edu>
Subject: [9fans] Acme
Date: Tue, 19 Mar 2002 22:26:16 -0500
Message-ID: <000701c1cfbe$ff2c1720$aa952f18@jjmj301>

Hi,

I have noticed a problem in Acme.

I open two windows in rio. Then I start Acme in both the windows. Now, if I
open a file in one Acme instance, it opens the file in both the instances.

Is this a problem? Or am I missing something?

Thanks
dharani


             reply	other threads:[~2002-03-20  6:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20  6:58 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-27 12:39 [9fans] acme Kenji Arisawa
2010-11-27 18:12 ` ron minnich
2010-11-28 11:17   ` Kenji Arisawa
2007-06-05 11:28 cej
2007-06-05 11:39 ` Federico Benavento
2007-06-05 12:01   ` Gabriel Diaz
2007-06-05 12:11     ` erik quanstrom
2007-06-05 11:59 ` erik quanstrom
2007-06-05 15:00 ` Russ Cox
2007-06-05 15:09   ` ron minnich
2007-06-06 12:12     ` cej
2007-06-05 17:55   ` lucio
2007-06-05 19:30     ` ron minnich
2007-06-05 18:00   ` lucio
2007-06-12 12:29     ` cej
2007-06-12  8:57       ` Russ Cox
2007-06-13  8:49         ` Richard Miller
2007-06-13  5:13           ` Russ Cox
2007-06-15  4:12             ` Russ Cox
2004-01-10  7:01 [9fans] Sam's protocol description? Rob Pike
2004-01-10 15:46 ` [9fans] acme vdharani
2004-01-10 16:07   ` rob pike, esq.
2002-05-10  2:24 rob pike, esq.
2002-03-20  3:30 [9fans] Acme rob pike
2002-03-11  0:15 [9fans] samuel Geoff Collyer
2002-03-20  3:26 ` [9fans] Acme Tharaneedharan Vilwanathan

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=20020320070411.4BE6A19A82@mail.cse.psu.edu \
    --to=forsyth@caldo.demon.co.uk \
    --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).