From: Josh Huber <huber+news@alum.wpi.edu>
Subject: Re: connect to MS Exchange ldap
Date: Wed, 30 Jun 2004 14:46:06 -0400 [thread overview]
Message-ID: <87smccrij5.fsf@amalthea.paradoxical.net> (raw)
In-Reply-To: <871xjxgvpx.fsf@isolkhowik.isd.dp.ua>
Serge Olkhowik <solo@isd.dp.ua> writes:
> * when query form is used I have to fill any search field exactly, i.e. not
> "solo" for e-mail, but "solo@isd.dp.ua"
>
> is it possible to exec partial match query?
I wonder if the LDAP schema is different for your exchange setup?
I can show my entry in our ldap directory with something like this:
ldapsearch -x -D "jhuber@company.com" -b "dc=company,dc=com" -W \
-h dc1.company.com "cn=Josh Huber"
I have this in my custom configuration:
'(eudc-inline-query-format (quote ((sn) (givenName) (givenName
sn) (mailNickname) (sAMAccountName))))
Each is a symbol in the schema which eudc will try to match on
with whatever text is before the point (when you issue an
eudc-expand-inline).
Here are a few:
givenName: Josh
sn: Huber
mailNickname: jhuber
sAMAccountName: jhuber
> * eudc-expand-inline doesn't work properly, for example I'm typing "solo"
> and then "M-x eudc-expand-inline" - it removes my text (i.e. "solo") and
> opens another buffer like this:
>
> ,----
> | Click <mouse-2> on a completion to select it.
> | In this buffer, type RET to select the completion near point.
> |
> | Possible completions are:
> | <> <>
> | <> <>
> `----
Are the "possible completions" really empty? I wonder if this
has something to do with the query format as well...
What is the value of eudc-inline-query-format, and do the
symbols match the schema of your ldap directory entries?
--
Josh Huber
prev parent reply other threads:[~2004-06-30 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <873c4jio1o.fsf@isolkhowik.isd.dp.ua>
2004-06-26 21:02 ` Kai Grossjohann
[not found] ` <87zn6niiof.fsf@amalthea.paradoxical.net>
[not found] ` <871xjxgvpx.fsf@isolkhowik.isd.dp.ua>
2004-06-30 18:46 ` Josh Huber [this message]
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=87smccrij5.fsf@amalthea.paradoxical.net \
--to=huber+news@alum.wpi.edu \
/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).