all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Martin Barth <martin@senfdax.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs on cygwin, hangs on startup
Date: Mon, 11 Feb 2008 11:22:37 +0100	[thread overview]
Message-ID: <30BD07B3-596C-4130-8044-7F7CB71E85C6@Web.DE> (raw)
In-Reply-To: <28e3d8b6b55aca0dda6fafbb2f80c65e@senfdax.de>


Am 11.02.2008 um 10:45 schrieb Martin Barth:

> if i start emacs with -q it starts normally.
>
> can you give me any hints how i can fix it?

This means that something in your init file, ~/.emacs, is not OK (see  
'emacs --help'). What you can do is edit this file (for example in  
GNU Emacs launched with -q or -Q) and comment one half. Save (and  
stay in this editor to be able to simply undo the previous change).  
Launch GNU Emacs. If it comes up, then the error is in the commented  
half. If it does not come up, then the error is in the uncommented  
half. By further dividing the faulty region (which can mean to undo  
previous comments and then comment the fine one and one half of the  
un-commented region) you'll reach the line with the faulty statement.

You can also try to add at the init file's beginning:

	(setq debug-on-error t)

This could make GNU Emacs launch and display a *Backtrace* buffer.  
It's lines will be truncated. M-x toggle-truncate-lines RET will un- 
clip them. Sometimes you don't need to do this, then you might see a  
text that points to a particular character position. Then it's very  
easy to find the error:

	M-x goto-char RET <the number> RET

--
Greetings

   Pete

There are three types of people in this world: those who can count,  
and those who cannot.






      reply	other threads:[~2008-02-11 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11  9:45 emacs on cygwin, hangs on startup Martin Barth
2008-02-11 10:22 ` Peter Dyballa [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30BD07B3-596C-4130-8044-7F7CB71E85C6@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=martin@senfdax.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.