unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Install C source code for for debugging help
Date: Fri, 27 Sep 2019 10:37:06 +0200	[thread overview]
Message-ID: <878sqannil.fsf@igel.home> (raw)
In-Reply-To: <1cb04f23-5fa1-c866-41a8-60156d15936d@cs.ucla.edu> (Paul Eggert's message of "Thu, 26 Sep 2019 23:13:15 -0700")

On Sep 26 2019, Paul Eggert <eggert@cs.ucla.edu> wrote:

> We need it because the feature in question is not working on Debian, or on
> Red Hat, or on any other GNU/Linux distribution that I know of. It's all
> very well to say that the user can change the source-directory variable to
> some random location and then download a correct copy of the right version
> of the Emacs source to that location, but that can be a tricky thing to do
> correctly when the same home directory is shared by multiple Emacs
> versions (which is common for me, at least).

Emacs should be taught to find its sources in the debug source
directory, where emacs-debugsource (or its equivalent) installs them.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."



  parent reply	other threads:[~2019-09-27  8:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 20:37 Install C source code for for debugging help Paul Eggert
2019-09-27  5:07 ` Eli Zaretskii
2019-09-27  6:13   ` Paul Eggert
2019-09-27  7:19     ` Eli Zaretskii
2019-09-27 13:01       ` Stefan Monnier
2019-09-27 13:12         ` Stefan Monnier
2019-09-27 13:33         ` Eli Zaretskii
2019-09-27 13:48           ` Stefan Monnier
2019-09-27 13:56             ` Eli Zaretskii
2019-09-27 14:24               ` Paul Eggert
2019-09-27 14:40                 ` Eli Zaretskii
2019-09-28  4:03                   ` Paul Eggert
2019-09-27 17:04                 ` Noam Postavsky
2019-09-27 22:45                   ` Fu Yuan
2019-09-28  0:09                     ` Juanma Barranquero
2019-09-28  2:14                     ` Michael Rohleder
2019-09-27 15:25               ` Stefan Monnier
2019-09-28  1:32                 ` Richard Stallman
2019-09-28  2:06                   ` Jean-Christophe Helary
2019-09-27 15:03             ` Lars Ingebrigtsen
2019-09-27 15:47             ` David Ringo
2019-09-27  8:37     ` Andreas Schwab [this message]
2019-09-27  9:06       ` Eli Zaretskii
2019-09-27 11:58         ` Andreas Schwab
2019-09-27 12:58           ` Eli Zaretskii
2019-09-27 13:45             ` Andreas Schwab
2019-09-27 13:50               ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2019-09-28 18:19 Angelo Graziosi
2019-09-29  6:56 ` Paul Eggert

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=878sqannil.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).