From: Noah Sussman <nsussman@mdsol.com>
To: Radon Rosborough <radon.neon@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: bug#26323: 25.1; Closing frames (in fullscreen) under Mac OS cause immediate crash
Date: Fri, 13 Jul 2018 16:25:45 -0400 [thread overview]
Message-ID: <CAK7SkjNMd941Kr=QEnKgdT1Pm2=K6O-rW0FOm+NqP+3D2mPYNQ@mail.gmail.com> (raw)
In-Reply-To: <CADB4rJFJgcFznahwGf8-gEa5k6bpLfgrfqoVckiszEhm3sbZqQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Thu, Jul 12, 2018 at 10:16 PM, Radon Rosborough <radon.neon@gmail.com>
wrote:
> > brew edit cask emacs
>
> Do you perhaps mean 'brew cask edit' rather than 'brew edit cask'?
>
The quoted command is the one I used.
It may not be optimal or there may be a more idiomatic Homebrew way to do
it, but I have looked at my .history file and here are all 3 commands I
used to get Emacs to stop crashing when closing a fullscreen window:
brew cask install emacs
brew edit cask emacs
# change the ctags as described above
brew reinstall cask emacs
I did try the other way round:
brew cask edit emacs
and it opens a different file, not the right file to put that ctags change
in!!!
[-- Attachment #2: Type: text/html, Size: 1225 bytes --]
next prev parent reply other threads:[~2018-07-13 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 20:52 bug#26323: 25.1; Closing frames (in fullscreen) under Mac OS cause immediate crash Noah Sussman
2018-07-12 20:51 ` Alan Third
2018-07-13 2:16 ` Radon Rosborough
2018-07-13 20:25 ` Noah Sussman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-16 0:54 Matthew Bauer
2018-03-16 10:47 ` Alan Third
2018-03-16 18:12 ` David Reitter
2018-03-18 11:15 ` Alan Third
2018-03-18 11:17 ` David Reitter
2018-03-18 11:30 ` Alan Third
2018-03-18 18:14 ` John Wiegley
2018-03-18 20:14 ` Alan Third
2018-03-19 0:37 ` Nick Helm
2018-03-19 12:29 ` Alan Third
2018-03-19 2:05 ` Matthew Bauer
2018-03-19 12:23 ` Alan Third
2018-03-20 1:05 ` John Wiegley
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='CAK7SkjNMd941Kr=QEnKgdT1Pm2=K6O-rW0FOm+NqP+3D2mPYNQ@mail.gmail.com' \
--to=nsussman@mdsol.com \
--cc=emacs-devel@gnu.org \
--cc=radon.neon@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).