GNU bug report logs - #17165
24.4.50; icomplete-exhibit: (wrong-type-argument number-or-marker-p nil)

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Glenn Morris <rgm <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#17165: closed (24.4.50; icomplete-exhibit: (wrong-type-argument
 number-or-marker-p nil))
Date: Wed, 07 Dec 2016 20:00:03 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 07 Dec 2016 14:58:56 -0500
with message-id <vazik7se7z.fsf <at> fencepost.gnu.org>
and subject line Re: bug#17165: 24.4.50; icomplete-exhibit: (wrong-type-argument number-or-marker-p nil)
has caused the debbugs.gnu.org bug report #17165,
regarding 24.4.50; icomplete-exhibit: (wrong-type-argument number-or-marker-p nil)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
17165: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17165
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.4.50; icomplete-exhibit: (wrong-type-argument number-or-marker-p
 nil)
Date: Tue, 1 Apr 2014 18:59:18 -0700 (PDT)

I have some code that does this:

(when (and (featurep 'icomplete)
           (natnump icicle-icomplete-mode-max-candidates))
      (if (< nb-cands icicle-icomplete-mode-max-candidates)
          (if (not icicle-last-icomplete-mode-value)
              (icomplete-mode -1)
            (icomplete-mode 1)
            (icomplete-exhibit)) ; <==========
          (icomplete-tidy)
          (icomplete-mode -1)))

Once in a while I have seen this wrong-type-argument error.  I suspect,
but I do not know, that it comes from this code in `icomplete-exhibit':

(if (and (or icomplete-show-matches-on-no-input
             (> (icomplete--field-end) (icomplete--field-beg)))
    ...

I see that `icomplete--field-end' and `icomplete--field-beg' are defined
simply in terms of `completion-in-region--data'.  And AFAICT, that
variable can be nil, in which case each of `icomplete--field-(end|beg)'
is nil also.

I see too that in minibuffer.el `completion-in-region--data' is
initialized to nil, and the code there takes care to test for a non-nil
value before trying to access its components using `nth':

(and completion-in-region--data
     (and (eq (marker-buffer (nth 0 completion-in-region--data))
              (current-buffer))
          (>= (point) (nth 0 completion-in-region--data))
          (<= (point)
              (save-excursion
                (goto-char (nth 1 completion-in-region--data))
                (line-end-position)))
         (funcall completion-in-region-mode--predicate)))

A naive guess is that the code in icomplete.el should do likewise:
ensure that `completion-in-region--data' is non-nil before applying
`nth' to it and then using the result in a numeric comparison.

HTH.



In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
 of 2014-03-27 on ODIEONE
Bzr revision: 116884 lekktu <at> gmail.com-20140327173422-cr942b3hn7xjurks
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/snapshot/trunk
 --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
 LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
 -Ic:/Devel/emacs/include''

[Message part 3 (message/rfc822, inline)]

From: Glenn Morris <rgm <at> gnu.org>
To: 17165-done <at> debbugs.gnu.org
Subject: Re: bug#17165: 24.4.50;
 icomplete-exhibit: (wrong-type-argument number-or-marker-p nil)
Date: Wed, 07 Dec 2016 14:58:56 -0500

>> Do you have a recipe for this bug?
>
> No.  And I haven't been able to debug it.

So it can't lead anywhere; closing.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.