Subject: bug#78142: 31.0.50 C-x C-e error on android

From: badli al rashid <[email-masked]>
Date: Wed, 30 Apr 2025 00:12:07 +0800

I was running the C-x C-e to evaluate the expression. Ielm is working

Debugger entered--Lisp error: (end-of-file)
  read(#<buffer *scratch*>)
  elisp--preceding-sexp()
  elisp--eval-last-sexp(nil)
  #f(compiled-function () #<bytecode 0x186754b75f7f>)()
  handler-bind-1(#f(compiled-function () #<bytecode 0x186754b75f7f>)
(error) eval-expression--debug)
  eval-last-sexp(nil)
  funcall-interactively(eval-last-sexp nil)
  call-interactively(eval-last-sexp nil nil)
  command-execute(eval-last-sexp)

Sent from Gmail

On Wed, Apr 30, 2025, 00:09 Eli Zaretskii <[email-masked]> wrote:

> > From: badli al rashid <[email-masked]>
> > Date: Tue, 29 Apr 2025 23:48:12 +0800
> >
> > Debugger entered--Lisp error: (end-of-file)
> >   read(#<buffer *scratch*>)
> >   elisp--preceding-sexp()
> >   elisp--eval-last-sexp(nil)
> >   #f(compiled-function () #<bytecode 0x186754b75f7f>)()
> >   handler-bind-1(#f(compiled-function () #<bytecode 0x186754b75f7f>)
> (error) eval-expression--debug)
> >   eval-last-sexp(nil)
> >   funcall-interactively(eval-last-sexp nil)
> >   call-interactively(eval-last-sexp nil nil)
> >   command-execute(eval-last-sexp)
>
> This is not a bug if the preceding sexp has unbalanced parentheses or
> if you typed "C-x C-e" at the end of the *scratch* buffer.
>