From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 58605@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#58605: 29.0.50; Commit 2a2f5530fa2 breaks ldap-search-internal
Date: Tue, 25 Oct 2022 15:42:07 +0200 [thread overview]
Message-ID: <87bkq06mvk.fsf@wi.uni-muenster.de> (raw)
In-Reply-To: <m28rl4t5ca.fsf@fastmail.fm> (Filipp Gunbin's message of "Tue, 25 Oct 2022 16:12:21 +0300")
Hi Filipp,
I’m not sure about conventions for closed bugs but I reply once more
here...
On 2022-10-25, Filipp Gunbin wrote:
> Hi Jens,
>
> On 25/10/2022 07:55 +0200, Jens Lechtenboerger wrote:
>
>> Hi there!
>>
>> On 2022-10-24, Filipp Gunbin wrote:
>>
>>> [...]
>>> But ldap-search expects ldap-ldapsearch-args to be at least what default
>>> value is, to be able to parse the output (btw, "-LL" was there since
>>> "forever", which is 20 years in this case; it's just the third L which
>>> was added recently, to exclude ldif version from the output).
>>
>> How should users know about that expectation?
>
> As I wrote, there should be no need to use it at all.
Then maybe it should not exist (at least not as defcustom).
Alternatively, the doc string might be improved:
A list of required arguments to pass to ‘ldapsearch’. Internal code
depends on the default value.
Best wishes
Jens
P.S. Thanks for your pointers regarding encryption with OpenLDAP!
next prev parent reply other threads:[~2022-10-25 13:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 6:05 bug#58605: 29.0.50; Commit 2a2f5530fa2 breaks ldap-search-internal Jens Lechtenboerger
2022-10-18 14:17 ` Eli Zaretskii
2022-10-20 8:12 ` Juri Linkov
2022-10-20 17:58 ` Filipp Gunbin
2022-10-21 6:25 ` Jens Lechtenboerger
2022-10-21 15:16 ` Filipp Gunbin
2022-10-22 9:43 ` Jens Lechtenboerger
2022-10-24 16:06 ` Filipp Gunbin
2022-10-25 5:55 ` Jens Lechtenboerger
2022-10-25 13:12 ` Filipp Gunbin
2022-10-25 13:42 ` Jens Lechtenboerger [this message]
2022-10-25 15:07 ` Filipp Gunbin
2022-10-26 6:07 ` Jens Lechtenboerger
2022-10-26 13:20 ` Filipp Gunbin
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=87bkq06mvk.fsf@wi.uni-muenster.de \
--to=lechten@wi.uni-muenster.de \
--cc=58605@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=juri@linkov.net \
/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).