From: Dan Jacobson <jidanni@deadspam.com>
Subject: next-error was never ready for makefiles
Date: 16 May 2002 11:17:43 +0800 [thread overview]
Message-ID: <m2lmaksrvs.fsf@jidanni.org> (raw)
Fellas, how could it be that 15 years ago I was already using M-x
compile and gdb etc. all hooked together, whatever, but still down to
this very day if I say, blow something in a Makefile, M-x compile
can't jump to the error:
cd /home/jidanni/unicode/
make
echo 'a@b#c|perl -wln a.pl
/bin/sh: -c: line 1: unexpected EOF while looking for matching `''
/bin/sh: -c: line 2: syntax error: unexpected end of file
make: *** [a] Error 2
Compilation exited abnormally with code 2 at Thu May 16 11:08:06
the Makefile's error is obvious:
a:
echo 'a@b#c$"|perl -wln a.pl
# echo 30|perl -wlne 'print hex $$_'
Anyway, will the emacs dude and/or the bash dude get together and do
what is needed for next-error to jump to problems even in makefiles?!
[first gotta say the name of the makefile...]
--
http://jidanni.org/ Taiwan(04)25854780
next reply other threads:[~2002-05-16 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 3:17 Dan Jacobson [this message]
2002-05-17 0:09 ` next-error was never ready for makefiles 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=m2lmaksrvs.fsf@jidanni.org \
--to=jidanni@deadspam.com \
--cc=kindly_remove_this_part_first_jidanni@ms46.hinet.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).