From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.32.82 with SMTP id b18cs52674ebd; Sat, 10 Apr 2010 03:45:20 -0700 (PDT) Received: by 10.204.153.24 with SMTP id i24mr1352846bkw.213.1270896320445; Sat, 10 Apr 2010 03:45:20 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id u10si4902479bkz.11.2010.04.10.03.45.20; Sat, 10 Apr 2010 03:45:20 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 8AC5C185831C; Sat, 10 Apr 2010 06:45:19 -0400 (EDT) Received: from mail-pv0-f178.google.com (mail-pv0-f178.google.com [74.125.83.178]) by rubyforge.org (Postfix) with ESMTP id 1371218582D4 for ; Sat, 10 Apr 2010 06:45:10 -0400 (EDT) Received: by pvg4 with SMTP id 4so2641940pvg.23 for ; Sat, 10 Apr 2010 03:45:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:subject:from:to :date:message-id:user-agent:content-transfer-encoding; bh=TmJnvyBhsIZWfc5Z478TGR//mHqNQaaEe3xDxkNOyl8=; b=U2ucrfk+BAqHY6Ld30gwSCukuTyXrj0chSxSY4JiFnpLPnWYivv3f5OgyIxHpSOmE9 zzpUUUyc1xKqsW5E4Qskw1QaKKaQh/9QqjQHoFG5HVXFnoiecC1UYEVkJf+dQOjMFDOa WrUz/mSd8tMrm3GzSuB3HPYMxQNNAqjrneUWQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:date:message-id:user-agent :content-transfer-encoding; b=eztmr0kJytovbH5bPDmOLvLrBEAxfsIpZCN9S/Jx1baGyeXREOTUlxNB3egz4DToTl OgvMZnwEb+5hsaCyA+LJ86kaFrVlnVTA4n9JsUSz3f0ZrUxVdgGAU1KYpk4lwXSYgOuw UrsGufjUR0rv8sHC68POJs3nW7ABWQ7iS8Jbw= Received: by 10.141.12.8 with SMTP id p8mr1521012rvi.134.1270895908817; Sat, 10 Apr 2010 03:38:28 -0700 (PDT) Received: from localhost ([203.110.240.41]) by mx.google.com with ESMTPS id 21sm1836965pzk.8.2010.04.10.03.38.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 10 Apr 2010 03:38:28 -0700 (PDT) From: Ramkumar Ramachandra To: sup-talk Date: Sat, 10 Apr 2010 16:06:07 +0530 Message-Id: <1270895761-sup-9463@kytes> User-Agent: Sup/git Subject: [sup-talk] [PATCH 0/4] Read and compose simultaneously X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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