unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: 62417@debbugs.gnu.org
Cc: Philip Kaludercic <philipk@posteo.net>
Subject: bug#62417: 30.0.50; Regression: 59ecf25fc860 is the first bad commit
Date: Fri, 24 Mar 2023 13:16:55 +0000	[thread overview]
Message-ID: <87sfducmrc.fsf@gmail.com> (raw)

This was originally reported in
https://github.com/joaotavora/sly/issues/534.  I had forgotten about it
high time I reported it, since it seems to be breaking the SLY Common
Lisp package in more places than I expected.

Before this commit:

   5ecf25fc86081c9df05b84194c36414c225c265 is the first bad commit
   commit 59ecf25fc86081c9df05b84194c36414c225c265
   Author: Philip Kaludercic <philipk@posteo.net>
   Date:   Thu Mar 10 10:59:52 2022 +0100
    
       * window.el (display-buffer-assq-regexp): Use buffer-match
    
    lisp/window.el | 15 ++++-----------
    1 file changed, 4 insertions(+), 11 deletions(-)

SLY, as can be downloaded from https://github.com/joaotavora/sly
operates normally in the following minimal invocation

   src/emacs -Q -nw -L ~/Source/Emacs/sly -l sly --eval '(setq tab-always-indent (quote complete))' -f sly
   ;; type (def, following by TAB

(This is the command I used for bisecting the error.)

After this commit, an error comes up about

   (wrong-type-argument stringp #<buffer *sly-completions*>)

I haven't yet investigated the reason.  There are other use cases inside
SLY that are also failing with similar errors, but they are not as easy
to trigger.

SLY in it its current state has worked for every version of Emacs 25
onwards, probably also 24. I just tested this case with Emacs 26 and it
works fine.

João





             reply	other threads:[~2023-03-24 13:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 13:16 João Távora [this message]
2023-03-24 15:22 ` bug#62417: 30.0.50; Regression: 59ecf25fc860 is the first bad commit João Távora
2023-03-24 16:05   ` Philip Kaludercic
2023-03-24 16:07     ` João Távora
2023-03-24 19:48       ` bug#62417: ; " João Távora
2023-03-25 12:55         ` Eli Zaretskii
2023-03-25 13:04           ` João Távora
2023-03-25 13:20             ` Eli Zaretskii
2023-03-25 13:56               ` João Távora
2023-03-25 14:13                 ` Eli Zaretskii
2023-03-25 14:15                   ` João Távora
2023-03-26 20:22                   ` João Távora
2023-03-26 21:23                     ` Philip Kaludercic
2023-03-27  2:24                     ` Eli Zaretskii
2023-03-27 12:06                       ` João Távora
2023-03-27 13:49                         ` Eli Zaretskii
2023-03-27 14:08                           ` João Távora
2023-03-27 15:20                             ` Eli Zaretskii
2023-03-27 16:33                               ` Eli Zaretskii
2023-03-27 16:42                                 ` João Távora
2023-03-27 17:09                                   ` Eli Zaretskii
2023-03-27 19:26                                     ` Philip Kaludercic
2023-03-28 11:11                                       ` Eli Zaretskii
2023-03-27 16:38                               ` João Távora
2023-03-25 13:17           ` Philip Kaludercic
2023-03-25 13:29             ` 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=87sfducmrc.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=62417@debbugs.gnu.org \
    --cc=philipk@posteo.net \
    /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).