Error Dismissing Startup Screen

Error Dismissing Startup Screen

[eabod]

Hi,

I'm using emacs with Ubuntu 8.10 (both of which are entirely new to me).
When I check the "Never show it again" box for the startup screen, and click
the "Dismiss this startup screen" link, i get the following error message:

"Cannot save customizations; init file was not fully loaded".

How can I remedy this?

Thanks.quinnculver@gmail.com
-- 
View this message in context: http://www.nabble.com/Error-Dismissing-Startup-Screen-tp21839889p21839889.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: Error Dismissing Startup Screen

[Peter Dyballa]

Am 04.02.2009 um 22:21 schrieb eabod:

> "Cannot save customizations; init file was not fully loaded".
>
> How can I remedy this?


Try launch GNU Emacs as 'emacs --debug-init' and correct your init  
file according to the messages in *Backtrace* buffer! This file  
obviously is faulty ...

--
Greetings

   Pete

If you're not confused, you're not paying attention.

Re: Error Dismissing Startup Screen

[eabod]

Pete,

I typed 'emacs --debug-init' into my terminal and emacs started with a blank
screen. Under the Buffers menu were only '*scratch*' and '*Messages*',  no
'*Backtrace*'. Any ideas?

Do I need to create an init file?


Peter Dyballa wrote:
> 
> 
> Am 04.02.2009 um 22:21 schrieb eabod:
> 
>> "Cannot save customizations; init file was not fully loaded".
>>
>> How can I remedy this?
> 
> 
> Try launch GNU Emacs as 'emacs --debug-init' and correct your init  
> file according to the messages in *Backtrace* buffer! This file  
> obviously is faulty ...
> 
> --
> Greetings
> 
>    Pete
> 
> If you're not confused, you're not paying attention.
> 
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Error-Dismissing-Startup-Screen-tp21839889p21860253.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: Error Dismissing Startup Screen

[Peter Dyballa]

Am 05.02.2009 um 21:19 schrieb eabod:

> I typed 'emacs --debug-init' into my terminal and emacs started  
> with a blank
> screen. Under the Buffers menu were only '*scratch*' and  
> '*Messages*',  no
> '*Backtrace*'. Any ideas?
>
> Do I need to create an init file?
>>
>>
>> Am 04.02.2009 um 22:21 schrieb eabod:
>>
>>> "Cannot save customizations; init file was not fully loaded".
>>>
>>> How can I remedy this?


I understand now! Since you do not have an init file, GNU Emacs can't  
save any customisation. Obviously the message you cited is a bit  
misleading – maybe it's worth to report it as a bug (see Help menu)  
that it gets corrected to report that no init file exists and a file  
name is needed (and GNU Emacs should suggest names) to save the  
customisation.

Maybe it helps to create with a 'touch ~/.emacs' an empty init file,  
launch GNU Emacs again, redo the customisation, and then save it.

So you have an answer to your latest question: yes, you need an init  
file to save customisation.

--
Greetings

   Pete

There is no national science just as there is no national  
multiplication table; what is national is no longer science.
				– Anton Checov

Re: Error Dismissing Startup Screen

[eabod]

How do I create the needed init file and in which dirctory does it belong?


Peter Dyballa wrote:
> 
> 
> Am 05.02.2009 um 21:19 schrieb eabod:
> 
>> I typed 'emacs --debug-init' into my terminal and emacs started  
>> with a blank
>> screen. Under the Buffers menu were only '*scratch*' and  
>> '*Messages*',  no
>> '*Backtrace*'. Any ideas?
>>
>> Do I need to create an init file?
>>>
>>>
>>> Am 04.02.2009 um 22:21 schrieb eabod:
>>>
>>>> "Cannot save customizations; init file was not fully loaded".
>>>>
>>>> How can I remedy this?
> 
> 
> I understand now! Since you do not have an init file, GNU Emacs can't  
> save any customisation. Obviously the message you cited is a bit  
> misleading – maybe it's worth to report it as a bug (see Help menu)  
> that it gets corrected to report that no init file exists and a file  
> name is needed (and GNU Emacs should suggest names) to save the  
> customisation.
> 
> Maybe it helps to create with a 'touch ~/.emacs' an empty init file,  
> launch GNU Emacs again, redo the customisation, and then save it.
> 
> So you have an answer to your latest question: yes, you need an init  
> file to save customisation.
> 
> --
> Greetings
> 
>    Pete
> 
> There is no national science just as there is no national  
> multiplication table; what is national is no longer science.
> 				– Anton Checov
> 
> 
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Error-Dismissing-Startup-Screen-tp21839889p21864014.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: Error Dismissing Startup Screen

