From: Eli Zaretskii <eliz@gnu.org>
To: "Pascal J. Bourguignon" <pjb@informatimago.com>
Cc: 33690@debbugs.gnu.org
Subject: bug#33690: 26.1; Wrong type argument: number-or-marker-p, nil in window-edges
Date: Mon, 10 Dec 2018 09:01:13 +0200 [thread overview]
Message-ID: <837egh3lxi.fsf@gnu.org> (raw)
In-Reply-To: <871s6qe65n.fsf@informatimago.com> (pjb@informatimago.com)
> From: "Pascal J. Bourguignon" <pjb@informatimago.com>
> Date: Sun, 09 Dec 2018 22:34:12 +0100
>
>
> Launching emacs in a terminal (DISPLAY=:0.0, but no X server running),
> including my .emacs, I get
> Wrong type argument: number-or-marker-p, nil in window-edges
> errors on C-n and C-p.
> The error come from window-edges.
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
> window-edges(nil t nil t)
> window-inside-pixel-edges()
> window-screen-lines()
> line-move-partial(1 nil)
> line-move(1 nil nil 1)
> next-line(1 1)
> funcall-interactively(next-line 1 1)
> call-interactively(next-line nil nil)
> command-execute(next-line)
>
> Running with a window-edges not compiled, we find that the problem is
> that border-width is nil. I would therefore suggest to patch
> window-edges, to use 0 when frame-internal-border-width returns nil
> (which occurs when running in a terminal):
I don't understand. The definition of frame-internal-border-width is
this:
DEFUN ("frame-internal-border-width", Fframe_internal_border_width, Sframe_internal_border_width, 0, 1, 0,
doc: /* Return width of FRAME's internal border in pixels. */)
(Lisp_Object frame)
{
return make_number (FRAME_INTERNAL_BORDER_WIDTH (decode_any_frame (frame)));
}
This can only return numbers, never nil, even when we are on a text
terminal. Are you sure you don't override this definition with some
local code?
Thanks.
next prev parent reply other threads:[~2018-12-10 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 21:34 bug#33690: 26.1; Wrong type argument: number-or-marker-p, nil in window-edges Pascal J. Bourguignon
2018-12-10 7:01 ` Eli Zaretskii [this message]
2018-12-10 10:05 ` Pascal J. Bourguignon
2018-12-10 10:16 ` Eli Zaretskii
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=837egh3lxi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33690@debbugs.gnu.org \
--cc=pjb@informatimago.com \
/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).