zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: completion for MUAs
Date: Sat, 14 Apr 2001 18:01:44 +0000	[thread overview]
Message-ID: <1010414180144.ZM3683@candle.brasslantern.com> (raw)
In-Reply-To: <3AD7461F.A6B691FC@u.genie.co.uk>

On Apr 13,  7:31pm, Oliver Kiddle wrote:
} Subject: PATCH: completion for MUAs
}
} The one thing which hasn't been done for any MUA is to parse the
} addressbook/alias list and use it for generating the e-mail addresses.
} 
} Does anyone have suggestions for getting at or parsing the addressbooks
} of different MUAs (apart from MH which is easy)?

There are quite a variety of addressbook formats, ranging from nothing
more than a batch of commands or assignments in the MUA's init files
through Pine's tab-delimited records to networked LDAP lookup.  Rather
than try to provide a function that parses any significant subset of
these, I suggest working out some kind of a plugin model -- paste up a
function name using $service or the like, and call it if it exists.

Then there's also completion of user names @ the local machine, and
maybe even /etc{/mail,}/aliases names or the equivalent for other MTAs.

} Some MUAs are happy with addresses in forms like 'Name <user@host>' and
} 'user@host (Name)'. Any thoughts on how to deal with these (such as
} whether it would be useful to expand to these) and other complications
} such as distribution lists would be helpful.

Some MUAs also are happy with comma-separated lists of addresses in one
or more command-line arguments while others make each argument an address
and don't attempt to parse it further (which can lead to strange problems
later when calling the MTA or having an SMTP conversation).

I'd advise completing only the user@host part, unless it's too difficult
to pick it out of the addressbook entry (but that'd be up to the plugin
in any case, if you take my advice above).

By "distribution lists" do you mean `@groupname:addr,addr,addr;' syntax,
or are you talking about e.g. completing individual addresses that appear
in the definition of a group or alias in the addressbook, or ...?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  parent reply	other threads:[~2001-04-14 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-13 18:31 Oliver Kiddle
2001-04-14 17:22 ` Bart Schaefer
2001-04-14 18:01 ` Bart Schaefer [this message]
2001-04-19 18:27   ` Oliver Kiddle
2001-04-20  4:11     ` Bart Schaefer

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=1010414180144.ZM3683@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).