* emacs startup: how to get rid of compile window despite of warnings
@ 2017-03-19 20:06 Krishnakant
2017-03-22 22:08 ` Emanuel Berg
0 siblings, 1 reply; 2+ messages in thread
From: Krishnakant @ 2017-03-19 20:06 UTC (permalink / raw)
To: help-gnu-emacs@gnu.org
Dear all,
I have seen some answers for my question on stack overflow and the likes.
But all of them have the solution to kill the compile buffer only when
there are no errors and no warnings.
But I have a different requirement.
I wish that the compile buffer closes even if there are just warnings.
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.
I have already set Emacs to show active buffer in full screen mode and
also inhibited the default tutorial from coming up in a buffer.
I did all this using customize-group emacs and in that I used the group
for init.
Now can some one just give me an idea of how to get this last one bit right?
Happy hacking.
Krishnakant.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: emacs startup: how to get rid of compile window despite of warnings
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
0 siblings, 0 replies; 2+ messages in thread
From: Emanuel Berg @ 2017-03-22 22:08 UTC (permalink / raw)
To: help-gnu-emacs
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-03-22 22:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).