From: Aaron Meurer <asmeurer@gmail.com>
To: Matt McClure <matthewlmcclure@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
XeCycle <XeCycle@gmail.com>
Subject: Re: First character beeps screen sometimes
Date: Sun, 11 Mar 2012 16:39:53 -0600 [thread overview]
Message-ID: <CAKgW=6JJoMvy1THpwkYk5K_WH62EtB=GaG8bN_DZPAJ2MMHh0g@mail.gmail.com> (raw)
In-Reply-To: <28633185894482899@unknownmsgid>
The answer is (setq inhibit-splash-screen t) (in your .emacs file), in
case anyone is interested.
Aaron Meurer
On Sun, Mar 11, 2012 at 3:43 PM, Matt McClure <matthewlmcclure@gmail.com> wrote:
> M-x apropos RET splash.*screen RET
>
> Matt McClure
> http://matthewlmcclure.com
> http://www.mapmyfitness.com/profile/matthewlmcclure
>
> On Mar 11, 2012, at 11:34 AM, Aaron Meurer <asmeurer@gmail.com> wrote:
>
>> On Sun, Mar 11, 2012 at 2:56 PM, Peter Dyballa <Peter_Dyballa@web.de> wrote:
>>>
>>> Am 11.3.2012 um 18:53 schrieb Matt McClure:
>>>
>>>> --no-site-file would eliminate that variable, correct?
>>>
>>> And only this file. As you wrote your own init file, made non-existing with -q, is OK, so it could be the system's init file that causes beeping. But it can also be that somewhere in the site Lisp directory inappropriate files are lying around. Developing GNU Emacs 24 has more specific options:
>>>
>>> --no-init-file, -q load neither ~/.emacs nor default.el
>>> --no-site-file do not load site-start.el
>>> --no-site-lisp, -nsl do not add site-lisp directories to load-path
>>> --quick, -Q equivalent to:
>>> -q --no-site-file --no-site-lisp --no-splash
>>
>> This is it! --no-splash removes the problem. Apparently, the splash
>> screen is "loaded" even though I can't see it, and takes up the first
>> keypress.
>>
>> Fortunately, this is easy to work-around. I just have to disable the
>> splash screen in my .emacs file. Any idea how to do this btw (I
>> didn't find a setting for it in M-x customize)?
>>
>> Should I M-x report-emacs-bug this?
>>
>> Aaron Meruer
>>
>>>
>>> Anyway, you could use this snippet to record in *Messages* buffer the files that are loaded. This has to be executed at first, maybe directly from the command line:
>>>
>>> (defadvice load (before debug-log activate)
>>> (message "(Tipp von Kai G) Loade now: %s" (ad-get-arg 0)))
>>>
>>>
>>> --
>>> Greetings
>>>
>>> Pete
>>>
>>> Give a man a fish, and you've fed him for a day. Teach him to fish, and you've depleted the lake.
>>>
next prev parent reply other threads:[~2012-03-11 22:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 21:14 First character beeps screen sometimes Aaron Meurer
2012-03-09 21:23 ` Drew Adams
2012-03-09 22:03 ` Aaron Meurer
2012-03-10 7:26 ` XeCycle
2012-03-10 20:47 ` Aaron Meurer
2012-03-10 20:50 ` Aaron Meurer
2012-03-11 3:40 ` Aaron Meurer
2012-03-11 9:02 ` Peter Dyballa
2012-03-11 17:53 ` Matt McClure
2012-03-11 20:56 ` Peter Dyballa
2012-03-11 21:33 ` Aaron Meurer
2012-03-11 21:43 ` Matt McClure
2012-03-11 22:39 ` Aaron Meurer [this message]
2012-03-11 23:47 ` Drew Adams
2012-03-12 0:11 ` Aaron Meurer
2012-03-12 0:31 ` Peter Dyballa
2012-03-12 2:15 ` Aaron Meurer
2012-03-11 23:45 ` Peter Dyballa
2012-03-13 3:01 ` XeCycle
2012-03-13 3:58 ` Aaron Meurer
2012-03-13 4:15 ` Yaoyuan
2012-03-14 11:29 ` XeCycle
2012-03-11 21:09 ` Aaron Meurer
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='CAKgW=6JJoMvy1THpwkYk5K_WH62EtB=GaG8bN_DZPAJ2MMHh0g@mail.gmail.com' \
--to=asmeurer@gmail.com \
--cc=XeCycle@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=matthewlmcclure@gmail.com \
/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).