unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Baloff <washdc@wash.edu>
Subject: Re: default startup mode
Date: 07 Aug 2005 09:37:29 +1000	[thread overview]
Message-ID: <873bpmy6va.fsf@wash.edu> (raw)
In-Reply-To: mailman.2587.1123169657.20277.help-gnu-emacs@gnu.org

Kevin Rodgers <ihs_4664@yahoo.com> writes:

> Baloff wrote:
> 
>  > I have this line in my .emacs
>  >
>  > (setq default-major-mode 'text-mode)	;new buffers are text mode
>  >
>  > when I start emacs, it opens up a scratch buffer in (Lisp Interaction)
>  > in the mode line. shouldn't that be text mode since the line above is
>  > in the .emacs.
>  > if not, how do I get emacs to start up with text mode as default? or
>  > should I?
> 
> ,----[ C-h v initial-major-mode RET ]
> | initial-major-mode's value is
> | lisp-interaction-mode
> |
> | Documentation:
> | Major mode command symbol to use for the initial *scratch* buffer.
> |
> | You can customize this variable.
> |
> | Defined in `startup'.
> `----
> 
> -- 
> Kevin Rodgers

thanks, 
I went looking for info about startup and found

Initial Options
===============

...
   Some initial options affect the loading of init files.  The normal
actions of Emacs are to first load `site-start.el' if it exists, then
your own init file `~/.emacs' if it exists, and finally `default.el' if
it exists; certain options prevent loading of some of these files or
substitute other files for them.


how do I find out if "in my case" all 3 files started up or any did
not.

  parent reply	other threads:[~2005-08-06 23:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 22:38 default startup mode Baloff
2005-08-04 15:19 ` Kevin Rodgers
2005-08-06 18:13   ` Christian Plate
2005-08-06 18:53     ` Peter Dyballa
     [not found]     ` <878xzf7x3b.fsf-f2P8RtOhboYi5CQI31g/s0B+6BGkLq7r@public.gmane.org>
2005-08-06 18:58       ` Jochen Küpper
     [not found] ` <mailman.2587.1123169657.20277.help-gnu-emacs@gnu.org>
2005-08-06 23:37   ` Baloff [this message]
2005-08-08 19:32     ` Kevin Rodgers

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=873bpmy6va.fsf@wash.edu \
    --to=washdc@wash.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.
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).