From: merlyn@stonehenge.com (Randal L. Schwartz)
To: 5946@debbugs.gnu.org
Subject: bug#5946: current HEAD fails "emacs -Q" on OSX command-line
Date: Wed, 14 Apr 2010 07:55:38 -0700 [thread overview]
Message-ID: <86aat6nkwl.fsf@red.stonehenge.com> (raw)
Repeat by:
emacs -Q
Aborts with
Fatal error (10)
then core dumps.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
next reply other threads:[~2010-04-14 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 14:55 Randal L. Schwartz [this message]
2010-04-14 16:51 ` bug#5946: current HEAD fails "emacs -Q" on OSX command-line Eli Zaretskii
2010-04-14 17:03 ` Randal L. Schwartz
2010-04-14 18:16 ` Eli Zaretskii
2010-04-14 18:43 ` Randal L. Schwartz
2010-04-14 19:05 ` Randal L. Schwartz
2010-04-14 20:16 ` Eli Zaretskii
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=86aat6nkwl.fsf@red.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=5946@debbugs.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).