unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: Debugging Emacs
Date: Sat, 28 Nov 2015 09:56:43 +0200	[thread overview]
Message-ID: <83h9k6r1z8.fsf@gnu.org> (raw)
In-Reply-To: <87lh9jp073.fsf@russet.org.uk>

> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: <emacs-devel@gnu.org>
> Date: Fri, 27 Nov 2015 22:05:52 +0000
> 
> With etc/DEBUG, I am worried not about what it does not say, but what it
> does say. It's really very dense.

It is written from the POV of someone who is way beyond basic
debugging techniques, and needs only the Emacs-specific information.
Once upon a time, only people matching that description "dared" to
debug Emacs on the C level.  This file was born back then.

> > More specifically, how about a preamble section at the beginning of
> > etc/DEBUG, named something like "If you are new to debugging Emacs",
> > and describing the preliminaries you think are important?  You can
> > refer to later sections instead of repeating what they say.
> 
> Yes, that was sort of the idea. Personally, I'd not be too worried about
> repeating things. I realise that this adds to the maintainance burden,
> but references to later sections make for harder reading.

It is OK to say something simple in the preamble, and refer to later
sections for more in-depth detail.

But I will now stop writing comments to a text I didn't yet see, and
let you work on it instead ;-)

> I'll try and simplify what I wrote a bit further.

Thanks.



  reply	other threads:[~2015-11-28  7:56 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 [this message]
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
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

  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=83h9k6r1z8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 public inbox

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

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).