unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Is there a setting that makes emacs begin editing the init.el file on startup?
Date: Thu, 04 Jan 2018 19:32:38 +0100	[thread overview]
Message-ID: <86h8s1cw55.fsf@zoho.com> (raw)
In-Reply-To: d60d00db-3f1f-4176-983c-eac773515c5b@googlegroups.com

Jonathon McKitrick wrote:

> I'm consolidating my configs across machines,
> and now every time I start the machine, instead
> of getting the empty scratch buffer, I see my
> init.el.

This happens because of something you did while
"consolidating configs across machines". (One
way to do that BTW is to have one file and the
push it across the system.)

Are you still invoking Emacs the standard way
or do you pass it any creative arguments?

If no, start examining the init files. If what
you see first thing is init.el, then search
your init files for any references to
that file.

> I've experimented with the 'inhibit' settings
> for startup messages, but nothing is getting me
> back to the blank scratch buffer.

Well, you can get to it manually but you
shouldn't have to.

This

    $ emacs -Q -eval '(setq inhibit-startup-screen t)'

should get you to the scratch buffer.
Any problems for normal invocation are in your
init files. Do a "binary search" (comment-out
in halfs over and over to locate the error) if
need be.

BTW here is what I do - but that's the other
way around, as I don't want the scratch
buffer :)

;; no fanfare / init
(setq inhibit-startup-screen t)
(setq inhibit-startup-echo-area-message "incal")
(setq byte-compile-verbose nil)

;; scratch buffer
(setq initial-scratch-message nil)
(kill-buffer "*scratch*")

-- 
underground experts united
http://user.it.uu.se/~embe8573


  reply	other threads:[~2018-01-04 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 17:40 Is there a setting that makes emacs begin editing the init.el file on startup? Jonathon McKitrick
2018-01-04 18:32 ` Emanuel Berg [this message]
2018-01-05 13:40 ` Tim Visher
2018-01-05 13:46   ` jmckitrick
2018-01-05 13:50     ` Tim Visher

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=86h8s1cw55.fsf@zoho.com \
    --to=moasen@zoho.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).