all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs startup: how to get rid of compile window despite of warnings
Date: Wed, 22 Mar 2017 23:08:34 +0100	[thread overview]
Message-ID: <yw.86inn1hsm5.fsf@zoho.com> (raw)
In-Reply-To: 8cd89045-b012-6389-8264-5aab7796a049@openmailbox.org

Krishnakant wrote:

> I have seen some answers for my question on
> stack overflow and the likes.

OK, but just what is your question exactly?

> But all of them have the solution to kill the
> compile buffer only when there are no errors
> and no warnings.

There is probably a miscommunication
(terminology) issue here.

The *compilation* buffer is what pops up when
you compile code in Emacs. You don't want to
automatically close this, especially not when
it reports warnings.

> But I have a different requirement.
>
> I wish that the compile buffer closes even if
> there are just warnings.

Here is some work on the debugger to make it
less noisy. You can fine tune it to not report
certain very harmless "errors". But just so not
have you confused this is an all-Emacs thing
that does not apply only to when Emacs starts!

    http://user.it.uu.se/~embe8573/conf/emacs-init/error.el

Also, this is a matter of suppressing certain
errors which you don't consider errors.
It isn't suppressing ALL errors which isn't
a sound attitude.

> This I need to have when emacs starts.
>
> Which is the right hook to call is one part
> and how do I exactly kill the buffer is
> another one.

It is a better attitude to find out what
warnings you get and solve them one by one.
This makes you a better programmer with
a better system.

Here is some more init stuff that might help
you or give you some ideas what to do:

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

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

For `inhibit-startup-echo-area-message', use
your username, I think what is in
`user-login-name'. But you should spell it out.

-- 
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
                   - so far: 69 Blogomatic articles -                   
                with: #moasen @ irc.freenode.net 6667                    




      reply	other threads:[~2017-03-22 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 20:06 emacs startup: how to get rid of compile window despite of warnings Krishnakant
2017-03-22 22:08 ` Emanuel Berg [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=yw.86inn1hsm5.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.
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.