From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.103.218.7 with SMTP id v7cs259903muq; Tue, 6 Apr 2010 09:26:18 -0700 (PDT) Received: by 10.204.4.219 with SMTP id 27mr1006870bks.197.1270571177916; Tue, 06 Apr 2010 09:26:17 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 24si28866726bwz.18.2010.04.06.09.26.17; Tue, 06 Apr 2010 09:26:17 -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 D844E3C804D; Tue, 6 Apr 2010 12:26:16 -0400 (EDT) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by rubyforge.org (Postfix) with ESMTP id EB1DF18582E3 for ; Tue, 6 Apr 2010 12:24:41 -0400 (EDT) Received: by qw-out-2122.google.com with SMTP id 3so16857qwe.29 for ; Tue, 06 Apr 2010 09:24:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type; bh=lxYLxLmbqo5EDE2D8P7UWdIzTP6XGJR0Zwvs5w+RJxM=; b=IsuoruQA5B5zYsLfwhktSFjAs2k9rrpIEytPSLL+Xwwx8Hu6XHR8vI4F4Yb7AiSxyN L7MG16mPGBs1cQjQNgX12K0SgjLqTXlhMSulMibCKP+OCHImpFE3w8Sc7HzsGD0jBFBp m2jPQ3pRSAYtgFZzunbSaVpa1ddI7EN8uOO5g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=obwMtMfZ7KCYxrezX0NC7vb7uw4rdL+o+QHjQ1BVe5e2PLcA54YWr568JkZfWb/I3Q GG/nLIelEZs73wsOPkyM6WF6kWyZzkPMzeY9A4q5pELX24aKQshK6k7DNi2a0UOhsxu9 OeJSD/zaXKBP29PL6BrdY/bnh9LKCbKdivaVQ= MIME-Version: 1.0 Received: by 10.229.95.4 with HTTP; Tue, 6 Apr 2010 09:24:17 -0700 (PDT) In-Reply-To: <1270113050-sup-7123@deepthought> References: <1270113050-sup-7123@deepthought> From: "shreyankg@gmail.com" Date: Tue, 6 Apr 2010 21:54:17 +0530 Received: by 10.229.234.68 with SMTP id kb4mr7194980qcb.103.1270571078384; Tue, 06 Apr 2010 09:24:38 -0700 (PDT) Message-ID: To: sup-talk Subject: Re: [sup-talk] Workflow questions 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Thu, Apr 1, 2010 at 3:01 PM, Anirudh Sanjeev wrote: > Hi, > > I've been using sup exclusively for four months now, and it's working > great! I sat down and was watching my email workflow and wanted to know how > other sup users work with their email. > > A. Reading email in the middle of compose: > This is my number one concern. I use vim to write my email, and since sup > makes a blocking call, I am unable to read my email while composing. The > only way I know how to do this right now is to quit my editor, hit ";" to > switch to inbox buffer and read the other emails. > > I was hoping that this workflow would be refactored into something like > this: > 1. User hits a key on message he/she wants to reply to. > 2. A file is created and a background process is launched (gvim remote, > emacs, etc) opening this file. > 3. User edits file, maybe creates more replies, and edits each > individually. > 4. Hitting "y" on a message which user had been composing will pull the > latest saved file and load it into compose mode. > 5. Hitting "y" again will send it. > > If you folks have workarounds for this issue, I'd love to hear it. My > current hack which I'm trying to fix up is to use the publish hook to quote > each message into a temporary file, edit that file, and pull text from that > file when sup invokes my editor to reply. Hi, Even I am facing this issue. Another alternative could be to push sup into a background process while invoking vim/any_other_editor in the foreground. And have some sort of bindings to switch between vim and the background sup process (don't know how that works). Finish editing and quitting would land you to the updated reply buffer in sup. > > B. Contacts: > I don't know if this is the appropriate way to do it, but when I want to > write a new email to a contact, I hit "C" and search for the name, and "M" > again and again till the lazy loading finally finds the name I'm looking > for. > > The system works great, although I wish there was some functionality to > search all contacts without loading all of them first. I use tab completion after pressing 'c' to compose new mail. Although tab completion is nor substitute for search, I agree. > > Whenever I need to include a new email address while composing, I need to > go back to my contacts list which can be quite cumbersome. I was hoping > that Vim's insert mode dictionary completion feature can be used. If all > the contacts are available in one file in the name format, I > can simply say: > > set dictionary += ~/.sup/contacts.txt > And instantly gain completion capabilities. Seems like a good idea. Also it could be handy if some sort of dynamic search could be added while you are typing down the 'To'/'Cc' field after starting to compose a new mail by pressing 'c'. -- Peace and Love, Shreyank Gupta Blog: http://allsortsofshrink.blogspot.com _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk