all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: Info file in emacs.gives Lisp error: (beginning-of-buffer) (end-of-buffer)
Date: Thu, 24 Dec 2020 07:48:00 +0100	[thread overview]
Message-ID: <trinity-6e0c3f0c-1681-46ed-9723-a5ca8cfc9e2b-1608792479931@3c-app-mailcom-bs02> (raw)
In-Reply-To: <87zh2367fn.fsf@zoho.eu>


> Sent: Thursday, December 24, 2020 at 12:01 PM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Info file in emacs.gives Lisp error: (beginning-of-buffer) (end-of-buffer)
>
> Christopher Dimech wrote:
>
> > What usually happens in that I make a mistake in my emacs
> > init file and emacs complains. If after loading emacs,
> > I call (setq debug-on-error t), would the debug on the
> > loading error work? Or would I need ho have (setq
> > debug-on-error t) before emacs is called.
>
> I'm not following, sorry...

Suppose I run the command "emacs" on a terminal and there is a problem in my init file.

If I want to debug the error, could I enable (setq debug-on-error t) from emacs.
Or would I have to include (setq debug-on-error t) in my init file before calling
"emacs" on the terminal?


> Correct the mistake without involving the debugger is what
> I would do, anyway.

Or course, if one can.

> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>



  reply	other threads:[~2020-12-24  6:48 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-6e0c3f0c-1681-46ed-9723-a5ca8cfc9e2b-1608792479931@3c-app-mailcom-bs02 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.