all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
Subject: Re: Emacs 22 problems with split init file
Date: Tue, 16 Jan 2007 08:50:55 +1100	[thread overview]
Message-ID: <87mz4kufgg.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.3068.1168856053.2155.help-gnu-emacs@gnu.org

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

> Am 15.01.2007 um 07:42 schrieb Tim X:
>
>> However, I do suspect it is something
>> related to the customize stuff which is causeing the seg faults.
>
> How about putting
>
> 	(message "From <this or that> custom file starts here")
> 	(message "From <this or that> custom file ends here")
>
> into your custom files? (You can also put some into ~/.emacs.) It's  only
> useful when you're able to to see the *Messages* buffer, so it  could be a good
> idea to comment the whole block of settings starting  with
>
> 	(custom-set-variables
>
> and ending with ``)´´ and see whether this leads to no crashes. Then  uncomment
> the first and the last line of customisation, to have a  valid ELisp statement,
> and see whether it's still OK. Next comes a  loop of binary dividing the
> customisation, i.e., finding the  increasingly smaller region with the faulty
> setting in it ...
>
> --

Hi Pete,

I've already tried that. The custom file (the correct one for the version of
emacs i.e. 22) is getting loaded and all the customization seems correct. In
fact, there don't seem to be any problems after starting emacs. However, when
you go to do certain operations after emacs has booted, such as start a mail
reading client, you will go to perform some operation and emacs crashes with
the segfault error. As soon as you use just a single init file, there are no
problems. 

I'll keep experimenting and see what happens. I have considerable amounts of
custom stuff and eliminating them in a methodical way is time consuming. 

Tim

-- 
tcross (at) rapttech dot com dot au

  parent reply	other threads:[~2007-01-15 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14  7:36 Emacs 22 problems with split init file Tim X
2007-01-14 11:14 ` Peter Dyballa
     [not found] ` <mailman.3046.1168773302.2155.help-gnu-emacs@gnu.org>
2007-01-15  6:42   ` Tim X
2007-01-15 10:14     ` Peter Dyballa
     [not found]     ` <mailman.3068.1168856053.2155.help-gnu-emacs@gnu.org>
2007-01-15 21:50       ` Tim X [this message]
2007-01-15 23:27         ` Peter Dyballa

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=87mz4kufgg.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    /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.