From: Augusto Stoffel <arstoffel@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50667@debbugs.gnu.org
Subject: bug#50667: Update ecomplete when used via standard UI
Date: Sat, 18 Sep 2021 23:35:51 +0200 [thread overview]
Message-ID: <87ilyxk1mw.fsf@gmail.com> (raw)
In-Reply-To: <87r1dlpp8t.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 18 Sep 2021 23:06:58 +0200")
On Sat, 18 Sep 2021 at 23:06, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Augusto Stoffel <arstoffel@gmail.com> writes:
>
>> If one keeps sets
>>
>> (setq message-mail-alias-type nil ;; or keep the default 'abbrev
>> message-expand-name-standard-ui t)
>>
>> and an ecomplete database file, then everything works OOTB,
>
> Works in what way?
If I hit TAB in an address field, my completion UI kicks in and I can
choose an address from the ecomplete database.
>
>> except that the ecomplete database doesn't get updated with new
>> addresses.
>>
>> Is the following change a reasonable fix for this?
>
> [...]
>
>> - (when (and (message-mail-alias-type-p 'ecomplete)
>> + (when (and (bound-and-true-p ecomplete-database)
>
> I think this would be highly surprising behaviour -- just loading a
> library shouldn't have such side effects.
Loading ecomplete doesn't populate 'ecomplete-database'. But if you set
'message-expand-name-standard-ui' to t, then 'ecomplete-start' will be
called when request completions.
>
> What's your use case here? You don't want to use ecomplete for alias
> expansions, but you still want to update the ecomplete database?
I want to use ecomplete via completion at point instead of ecomplete's
electric UI. This is what the variable
'message-expand-name-standard-ui' is meant for, right?
next prev parent reply other threads:[~2021-09-18 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 21:01 bug#50667: Update ecomplete when used via standard UI Augusto Stoffel
2021-09-18 21:06 ` Lars Ingebrigtsen
2021-09-18 21:35 ` Augusto Stoffel [this message]
2021-09-19 15:10 ` Lars Ingebrigtsen
2021-09-19 16:02 ` Augusto Stoffel
2021-11-05 3:28 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilyxk1mw.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=50667@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).