[Mike Treseler]

eabod wrote:
> How do I create the needed init file

touch ~/.emacs

> in which directory does it belong?

That's the ~/ part

or, if you prefer

cd $HOME
touch .emacs

Re: Error Dismissing Startup Screen

[Glenn Morris]

Peter Dyballa wrote:

> I understand now! Since you do not have an init file, GNU Emacs can't
> save any customisation.

A 10 second experiment shows this statement is false.

> So you have an answer to your latest question: yes, you need an init
> file to save customisation.

No you don't; one will be created for you.

Re: Error Dismissing Startup Screen

[Joe Schafer]

eabod <quinnculver@gmail.com> writes:

> How do I create the needed init file and in which dirctory does it belong?

You can use ~/.emacs or ~/.emacs.d/init.el, emacs will check for both.

Re: Error Dismissing Startup Screen

[Peter Dyballa]

Am 06.02.2009 um 01:00 schrieb eabod:

> How do I create the needed init file and in which dirctory does it  
> belong?


The info documentation on GNU Emacs describes this. On an UNIX system  
'touch ~/.emacs' would create an empty possible init file.

--
Greetings

   Pete

Isn't vi that text editor with two modes... one that beeps and one  
that corrupts your file?
				– Dan Jacobson, on comp.os.linux.advocacy

Re: Error Dismissing Startup Screen

[eabod]

I actually had a .emacs file in my Home directory all along. So now what
could the problem be?


Peter Dyballa wrote:
> 
> 
> Am 06.02.2009 um 01:00 schrieb eabod:
> 
>> How do I create the needed init file and in which dirctory does it  
>> belong?
> 
> 
> The info documentation on GNU Emacs describes this. On an UNIX system  
> 'touch ~/.emacs' would create an empty possible init file.
> 
> --
> Greetings
> 
>    Pete
> 
> Isn't vi that text editor with two modes... one that beeps and one  
> that corrupts your file?
> 				– Dan Jacobson, on comp.os.linux.advocacy
> 
> 
> 
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Error-Dismissing-Startup-Screen-tp21839889p21879616.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: Error Dismissing Startup Screen

[Barry Margolin]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

In article <mailman.51.1233950246.31690.help-gnu-emacs@gnu.org>,
 eabod <quinnculver@gmail.com> wrote:

> I actually had a .emacs file in my Home directory all along. So now what
> could the problem be?

Maybe there's a permissions problem?

> 
> 
> Peter Dyballa wrote:
> > 
> > 
> > Am 06.02.2009 um 01:00 schrieb eabod:
> > 
> >> How do I create the needed init file and in which dirctory does it  
> >> belong?
> > 
> > 
> > The info documentation on GNU Emacs describes this. On an UNIX system  
> > 'touch ~/.emacs' would create an empty possible init file.
> > 
> > --
> > Greetings
> > 
> >    Pete
> > 
> > Isn't vi that text editor with two modes... one that beeps and one  
> > that corrupts your file?
> > 				– Dan Jacobson, on comp.os.linux.advocacy
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***

Re: Error Dismissing Startup Screen

[Glenn Morris]

eabod wrote:

> I actually had a .emacs file in my Home directory all along. So now what
> could the problem be?

If I were you, I'd just

mv ~/.emacs ~/.emacs.OFF

Optionally, complain to whoever supplied that file.