9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] 'win' execution behaviour in acme
Date: Sat, 30 Jan 2010 22:22:14 -0800	[thread overview]
Message-ID: <fe41879c1001302222j264805bl53a50bc9c02137c6@mail.gmail.com> (raw)

Executing this block of text:

win -e cmd1 args ...
win -e cmd2 args ...
win -e cmd3 args ...
win -e cmd4 args ...

opens up *one* acme window with
the first of the `win' commands.
Once you `Del' that win, the second
one appears, and so forth. But the
behaviour I would expect is that I
get four separate `win' windows, each
running the separate commands.
I'm trying to automate the opening of
the `win' windows through a separate
script, so it would be nice to know
whether there is some way to achieve
what I'd expect.


Thanks,
ak



             reply	other threads:[~2010-01-31  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-31  6:22 Akshat Kumar [this message]
2010-01-31  6:36 ` Tony Lainson
2010-01-31  6:48   ` Akshat Kumar

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=fe41879c1001302222j264805bl53a50bc9c02137c6@mail.gmail.com \
    --to=akumar@mail.nanosouffle.net \
    --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).