From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Third Newsgroups: gmane.emacs.devel Subject: Re: Emacs on macOS Date: Sun, 3 Apr 2022 14:45:26 +0100 Message-ID: References: <0CBBB7FB-1D2A-46C7-90C2-8664913B0E29@icloud.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39373"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Perry Smith Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 03 15:46:30 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nb0Yn-000A4B-RD for ged-emacs-devel@m.gmane-mx.org; Sun, 03 Apr 2022 15:46:29 +0200 Original-Received: from localhost ([::1]:45548 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nb0Ym-0007rU-Po for ged-emacs-devel@m.gmane-mx.org; Sun, 03 Apr 2022 09:46:28 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:36338) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nb0Xz-0007Ba-LA for emacs-devel@gnu.org; Sun, 03 Apr 2022 09:45:40 -0400 Original-Received: from outbound.soverin.net ([116.202.126.228]:52325) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nb0Xt-0001sq-Gv for emacs-devel@gnu.org; Sun, 03 Apr 2022 09:45:36 -0400 Original-Received: from smtp.soverin.net (unknown [10.10.3.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id 022A0D1; Sun, 3 Apr 2022 13:45:29 +0000 (UTC) Original-Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.99]) by soverin.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=idiocy.org; s=soverin; t=1648993528; bh=YMZ43kyBES17/t121ljvOAasL/KV2CjexMFnhWsJlFI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=F4ZAC1+aJyq1w7Fi/USiacjGmSENtYRWzoHhuho18taPWzPnrSlEqTuM8wdDLDZi6 6pInfkAPxdtF67TFhAd+eqmFhvWCzwatK+mKCOLW7vil0r84McYWBd/KLzHPMPjldz vh0fHfNbUcxvEEjLxCR/iOihx72ZRcTSfEYtapC/6jVpvU3Fgdg0Tq3hYyKP18qXMt cdKIhwMb2LyZVIMRpB10ac+X/rLVzSYXr8kAU911o7M7UXSnwUanTNB4MSPUArIzNB p57o0rSa9eHF3KpuBptAa3NfGfzMC8RFkpm+7An/CEshVo6vbYFcgmt/Mi74XGDkVH DUq923XowTmyg== Original-Received: from alan by faroe.holly.idiocy.org with local (Exim 4.95) (envelope-from ) id 1nb0Xm-000K8Q-Pw; Sun, 03 Apr 2022 14:45:26 +0100 Mail-Followup-To: Alan Third , Perry Smith , emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: <0CBBB7FB-1D2A-46C7-90C2-8664913B0E29@icloud.com> Received-SPF: pass client-ip=116.202.126.228; envelope-from=alan@idiocy.org; helo=outbound.soverin.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:287735 Archived-At: On Thu, Mar 31, 2022 at 05:52:01PM -0500, Perry Smith wrote: > When emacs dies on a Mac (as with any application), a GUI window > pops up with a place to enter some text and a button that says > “Report”. When the button is hit, something sends something > somewhere but I doubt if anything is sent to the emacs-bug list. The > window appears to have some pretty useful information like stack > trace for each thread, etc. > > The flip side is, report-emacs-bug also has a lot of useful > information. My question is what is the preferred or most effective > way to combine these two sources of information? One choice is to > copy what is in the macOS window and paste it into the email that > report-emacs-bug creates. Another choice might be to attach a file > that macOS creates when an application dies but I don’t know where > that file lives. I'd suggest your copy/paste option. Or if the output from the macOS window is very large attach it as a file. The output from the macOS window can be of no use or a lot of use, depending on what caused the crash, and sometimes how the build has been done, but it's usually better than nothing. -- Alan Third