From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: [romain@orebokech.com: Re: compile.el change]
Date: Mon, 17 Jul 2006 00:08:33 -0400 [thread overview]
Message-ID: <874pxgkh4u.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1G1ExX-00064T-G9@fencepost.gnu.org> (Richard Stallman's message of "Fri, 14 Jul 2006 00:07:23 -0400")
Richard Stallman <rms@gnu.org> writes:
> Would someone please fix this and ack?
Fixed.
> From: Romain Francoise <romain@orebokech.com>
> Subject: Re: compile.el change
>
> I found another case: when you use M-x byte-compile-file, the following
> is inserted in the Compile-Log buffer:
>
> | ^L
> | Compiling file /tmp/foo.el at Wed Jul 12 20:39:40 2006
> | Entering directory `/tmp/'
>
> The middle line gets recognized as a compilation error, but it's not.
prev parent reply other threads:[~2006-07-17 4:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 4:07 [romain@orebokech.com: Re: compile.el change] Richard Stallman
2006-07-17 4:08 ` Chong Yidong [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
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=874pxgkh4u.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@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).