From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, nrichard@ulb.ac.be,
Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: Debugging Emacs
Date: Mon, 07 Dec 2015 12:18:43 -0600 [thread overview]
Message-ID: <86twnuf7gc.fsf@stephe-leake.org> (raw)
In-Reply-To: <837fkqdxq7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 07 Dec 2015 18:34:08 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Probably, etc/DEBUG needs to be replaced with a section in the elisp
>> manual.
>
> Somebody already mentioned that. I don't think I agree: when you
> debug, you need the instructions be available on the simplest medium
> possible, so a plain text file is better than Info. What's more
> important, a single file with a distinct name is easier found than a
> section in a large manual.
It would be very rare to have no working Emacs available to read an info
manual.
Perhaps a short summary in etc/DEBUG, with more complete description in
the manual?
--
-- Stephe
next prev parent reply other threads:[~2015-12-07 18:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 17:23 Debugging Emacs Phillip Lord
2015-11-27 17:48 ` Karl Fogel
2015-11-27 21:53 ` Phillip Lord
2015-11-28 7:50 ` Eli Zaretskii
2015-11-27 17:58 ` Eli Zaretskii
2015-11-27 18:15 ` Eli Zaretskii
2015-11-27 22:05 ` Phillip Lord
2015-11-28 7:56 ` Eli Zaretskii
2015-11-28 19:39 ` Phillip Lord
2015-11-28 20:38 ` Eli Zaretskii
2015-11-28 21:35 ` Phillip Lord
2015-11-29 18:13 ` Stephen Leake
2015-11-29 19:25 ` John Wiegley
2015-11-29 21:26 ` Phillip Lord
2015-11-29 19:46 ` Marcin Borkowski
2015-11-30 13:33 ` Nicolas Richard
2015-12-05 10:55 ` Eli Zaretskii
2015-12-07 9:51 ` Phillip Lord
2015-12-07 16:34 ` Eli Zaretskii
2015-12-07 18:18 ` Stephen Leake [this message]
2015-12-07 18:30 ` Eli Zaretskii
2015-12-10 22:36 ` Phillip Lord
2015-12-11 7:39 ` Eli Zaretskii
2015-12-11 15:47 ` Phillip Lord
2015-11-28 8:41 ` Marcin Borkowski
2015-11-28 9:47 ` 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=86twnuf7gc.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nrichard@ulb.ac.be \
--cc=phillip.lord@russet.org.uk \
/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.