From: Bulent Murtezaoglu <bm@acm.org>
Subject: Re: sharing files?
Date: Mon, 15 Nov 2004 03:37:16 +0200 [thread overview]
Message-ID: <87mzxjgaer.fsf@p4.internal> (raw)
In-Reply-To: 10pg108cqj13l3d@corp.supernews.com
>>>>> "M" == Mike <mikee@mikee.ath.cx> writes:
[...]
M> That's neat. I had not heard/read the emacs could do that. I'm
M> thinking less of a white-board, though I said that, I'm
M> thinking really of something like a snippet of code that looks
M> for timestamp changes and reloads the buffer. [...]
Hmm, if the whiteboard nature is not required then perhaps one could
consider mail or news.
M> It's not
M> real-time, but should allow sharing of ideas, issues, etc. What
M> do you think?
I think itimers+whatever kind of notification mechanism (beep?) you
want could do this. But you'll still need to work out the details of
who owns what and who can edit what etc. These problems don't exist
in either mail or news.
cheers,
BM
next prev parent reply other threads:[~2004-11-15 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 21:42 sharing files? Mike
2004-11-14 23:17 ` Pascal Bourguignon
2004-11-15 1:19 ` Mike
2004-11-15 1:37 ` Bulent Murtezaoglu [this message]
2004-11-15 3:01 ` David Hansen
2004-11-15 23:11 ` kgold
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mzxjgaer.fsf@p4.internal \
--to=bm@acm.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).