Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Define groups of recipients
Date: Fri, 15 Mar 2019 17:41:25 -0700	[thread overview]
Message-ID: <87bm2babwq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871s3793mx.fsf@web.de>

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> > Ok, that would be the last resort.  I had hoped for a nice solution in
>> > Emacs.
>>
>> But what would a "nice solution" look like? I suppose you could always
>> write your own completion-at-point function.
>
> That I could somewhere create a record for a group consisting of a name,
> a mail alias, and a number of Email addresses.  Writing my own
> completion-at-point function doesn't count as "nice".

No, I suppose not. You can also build mail abbrevs without too much
trouble using the function `define-mail-abbrev', that might be your
easiest entry-point. I'm still not quite clear on what your ideal
workflow would be here.

>> > BTW, anyone knowing why BBDB comes with a manual that looks like
>>
>> BBDB's lack of manual is half of why I ended up writing EBDB (only
>> partly joking).
>
> Ok, I may be switching because of the manual (also only partly joking).
> No, I wanted to have a look at it for a longer time anyway ;-)

I've been sort of tracking the vCard RFC when considering what record
classes to add, and vCard does have the concept of a "group" record,
which is just a collection of other records. This wouldn't save you any
work, however, since you'd still need to create the person records, and
add them to the group. I suppose I could allow adding mail fields
instead of "people" to the group, but it still seems roundabout.

Eric




  reply	other threads:[~2019-03-16  0:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 13:45 Michael Heerdegen
2019-03-15 14:50 ` Enrico Schumann
2019-03-15 15:44   ` Michael Heerdegen
2019-03-15 15:58     ` Eric Abrahamsen
2019-03-15 19:37       ` Michael Heerdegen
2019-03-15 21:41         ` Eric Abrahamsen
2019-03-15 22:25           ` Michael Heerdegen
2019-03-16  0:41             ` Eric Abrahamsen [this message]
2019-03-17  0:42     ` Bob Newell
2019-03-17 12:42       ` Michael Heerdegen
2019-03-17 12:59         ` Dan Christensen
2019-03-18 15:16           ` Emanuel Berg
2019-03-18 16:31           ` Michael Heerdegen
2019-03-18 16:54           ` Michael Heerdegen
2019-03-18 17:15             ` Eric Abrahamsen
2019-03-18 22:59               ` Emanuel Berg
2019-03-19 15:34                 ` Eric Abrahamsen
2019-03-19 16:53                   ` Emanuel Berg
2019-03-16  0:17 ` Emanuel Berg

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=87bm2babwq.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).