GNU bug report logs - #25385
24.5; `shr-next-link' wrong-type-argument error

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 25385 in the body.
You can then email your comments to 25385 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.5; `shr-next-link' wrong-type-argument error
Date: Sat, 7 Jan 2017 09:01:09 -0800 (PST)

Apologies if this doesn't help at all - please close it in that case.

I don't use EWW, but I used it very briefly, and got this when I hit
`TAB' near the end of the buffer:

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  text-property-not-all(nil 423 help-echo nil)
  shr-next-link()
  call-interactively(shr-next-link nil nil)
  command-execute(shr-next-link)

Presumably a more user-friendly error should be raised if there are no
more links to navigate to.


In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'

Message #8 received at 25385 <at> debbugs.gnu.org (full text, mbox):

From: npostavs <at> users.sourceforge.net
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 25385 <at> debbugs.gnu.org
Subject: Re: bug#25385: 24.5; `shr-next-link' wrong-type-argument error
Date: Sat, 07 Jan 2017 12:08:38 -0500

tags 25385 confirmed
tags 25385 fixed
close 25385 25.1
quit

Drew Adams <drew.adams <at> oracle.com> writes:

> Apologies if this doesn't help at all - please close it in that case.
>
> I don't use EWW, but I used it very briefly, and got this when I hit
> `TAB' near the end of the buffer:
>
> Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
>   text-property-not-all(nil 423 help-echo nil)
>   shr-next-link()
>   call-interactively(shr-next-link nil nil)
>   command-execute(shr-next-link)
>
> Presumably a more user-friendly error should be raised if there are no
> more links to navigate to.

In Emacs 25.1, EWW responds with a "No next link" message in this
scenario.

Message #17 received at 25385 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 25385 <at> debbugs.gnu.org
Subject: Re: bug#25385: 24.5; `shr-next-link' wrong-type-argument error
Date: Sat, 07 Jan 2017 18:09:43 +0100

On Jan 07 2017, Drew Adams <drew.adams <at> oracle.com> wrote:

> I don't use EWW, but I used it very briefly, and got this when I hit
> `TAB' near the end of the buffer:
>
> Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
>   text-property-not-all(nil 423 help-echo nil)
>   shr-next-link()
>   call-interactively(shr-next-link nil nil)
>   command-execute(shr-next-link)
>
> Presumably a more user-friendly error should be raised if there are no
> more links to navigate to.

I cannot reproduce that.  I get a message "No next link", and no error.

Andreas.

-- 
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Previous Next

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