From: Benjamin Rutt <rutt.4+news@osu.edu>
Subject: Re: compiling in C mode and the compilation buffer
Date: Wed, 28 Jul 2004 08:57:15 -0400 [thread overview]
Message-ID: <87y8l4b87o.fsf@osu.edu> (raw)
In-Reply-To: 20040728023945.2d3d1697@localhost
Shug Boabie <no.spam@example.com> writes:
>> excellent, however i would still like the window to remain open upon
>> detection of warnings as well [in order to force me to write ISO C99 code
>> :-)]. i use the compile command exclusively for C code, so a grep for
>> "warning:" should be sufficient. however, my attempts to customise your
>> function have failed. any further hints?
>
> for the record, here is what i have been trying to do, but it is not
> working:
>
> (defun sam-compile (buf str)
> (when (string-match "*compilation.*" (buffer-name buf))
> (if (string-match "exited abnormally" str)
> (progn
> (message "compilation errors, press C-x ` to view"))
> (if (string-match "warning:" str)
> (progn
> (message "compilation warnings, press C-x ` to view"))
> (run-at-time 0.5 nil 'delete-windows-on buf)
> (message "no compile errors or warnings")))))
This won't work because the `str' variable above only gets the last
line output by emacs during a compilation. It will either look like
"Compilation exited abnormally" or "Compilation finished".
I suggest if you really want to treat warnings as errors, you can tell
your compiler to do so. Under gcc, you would pass the -Werror flag
during compilation.
Note, also, that even during successful compilation, you can still do
C-x ` to take you to any warnings that may have occured.
--
Benjamin Rutt
next prev parent reply other threads:[~2004-07-28 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 22:35 compiling in C mode and the compilation buffer Shug Boabie
2004-07-25 22:52 ` Benjamin Rutt
2004-07-28 1:24 ` Shug Boabie
2004-07-28 1:40 ` Shug Boabie
2004-07-28 12:57 ` Benjamin Rutt [this message]
2004-07-28 20:29 ` Shug Boabie
2004-07-28 21:41 ` Benjamin Rutt
2004-07-26 22:59 ` Kevin Rodgers
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=87y8l4b87o.fsf@osu.edu \
--to=rutt.4+news@osu.edu \
/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).