[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Major mode weirdness.

From: Valentin Plechinger
Subject: Re: Major mode weirdness.
Date: Wed, 13 Jul 2011 20:37:03 +0200
User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.8 Emacs/23.3 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

(setq default-major-mode 'text-mode)
for all new buffers (initial *scratch* buffer is different though)

R. Clayton wrote:
> I am running GNU Emacs 23.3.1 (i486-pc-linux-gnu, GTK+ Version 2.24.3) of
> 2011-04-10 on raven, modified by Debian on a debian testing system updated
> weekly.
> I have noticed that the initial scratch buffer, the one you get when you just
> run emacs with no command-line arguments, is in fundamental mode, even though
> .emacs contains, in custom-set-variables, '(initial-major-mode (quote
> text-mode)) and help-variable in *scratch* reports initial-major-mode's value
> is text-mode.
> What is the error I'm making in trying to get the initial buffer to be in text
> mode?
> I have also noticed that doing (setq major-mode 'text-mode) in .emacs has no
> effect: new buffers are set to fundamental mode rather than text mode.  The
> help-variable documentation for major-mode indicates that setting help-mode
> makes it buffer local, which seems like strange behavior for a variable that's
> supposed to provide a global value.  Setting major-mode in 
> custom-set-variables
> works as expected.
> Although I expect I know the answer to this one, I'll ask it anyway: why is it
> that a "top-level" setq on major-mode in .emacs doesn't work?
> Also, top-level setqs on initial-major-mode and major-mode used to work as
> expected up until a few weeks ago.  What has changed since then?  Searching
> around in the /usr/share/doc/emacs23 change files doesn't produce anything I
> can recognize as an explanation.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]