From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Fabrice Bauzac-Stehly <libnoon@orange.fr>
Cc: 62721@debbugs.gnu.org, fgunbin@fastmail.fm
Subject: bug#62721: 30.0.50; EUDC: stop adding a wildcard to LDAP searches
Date: Mon, 15 May 2023 14:28:39 -0400 [thread overview]
Message-ID: <m3r0rha1pk.fsf@fitzsim.org> (raw)
In-Reply-To: <878rdqg24j.fsf@fedora.home> (Fabrice Bauzac-Stehly's message of "Sun, 14 May 2023 21:10:52 +0200")
Hi Fabrice,
Fabrice Bauzac-Stehly <libnoon@orange.fr> writes:
> For the time being, on my side, I customize "Eudc Ldap No Wildcard
> Attributes" by adding to this list the attribute for which I don't want
> an automatic "*" wildcard appended.
Do you mind posting the `eudc-ldap-no-wildcard-attributes' setting you
ended up with? The docstring for that variable doesn't mention
adjusting this as a preference, only LDAP failure workarounds. I would
like to update the docstring with an example, to make your use case more
discoverable.
> As a software engineer, I suspect this issue could be better addressed
> by the Emacs codebase, because I don't think it is wise for
> eudc-query-form to arbitrarily add an automatic wildcard to the last
> field, this does not make sense to me. But I'll let Emacs experts think
> about it.
>
> As far as I'm concerned, I have this workaround that works for me.
OK, thanks for following up. My feeling is that someone using both
`eudc-query-form' and `eudc-expand-inline' would want the behaviour of
both functions to match with respect to wildcard addition. And
`eudc-ldap-no-wildcard-attributes' allows the user to customize the
behaviour to their preference/expectation (which you've done), so I
think this is fine as-is (except the docstring).
Thomas
next prev parent reply other threads:[~2023-05-15 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 7:20 bug#62721: 30.0.50; EUDC: stop adding a wildcard to LDAP searches Fabrice Bauzac-Stehly
2023-04-10 14:29 ` Filipp Gunbin
2023-04-10 19:09 ` Fabrice Bauzac-Stehly
2023-04-10 19:36 ` Filipp Gunbin
2023-04-19 12:48 ` Thomas Fitzsimmons
2023-05-14 19:10 ` Fabrice Bauzac-Stehly
2023-05-15 18:28 ` Thomas Fitzsimmons [this message]
2023-05-15 20:15 ` Fabrice Bauzac-Stehly
2023-05-15 20:36 ` Thomas Fitzsimmons
2023-05-15 20:40 ` Thomas Fitzsimmons
2023-05-15 21:56 ` Thomas Fitzsimmons
2023-05-16 8:24 ` Fabrice Bauzac-Stehly
2023-05-16 8:14 ` Fabrice Bauzac-Stehly
2023-05-16 10:57 ` Thomas Fitzsimmons
2023-05-17 6:12 ` Fabrice Bauzac-Stehly
2023-05-17 11:01 ` Thomas Fitzsimmons
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=m3r0rha1pk.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=62721@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=libnoon@orange.fr \
/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).