all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: 22984-done@debbugs.gnu.org
Subject: bug#22984: 25.0.92; Typo in etc/DEBUG
Date: Sat, 12 Mar 2016 10:34:01 +0200	[thread overview]
Message-ID: <83egbggkna.fsf@gnu.org> (raw)
In-Reply-To: <87h9gcemrj.fsf@gmail.com> (nljlistbox2@gmail.com)

> From: nljlistbox2@gmail.com (N. Jackson)
> Cc: 22984@debbugs.gnu.org
> Date: Fri, 11 Mar 2016 17:18:56 -0400
> 
> At 22:27 +0200 on Friday 2016-03-11, Eli Zaretskii wrote:
> >
> > How about the following variant?
> >
> >   This will suggest the file name of the default binary to debug; if
> >   the suggested default is not the Emacs binary you want to debug,
> >   change the file name as needed.
> >
> > (This avoids the potentially confusing word "load", and also makes it
> > clear we are talking about debugging Emacs, not some other program.)
> 
> Yes, that's better. It clearly states its meaning.

Pushed, thanks.

> Did you see the following suggestion in my earlier message. [I wasn't
> sure if you'd missed it, or if you'd decided it wasn't valid.] This was
> with regard to etc/DEBUG not being about the Elisp debugger.

We only mention the Lisp debugger once in the entire file.  I added a
reference to the ELisp manual there.





      reply	other threads:[~2016-03-12  8:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 15:18 bug#22984: 25.0.92; Typo in etc/DEBUG N. Jackson
2016-03-11 15:59 ` Eli Zaretskii
2016-03-11 18:30   ` N. Jackson
2016-03-11 18:39     ` Eli Zaretskii
2016-03-11 19:06       ` N. Jackson
2016-03-11 19:42         ` Eli Zaretskii
2016-03-11 20:12           ` N. Jackson
2016-03-11 20:27             ` Eli Zaretskii
2016-03-11 21:18               ` N. Jackson
2016-03-12  8:34                 ` Eli Zaretskii [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

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

  git send-email \
    --in-reply-to=83egbggkna.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22984-done@debbugs.gnu.org \
    --cc=nljlistbox2@gmail.com \
    /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.