unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Phil Brown <p.brown.phil@gmail.com>
Cc: 45900-done@debbugs.gnu.org
Subject: bug#45900: 28.0.50; [PATCH] [native-comp] Improve backtraces from async workers
Date: Sat, 16 Jan 2021 12:40:50 +0000	[thread overview]
Message-ID: <xjf35z112ct.fsf@sdf.org> (raw)
In-Reply-To: <CANOp0OgfheBMAZBUpsp46YLAXOp3J1WxpaGncG-RO9FqJ81bBQ@mail.gmail.com> (Phil Brown's message of "Fri, 15 Jan 2021 10:19:37 -0800")

Phil Brown <p.brown.phil@gmail.com> writes:

> Hi bug list,
>
> I've been happily using the native-comp branch and it works well. Attached is a tiny change to set
> `backtrace-line-length' in comp.el's async workers. I was debugging a few failed compilations and had run `(setq
> backtrace-line-length 0)` in an attempt to see the full path of the offending files (turned out to be autoloads). The
> setting was having no effect on the async compile errors and I realized the batch-mode worker processes weren't
> inheriting it.
>
> I haven't signed CA papers since this change is so small, but am happy to if that's needed.
>
> Thanks!
> -Phil

Hi Phil,

thanks for the patch!  In as 88100bed0a.

My suggestion would be to do the CA paperwork anyway as might be handy
for the future :)

Closing

Thanks

  Andrea





      reply	other threads:[~2021-01-16 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 18:19 bug#45900: 28.0.50; [PATCH] [native-comp] Improve backtraces from async workers Phil Brown
2021-01-16 12:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=xjf35z112ct.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=45900-done@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=p.brown.phil@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 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).