From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] anyone else notice this expecation
Date: Tue, 22 Apr 2003 12:31:24 +0100 [thread overview]
Message-ID: <253bc58359da15876710414b0e133dee@vitanuova.com> (raw)
In-Reply-To: <a48d2492ff119252b4424f99af499552@plan9.bell-labs.com>
> > i think the solution is probably to have a central
> > acme/sam-like server, so i can be using several clients
> > to edit the same files without conflicts
> > and with whatever UI is appropriate.
>
> how does this solve the screen real estate problem?
it means i could use a sam -d like interface
to edit lots of files at once without worrying
about whether some of those same files are
currently being edited inside an acme
session.
it's annoying when that happens, because
i then have to try to merge the disparate
changes made in each version, which
is error prone (i've been bitten a fair few times)
next prev parent reply other threads:[~2003-04-22 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 16:27 matt
2003-04-17 16:49 ` rog
2003-04-17 16:50 ` rsc
2003-04-17 17:20 ` rog
2003-04-18 0:36 ` okamoto
2003-04-20 19:33 ` rog
2003-04-20 19:51 ` Russ Cox
2003-04-22 11:31 ` rog [this message]
2003-04-22 13:10 ` matt
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=253bc58359da15876710414b0e133dee@vitanuova.com \
--to=rog@vitanuova.com \
--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).