From: Michael Heerdegen <michael_heerdegen@web.de>
To: ding@gnus.org
Subject: Re: Define groups of recipients
Date: Mon, 18 Mar 2019 17:54:32 +0100 [thread overview]
Message-ID: <87zhpsqg1j.fsf@web.de> (raw)
In-Reply-To: <878sxd7j2r.fsf@uwo.ca> (Dan Christensen's message of "Sun, 17 Mar 2019 08:59:24 -0400")
Dan Christensen <jdc@uwo.ca> writes:
> and then you compose a message to groupname and hit SPC or , after
> groupname and it expands.
FWIW I guess this could also work with normal completion but
`message-expand-name' doesn't try when you use bbdb, even if bbdb
doesn't have a completion:
#+begin_src emacs-lisp
(defun message-expand-name ()
(cond ((and (memq 'eudc message-expand-name-databases)
(boundp 'eudc-protocol)
eudc-protocol)
(eudc-expand-inline))
((and (memq 'bbdb message-expand-name-databases)
(fboundp 'bbdb-complete-name))
(let ((starttick (buffer-modified-tick)))
(or (bbdb-complete-name)
;; Apparently, bbdb-complete-name can return nil even when
;; completion took place. So let's double check the buffer was
;; not modified.
(/= starttick (buffer-modified-tick)))))
(t
(expand-abbrev))))
#+end_src
I wonder if this is intended. I guess it is, at least it has been like
that for a long time.
Michael.
next prev parent reply other threads:[~2019-03-18 16:54 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
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 [this message]
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=87zhpsqg1j.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).