unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabrice Bauzac-Stehly <libnoon@orange.fr>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 62721@debbugs.gnu.org
Subject: bug#62721: 30.0.50; EUDC: stop adding a wildcard to LDAP searches
Date: Mon, 10 Apr 2023 21:09:46 +0200	[thread overview]
Message-ID: <873557pn9h.fsf@fedora.home> (raw)
In-Reply-To: <m2pm8b7quo.fsf@fastmail.fm> (message from Filipp Gunbin on Mon, 10 Apr 2023 17:29:35 +0300)

Hello,

Sorry, I have not put sufficient information in my initial message.  In
my case, I'm using eudc-query-form, where I know I can add wildcards to
the fields if I want.  My complaint is about the fact that a wildcard is
imposed on me in this case, with annoying consequences.  Thanks to your
message, I understand though that this automatic wildcard may be useful
in other contexts where `eudc-ldap-format-query-as-rfc1558' is called.

Customizing `eudc-ldap-no-wildcard-attributes' would work in the sense
that I could disable the wildcards in all cases, but I suspect this
solution is not ideal as it would also disable it in the case of
eudc-expand-inline where (as I understand from your message) it would
actually be useful.

I think that in the case of eudc-query-form, no wildcard should ever be
added.  What do you think?  Should we pass some parameter so that
eudc-ldap-format-query-as-rfc1558 knows what to do?

Thanks!





  reply	other threads:[~2023-04-10 19:09 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 [this message]
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
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=873557pn9h.fsf@fedora.home \
    --to=libnoon@orange.fr \
    --cc=62721@debbugs.gnu.org \
    --cc=fgunbin@fastmail.fm \
    /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).