Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: problems with eudc-expand-inline in EUDC
Date: Fri, 19 Mar 2010 14:31:44 -0500	[thread overview]
Message-ID: <87iq8s5crj.fsf@lifelogs.com> (raw)
In-Reply-To: <87pr33t3tv.fsf@zinc.branchcut.ath.cx>

On Wed, 17 Mar 2010 10:34:04 -0400 Desmond Rivet <desmond_news@videotron.ca> wrote: 

DR> I'm attempting to connect to an LDAP server containing some email
DR> contacts.  The relavent portion of my .gnus.el looks like this:
...
DR> I type "m" to bring up a mail buffer.  Then I type, for example, "david"
DR> in the the To: field and I type "TAB" (associated with
DR> eudc-expand-inline).  What I *expect* to see is some kind of indication
DR> that "david" doesn't exist in LDAP, or that he does and here he is, or
DR> that emacs had trouble connecting to the server, etc.  Something along
DR> these lines.  What I see instead is this (once I turn on debug):

DR> Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
DR>   byte-code("...")
DR>   eudc-expand-inline()
DR>   call-interactively(eudc-expand-inline nil nil)

DR> I'm a bit mystified by this.  I presume that eudc-expand-inline is
DR> epxpecting a string as one of its arguments, and is instead getting nil.
DR> The help for the function doesn't mention a string arugment.  It only
DR> mentions the replace-p argument.

DR> If I had to take a stab at guessing, I would say that eudc-expand-inline
DR> takes the query string (extracted from the buffer before the point) as
DR> a parameter, and this string is not being extracted properly.

I think this is an Emacs issue, not Gnus-specific.  Could you try to
replicate it with a recent Emacs checkout and submit it as an Emacs bug
if necessary?

Thanks
Ted

      reply	other threads:[~2010-03-19 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 14:34 Desmond Rivet
2010-03-19 19:31 ` Ted Zlatanov [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=87iq8s5crj.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=info-gnus-english@gnu.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.
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).