From: Anirudh Sanjeev <anirudh@anirudhsanjeev.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Workflow questions
Date: Thu, 01 Apr 2010 15:01:22 +0530 [thread overview]
Message-ID: <1270113050-sup-7123@deepthought> (raw)
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.
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.
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 <emailaddress> format, I
can simply say:
set dictionary += ~/.sup/contacts.txt
And instantly gain completion capabilities.
Thanks,
Anirudh
--
Senior Undergraduate Student, Indian Institute of Technology, Kharagpur
http://anirudhsanjeev.org
The Unix philosophy - Do one thing. Do it well.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-04-06 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 9:31 Anirudh Sanjeev [this message]
2010-04-06 16:24 ` shreyankg
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=1270113050-sup-7123@deepthought \
--to=anirudh@anirudhsanjeev.org \
--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