From: Cheng Gao <chenggao@gmail.com>
Subject: Re: Successful build of emacs-unicode-2 under Windows with MinGW
Date: Thu, 23 Sep 2004 17:51:31 +0800 [thread overview]
Message-ID: <ciu6b5$cfa$1@sea.gmane.org> (raw)
In-Reply-To: E1CA7ec-0002qw-1Q@fencepost.gnu.org
,----
| Lots of us are testing the trunk. I think it is important
| to have some people regularly using the emacs-unicode-2 branch,
| while most test the trunk.
|
| So if you're regularly using the emacs-unicode-2 branch,
| please speak up.
`----
I think this branch especially interests users from non-latin language background
like me. For example, with Chinese-GBK and Chinese-GB18030 supported in
emacs-unicode-2, it's very happy to use Gnus to view any Chinese
message. While with Emacs trunk, some messages can not be viewed
properly with GB2312. This is why I am so interested in this branch.
So far my adventure is fairly good, though I expect there will be many
bugs. (In fact I have found some).
Now the most painful thing is with getting source.
Savannah CVS is really slow for this branch. I think it takes forever
for me to update it. At the same time, trunk update is fairly fast.
And I have luckily gotten Miles' arch source for only once. After that,
I have tried several times to update with no joy.
Now I am very curious for one thing:
Is there any big date/time processing related changes in unicode-2
recently?
At least under MinGW version, evaluating
(format-time-string "%Y-%m-%d" emacs-build-time)
generates an empty string as " " (8 spaces).
While value of `emacs-build-time is (16722 29008 93000).
I have compared src/editfns.c of trunk and unicode-2 branch and found no
difference. I think the changes are in other place(s).
And if I run Gnus in Emacs 22, then exit (with newsrc.eld saved), then I
use Emacs trunk (21.3.50) to run Gnus, it generates an error as "Invalid
Date:". My investigation shows that in newsrc.eld,
`gnus-newsrc-last-checked-date is set as a empty string by Emacs 22.
So I have to remove (setq gnus-newsrc-last-checked-date ...) line
manually from .newsrc.eld, and Gnus can run from Emacs trunk.
But then without this line, Gnus can not run from Emacs 22. It shows the
same error as "Invalid Date:".
Then I have to run Gnus in Emacs trunk, and exit, thus a valid (setq
gnus-newsrc-last-checked-date ...) line is generated, and then Gnus can
be run from Emacs 22.
This test is with MinGW build with source got two weeks ago. Maybe this
has been fixed, but owing to inaccessibility of cvs/arch source, I can
not test with the latest code.
My preliminary impression is that this problem may be platform-specific.
In my home computer with Gentoo GNU/Linux with latet code, seems above
mentioned two problems dont exist. Tonight I'll make check and confirm this.
Sincerely yours,
CG
--
这去者,不能见他的脸,背影模糊。
next prev parent reply other threads:[~2004-09-23 9:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 6:42 Successful build of emacs-unicode-2 under Windows with MinGW Cheng Gao
2004-09-20 17:24 ` Cheng Gao
2004-09-21 5:37 ` Dhruva Krishnamurthy
2004-09-21 5:50 ` Miles Bader
2004-09-21 6:34 ` Cheng Gao
2004-09-22 13:59 ` Richard Stallman
2004-09-22 16:14 ` zrr
2004-09-23 4:22 ` Dhruva Krishnamurthy
2004-09-23 16:44 ` Richard Stallman
2004-09-24 6:21 ` Dhruva Krishnamurthy
2004-09-24 7:24 ` Cheng Gao
2004-09-24 7:43 ` Jason Rumney
2004-09-27 5:07 ` Dhruva Krishnamurthy
2004-09-27 9:22 ` Cheng Gao
2004-09-27 9:41 ` Dhruva Krishnamurthy
2004-09-27 9:57 ` Jason Rumney
2004-09-27 9:59 ` Dhruva Krishnamurthy
2004-09-27 10:38 ` Dhruva Krishnamurthy
2004-09-27 10:41 ` Miles Bader
2004-09-27 11:04 ` Cheng Gao
2004-09-28 0:11 ` Paul Pogonyshev
2004-09-27 21:41 ` Jason Rumney
2004-09-23 9:51 ` Cheng Gao [this message]
2004-09-23 10:07 ` Miles Bader
2004-09-21 8:56 ` Dhruva Krishnamurthy
2004-09-21 9:18 ` Cheng Gao
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ciu6b5$cfa$1@sea.gmane.org' \
--to=chenggao@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.