From: jidanni@jidanni.org
To: 10239@debbugs.gnu.org
Subject: bug#10239: compilation-auto-jump-to-first-error vs. giant binary executables
Date: Wed, 07 Dec 2011 07:14:41 +0800 [thread overview]
Message-ID: <87y5upfg2m.fsf@jidanni.org> (raw)
$ cat Makefile
a:;set -Y
$ emacs -Q -eval '(setq compilation-auto-jump-to-first-error t)' -f compile
RET
/bin/sh: line 0: set: -Y: invalid option
Wham pow! We are looking at a whole megabyte of binary ELF /bin/sh executable.
I didn't try it on lager files or with ones with strings the colorizer
would try to color etc.
next reply other threads:[~2011-12-06 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 23:14 jidanni [this message]
2019-09-29 17:08 ` bug#10239: compilation-auto-jump-to-first-error vs. giant binary executables Lars Ingebrigtsen
2019-09-29 17:30 ` 積丹尼 Dan Jacobson
2019-09-29 17:43 ` Andreas Schwab
2019-09-29 18:48 ` bug#25329: " Lars Ingebrigtsen
2019-10-09 23:20 ` bug#10239: " Lars Ingebrigtsen
2019-10-10 8:32 ` bug#25329: " Andreas Schwab
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=87y5upfg2m.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=10239@debbugs.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 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).