unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Chong Yidong <cyd@gnu.org>
Cc: "11395@debbugs.gnu.org" <11395@debbugs.gnu.org>,
	Richard Stanton <stanton@haas.berkeley.edu>
Subject: bug#11395: 24.0.96; Sporadic crashing
Date: Tue, 15 May 2012 18:17:13 +0200	[thread overview]
Message-ID: <A50702F0-849D-444F-B433-C14FD49D0C49@swipnet.se> (raw)
In-Reply-To: <87k40d79sv.fsf@gnu.org>

Hello.

15 maj 2012 kl. 17:17 skrev Chong Yidong:

> Richard Stanton <stanton@haas.berkeley.edu> writes:
> 
>> 1) When run this way, where does Emacs look by default for my own .el
>> files? Normally I put them under
>> /Applications/Emacs.app/Contents/Resources/site-lisp, which Emacs
>> under OS X searches (along with all subdirectories) automatically.
> 
> It should not make any difference.
> 
>> 2) When I type a key in the resulting Emacs window, the character I
>> just typed appears in the shell window, not the Emacs window. How do I
>> get around that?
> 
> I have no idea what this means; I haven't heard of such a problem
> before.  Maybe someone else who has used Emacs on Mac OS X can help.
> 
> 

You should cd to src and then start gdb like this:

% gdb ../nextstep/Emacs.app/Contents/MacOS/Emacs

not use the emacs that is in src.

Emacs can't find its resources otherwise, and isn't properly initialized.

	Jan D.






  reply	other threads:[~2012-05-15 16:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 20:37 bug#11395: 24.0.96; Sporadic crashing Richard Stanton
     [not found] ` <handler.11395.B.133599119221506.ack@debbugs.gnu.org>
2012-05-02 20:48   ` bug#11395: Acknowledgement (24.0.96; Sporadic crashing) Richard Stanton
2012-05-03 22:15   ` bug#11395: 24.0.96; Sporadic crashing Richard Stanton
2012-05-04  2:25     ` Chong Yidong
2012-05-05  4:17     ` Chong Yidong
2012-05-05  4:21       ` Richard Stanton
2012-05-05  4:45         ` Chong Yidong
2012-05-05  6:40           ` Richard Stanton
2012-05-11 13:22           ` Chong Yidong
2012-05-11 15:21             ` Richard Stanton
2012-05-11 17:26               ` Chong Yidong
2012-05-11 18:09                 ` Richard Stanton
2012-05-12  6:35                   ` Chong Yidong
2012-05-14 20:45                     ` Richard Stanton
2012-05-15 15:17                       ` Chong Yidong
2012-05-15 16:17                         ` Jan Djärv [this message]
2012-05-15 16:23                           ` Jan Djärv
2012-05-15 17:48                             ` Richard Stanton
2012-05-16 16:48                     ` Richard Stanton
2012-05-17  9:10                       ` Chong Yidong
2012-05-19  6:24                         ` Paul Eggert
2012-05-17 12:00                       ` Chong Yidong
2012-05-17 16:35                         ` Richard Stanton
2015-12-25 23:14                           ` Lars Ingebrigtsen
2015-12-26  1:01                             ` Richard Stanton

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=A50702F0-849D-444F-B433-C14FD49D0C49@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=11395@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    --cc=stanton@haas.berkeley.edu \
    /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).