unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>,
	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 09:00:30 -0800 (PST)	[thread overview]
Message-ID: <9528f14b-c69b-42f6-9851-1edb04418ae8@default> (raw)
In-Reply-To: <trinity-4880b592-507d-445b-8ebd-f2f68b69be0a-1608742558551@3c-app-mailcom-bs08>

> 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)
 
> Debugger entered--Lisp error: (end-of-buffer)

Do you see that when you start Emacs with `emacs -Q'?

Do you mean that each time you hit a vertical arrow key you get such an error, or just when you do that at the beginning or end of an Info node.  The latter is expected.



  reply	other threads:[~2020-12-23 17:00 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 [this message]
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
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=9528f14b-c69b-42f6-9851-1edb04418ae8@default \
    --to=drew.adams@oracle.com \
    --cc=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).