From: Jude DaShiell <jdashiel@panix.com>
To: Emanuel Berg <moasenwood@zoho.eu>, help-gnu-emacs@gnu.org
Subject: Re: r.f.e. emacs tutorial
Date: Mon, 24 Aug 2020 13:22:57 -0400 [thread overview]
Message-ID: <alpine.NEB.2.23.451.2008241322090.12324@panix1.panix.com> (raw)
In-Reply-To: <87wo1om0ss.fsf@ebih.ebihd>
In internet context request for enhancement similar to R.F.C. request
for comments.
On Mon, 24 Aug 2020, Emanuel Berg via Users list for the GNU Emacs text
editor wrote:
> Date: Mon, 24 Aug 2020 13:05:55
> From: Emanuel Berg via Users list for the GNU Emacs text editor
> <help-gnu-emacs@gnu.org>
> Reply-To: Emanuel Berg <moasenwood@zoho.eu>
> To: help-gnu-emacs@gnu.org
> Subject: Re: r.f.e. emacs tutorial
>
> ... what is "r.f.e.", Radio Free Europe?
>
> Jude DaShiell wrote:
>
> > on the emacs debugger for when .emacs and similar
> > files get messed up how to use emacs --debug to
> > locate problems and repair those problems?
>
> There seems to be no such option as --debug according
> to the man page emacs(1) (GNU Emacs 26.1,
> 2007 April 13 - hm ... that old a man page?)
>
> OTOH, Emacs doesn't report an error on
> $ emacs --debug # maybe because it is a prefix of
> --debug-init, as e.g. --xyz does report
> 'Unknown option'.
>
> (If indeed a prefix thing, it should be dropped IMO.
> Error prone and doesn't look right - by
> definition, even.)
>
> Anyway, keeping up with the man page, it says:
>
> --debug-init
> Enable Emacs Lisp debugger during the process?
> ing of the user init file ~/.emacs. This is
> useful for debugging problems in the init file.
>
> Here,
>
> (info "(emacs) Initial Options")
>
> it says
>
> --debug-init?
> Enable the Emacs Lisp debugger for errors in the init file. *Note
> Entering the Debugger on an Error: (elisp)Error Debugging.
>
> which is a reference to
>
> (info "(elisp) Error Debugging")
>
> where
>
> (how-many "init") ; 4
>
> HIH :)
>
>
--
prev parent reply other threads:[~2020-08-24 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 16:37 r.f.e. emacs tutorial Jude DaShiell
2020-08-24 17:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-24 17:22 ` Jude DaShiell [this message]
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=alpine.NEB.2.23.451.2008241322090.12324@panix1.panix.com \
--to=jdashiel@panix.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.
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).