From: Ramkumar Ramachandra <artagnon@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] [PATCH 0/4] Read and compose simultaneously
Date: Sat, 10 Apr 2010 16:06:07 +0530 [thread overview]
Message-ID: <1270895761-sup-9463@kytes> (raw)
This patch series will allow sup to read and compose in separate
threads when the user wishes to do so.
It's still an early WIP, and I've posted it to the list so I can get a
wider test audience, and more importantly comments on my design. It's
been hacked together in a few hours, *very* buggy at the moment. I've
only minimally tested it with `emacsclient`.
I'd also appreciate any general style comments: I've never written a
line of Ruby prior to this.
Applies cleanly to `next`.
Thanks.
-- Ram
Ramkumar Ramachandra (4):
Add method to shell out asynchronously
Poll for editor status
Callback to compose
Appropriate call to shell_out_async
lib/sup/buffer.rb | 20 ++++++++++++
lib/sup/modes/compose-mode.rb | 17 ++++++++++
lib/sup/modes/edit-message-mode.rb | 58 +++++++++++++++++++----------------
lib/sup/poll.rb | 31 ++++++++++++++++++-
4 files changed, 98 insertions(+), 28 deletions(-)
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2010-04-10 10:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1270895761-sup-9463@kytes \
--to=artagnon@gmail.com \
--cc=sup-talk@rubyforge.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