all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: poppyer <poppyer@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Prevent Info Screen on Emacs Startup
Date: 08 Jun 2007 15:48:41 +0100	[thread overview]
Message-ID: <0fr6om8pti.fsf@clpc78.comlab> (raw)
In-Reply-To: 87odjq8q46.fsf@lion.rapttech.com.au

I think somebody has point out the solution several days ago
add this to .emacs file


;; Supress the GNU startup message
(setq inhibit-startup-message t)


Tim X <timx@nospam.dev.null> writes:

> Ken Goldman <kgold@watson.ibm.com> writes:
> 
> > My standard answer to startup complaints is to use the emacs client/server
> > model.  Start up emacs once and then leave it running forever as a server.
> > Edit new files using the emacs client.
> >
> > This solves all the typical "slow startup" complaints as well as your splash
> > screen issue.
> >
> 
> Using the emacs client stuff is good. However, to answer the OPs original
> question, you can disable the splash screen with a command line switch (I think
> it might be -no-splash or something similar). 
> 
> You can probably get rid of it through customize or X resources as well.
> However, I'm not sure as I've never bothered (because I don't start emacs that
> often - leave it running for weeks at a time).
> 
> Tim
> 
> > Joe Hesse wrote:
> >> I have emacs 22.0.990.1.  Using Fedora 7 with Gnome.
> >>
> >> When I start emacs from a command shell under Gnome, like:
> >> $ emacs myfile.txt &
> >> the emacs editor starts with an info screen.  I can get rid of the info
> >> screen with ctrl-l.
> >>
> >> I would prefer that this info screen not be there and I am immediately
> >> editing myfile.txt.  How do I do this?
> 
> -- 
> tcross (at) rapttech dot com dot au

-- 

      reply	other threads:[~2007-06-08 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 20:09 Prevent Info Screen on Emacs Startup Joe Hesse
2007-06-06 20:27 ` Robert D. Crawford
2007-06-08 13:09 ` Ken Goldman
2007-06-08 14:42   ` Tim X
2007-06-08 14:48     ` poppyer [this message]

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=0fr6om8pti.fsf@clpc78.comlab \
    --to=poppyer@gmail.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.
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.