Eli Zaretskii <[EMAIL PROTECTED]> writes:
> If they have the same timestamps, why do you get "source is newer"
> messages? I don't get them on my machine, and lread.c explicitly
> checks for .elc time _less_ than the .el time, not _less_or_equal_.
> Could you please look closer at this problem an
> From: Zhang Wei <[EMAIL PROTECTED]>
> Date: Wed, 11 Jul 2007 12:06:40 +0800
>
> The `cp' command of my installation don't preserve timestamps by
> default
`cp' never did. Only the Windows copy commands do.
> that makes the .elc files and the .el files have same timestamps as they
> are instal
The `cp' command of my installation don't preserve timestamps by
default, that command comes from the GNU coreutils 5.3.0 package:
--8<---cut here---start->8---
D:\download\emacs-gbk\nt>cp --version
cp (GNU coreutils) 5.3.0
Written by Torbjorn Granlund, David Ma
> Date: Tue, 10 Jul 2007 13:10:17 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED], emacs-pretest-bug@gnu.org, [EMAIL PROTECTED], [EMAIL
> PROTECTED]
>
> Anyway, back to the suggestion at hand: fine, I will make the
> --enable-encoding behavior the default when @documentencodi
Perhaps I'm confused: if Texinfo commands are not the recommended
way,
The Texinfo commands aren't unrecommended either. Both ways have their
advantages -- it depends on the document. That's why we support both.
then why do we have them? why not tell users to always use
literal
> Date: Mon, 9 Jul 2007 16:14:15 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED], emacs-pretest-bug@gnu.org, [EMAIL PROTECTED], [EMAIL
> PROTECTED]
>
> source was written well,
>
> I can't agree that it is bad to use literal characters instead of
> Texinfo commands.
Pe
Now that I've switched coreutils to GPL V3, I find the default behavior
(asking me if I want to downgrade to version 2) to be annoying -- and ironic.
This is against emacs built from cvs (git, actually :-) today.
Here's the patch I'm using:
2007-07-10 Jim Meyering <[EMAIL PROTECTED]>
G
