From: Christopher Dimech <dimech@gmx.com>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Info file in emacs.gives Lisp error: (beginning-of-buffer) (end-of-buffer)
Date: Wed, 23 Dec 2020 18:35:36 +0100 [thread overview]
Message-ID: <trinity-e409eb35-d79d-434a-b5a7-66c60ab6332f-1608744936003@3c-app-mailcom-bs08> (raw)
In-Reply-To: <m1zh24o303.fsf@yahoo.es>
I had debug-on-error. Am now doing a cycle function for debug "on"
and "off".
Can I improve on the following?
(defvar debug-cycle-state 1)
(defun debug-cycle ()
(interactive)
(pcase typh-frame-size-state
(1 (setq debug-on-error nil)
(setq typh-frame-size-state 2))
(2 (setq debug-on-error t)
(setq debug-ignored-errors nil)
(setq debug-on-message "unescaped character literals")
(setq typh-frame-size-state 1)) ))
(global-set-key (kbd "H-g") #'debug-cycle)
> Sent: Wednesday, December 23, 2020 at 10:48 PM
> From: "Daniel Martín" <mardani29@yahoo.es>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Info file in emacs.gives Lisp error: (beginning-of-buffer) (end-of-buffer)
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > I am displaying an info file in emacs. But when I use the arrow keys to move up and down
> > the document I get
> >
> > Debugger entered--Lisp error: (beginning-of-buffer)
> > signal(beginning-of-buffer nil)
> > previous-line(1 1)
> > funcall-interactively(previous-line 1 1)
> > call-interactively(previous-line nil nil)
> > command-execute(previous-line)
> >
> >
> > Debugger entered--Lisp error: (end-of-buffer)
> > signal(end-of-buffer nil)
> > next-line(1 1)
> > funcall-interactively(next-line 1 1)
> > call-interactively(next-line nil nil)
> > command-execute(next-line)
>
> I can't reproduce this problem. Could you give some more detailed steps
> to reproduce it? How much content does the Info file have? Can you
> reproduce the problem from "emacs -Q"? Thanks.
>
next prev parent reply other threads:[~2020-12-23 17:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 16:55 Info file in emacs.gives Lisp error: (beginning-of-buffer) (end-of-buffer) Christopher Dimech
2020-12-23 17:00 ` Drew Adams
2020-12-23 17:10 ` Christopher Dimech
2020-12-23 17:35 ` Eli Zaretskii
2020-12-23 17:40 ` Christopher Dimech
2020-12-23 17:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-23 17:13 ` Christopher Dimech
2020-12-23 17:18 ` Daniel Martín
2020-12-23 17:35 ` Christopher Dimech [this message]
2020-12-23 17:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-23 17:56 ` Christopher Dimech
2020-12-23 18:49 ` Christopher Dimech
2020-12-23 18:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-23 18:59 ` Christopher Dimech
2020-12-23 19:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-24 4:55 ` Christopher Dimech
2020-12-24 5:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-24 5:39 ` Christopher Dimech
2020-12-24 6:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-24 6:48 ` Christopher Dimech
2020-12-24 8:10 ` Michael Heerdegen
2020-12-24 8:23 ` Christopher Dimech
2020-12-24 11:10 ` Michael Heerdegen
2020-12-24 11:28 ` Christopher Dimech
2020-12-24 11:29 ` Christopher Dimech
2020-12-24 12:43 ` Michael Heerdegen
2020-12-24 16:35 ` Drew Adams
2020-12-25 4:21 ` Michael Heerdegen
2020-12-24 4:09 ` Michael Heerdegen
2020-12-24 4:58 ` Christopher Dimech
2020-12-24 5:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-24 5:44 ` Christopher Dimech
2020-12-24 14:24 ` 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=trinity-e409eb35-d79d-434a-b5a7-66c60ab6332f-1608744936003@3c-app-mailcom-bs08 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mardani29@yahoo.es \
/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.
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).