unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Takenari Shinohara <takenari.shinohara@gmail.com>,
	Ergus <spacibba@aol.com>
Cc: 37824@debbugs.gnu.org
Subject: bug#37824: Args out of range error
Date: Sat, 19 Oct 2019 20:34:53 +0300	[thread overview]
Message-ID: <834l047i6b.fsf@gnu.org> (raw)
In-Reply-To: <CAKNh7-B4q6PORzUzhtrrbs790qCC-gA1DesertuvFJtwiLf7XQ@mail.gmail.com> (message from Takenari Shinohara on Sun, 20 Oct 2019 00:27:22 +0900)

> From: Takenari Shinohara <takenari.shinohara@gmail.com>
> Date: Sun, 20 Oct 2019 00:27:22 +0900
> 
> After building recent head, I started to see Args out of range errors occasionally.
> 
>  sort: Args out of range: [nil :family :foundry :swidth :height :weight :slant :underline :inverse :foreground ...], 19
> 
> I inspected a little, and I think a found the problem.
> Commit f9206f34d63104c50659a15d3615646a09df87bf intorduced new LFACE_EXTEND_INDEX enum for lface_attribute_index 
> in src/dispextern.h, but probably forgot to add corresponding value to internal-lisp-face-attributes defvar, 
> causing an arg-out-of-range error for few face related functions.
> 
> After adding :extend keyword to internal-lisp-face-attributes the error don't occur.  
> 
> (setq internal-lisp-face-attributes
>   [nil
>    :family :foundry :swidth :height :weight :slant :underline :inverse
>    :foreground :background :stipple :overline :strike :box
>    :font :inherit :fontset :vector :extend])

Thanks.

Jimmy, could you please take a look at this issue?





  reply	other threads:[~2019-10-19 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-19 15:27 bug#37824: Args out of range error Takenari Shinohara
2019-10-19 17:34 ` Eli Zaretskii [this message]
2019-10-20 13:22   ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-20 20:03   ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=834l047i6b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37824@debbugs.gnu.org \
    --cc=spacibba@aol.com \
    --cc=takenari.shinohara@gmail.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).