From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] External contact manager/address book
Date: Wed, 07 May 2008 14:10:35 -0400 [thread overview]
Message-ID: <1210183305-sup-1959@cabinet> (raw)
In-Reply-To: <1210180469-sup-4780@dhn-desktop>
Excerpts from Daniel H. Neilson's message of Wed May 07 13:14:39 -0400 2008:
> In keeping with the philosophy of having one good tool for each job, I
> use a separate program to manage contacts (abook). It helps me to
> have phone numbers, birthdays, mailing addresses, and e-mail addresses
> all in the same place.
Hey, thanks for linking to abook. It looks like it might be exactly
what I've been looking for.
> abook is designed to work with mutt, using
>
> set query_command="abook --mutt-query '%s'"
>
> I wonder if there is a way to get similar behavior in sup?
I think you're looking for the extra-contact-addresses hook, announced
about a month ago:
extra-contact-addresses
-----------------------
File: ~/.sup/hooks/extra-contact-addresses.rb
A list of extra addresses to propose for tab completion, etc. when the
user is entering an email address. Can be plain email addresses or can
be full "User Name <email at domain.tld>" entries.
Variables: none
Return value: an array of email address strings.
Looks like, at present, you'll have to request the full db from abook
and pass it up to sup, and you'll have to do a bit of processing to
transform the format from mutt's "email at address Full Name" to "Full Name
<email at address>".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080507/25fe5341/attachment.bin>
next prev parent reply other threads:[~2008-05-07 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 17:14 Daniel H. Neilson
2008-05-07 18:10 ` Marc Hartstein [this message]
2008-05-08 11:26 ` Israel Herraiz
2008-05-08 11:55 Daniel H. Neilson
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=1210183305-sup-1959@cabinet \
--to=marc.hartstein@alum.vassar.edu \
/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