8:33 p.m.
Steve,
Thanks for the new package organization. I think it's a lot clearer.
I just tried to build all the packages for the first time in awhile,
and in the edit-utils package I got the following error:
While compiling toplevel forms in file
/usr/local/build/xemacs-packages-2001-07-04/xemacs-packages/edit-utils/search-buffers.el:
!! End of stream ((#<buffer " *Compiler Input*">))
When I looked at the file, it seems that every line is terminated with
^M. Since I am trying to build with a non-Mule XEmacs, the ^Ms
confuse the byte compiler.
I could submit a patch if you want. Just let me know.
- vin
9:42 p.m.
>>>> "Vin" == Vin Shelton <acs(a)xemacs.org>
writes:
Vin> Steve,
Vin> Thanks for the new package organization. I think it's a lot clearer.
Vin> I just tried to build all the packages for the first time in awhile,
Vin> and in the edit-utils package I got the following error:
Vin> While compiling toplevel forms in file
/usr/local/build/xemacs-packages-2001-07-04/xemacs-packages/edit-utils/search-buffers.el:
Vin> !! End of stream ((#<buffer " *Compiler Input*">))
Vin> When I looked at the file, it seems that every line is terminated with
Vin> ^M. Since I am trying to build with a non-Mule XEmacs, the ^Ms
Vin> confuse the byte compiler.
Vin> I could submit a patch if you want. Just let me know.
Hi Vin, since this file originates between my four walls, and I'm
living wedged between Windows, I'm prepared to admit anything :-)
If Steve agrees, I definitely welcome your patch.
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
10:33 p.m.
|--==> "APA" == Adrian Aichner <Adrian.Aichner(a)t-online.de> writes:
APA> Hi Vin, since this file originates between my four walls, and I'm
APA> living wedged between Windows, I'm prepared to admit anything :-)
Someone really should throw you a unix life-line to save you from your
hell. :-)
APA> If Steve agrees, I definitely welcome your patch.
I definitely agree.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
1:27 a.m.
Adrian.Aichner(a)t-online.de (Adrian Aichner) writes:
Hi Vin, since this file originates between my four walls, and
I'm
living wedged between Windows, I'm prepared to admit anything :-)
If Steve agrees, I definitely welcome your patch.
Well, the patch is straight-forward, but large:
- vin
10:31 p.m.
|--==> "VS" == Vin Shelton <acs(a)xemacs.org> writes:
VS> Steve,
VS> Thanks for the new package organization. I think it's a lot clearer.
You're welcome.
VS> I just tried to build all the packages for the first time in awhile,
VS> and in the edit-utils package I got the following error:
VS> While compiling toplevel forms in file
/usr/local/build/xemacs-packages-2001-07-04/xemacs-packages/edit-utils/search-buffers.el:
VS> !! End of stream ((#<buffer " *Compiler Input*">))
VS> When I looked at the file, it seems that every line is terminated with
VS> ^M. Since I am trying to build with a non-Mule XEmacs, the ^Ms
VS> confuse the byte compiler.
Darn!
VS> I could submit a patch if you want. Just let me know.
Yes please.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
9:34 a.m.
Vin Shelton <acs(a)xemacs.org> writes:
When I looked at the file, it seems that every line is terminated
with ^M. Since I am trying to build with a non-Mule XEmacs, the ^Ms
confuse the byte compiler.
Or perhaps the reader? The byte-compiler should work with the data
structures provided by the reader.
If so, couldn't we fix the reader to consider ^M a whitespace
character like it does for newline, ^L, etc.?
4:16 a.m.
Yes, I think you're right, it probably is the reader. And I think the
reader should consider ^M as whitespace.
- vin
Hrvoje Niksic <hniksic(a)arsdigita.com> writes:
Vin Shelton <acs(a)xemacs.org> writes:
> When I looked at the file, it seems that every line is terminated
> with ^M. Since I am trying to build with a non-Mule XEmacs, the ^Ms
> confuse the byte compiler.
Or perhaps the reader? The byte-compiler should work with the data
structures provided by the reader.
If so, couldn't we fix the reader to consider ^M a whitespace
character like it does for newline, ^L, etc.?
8535
days inactive
8537
days old
6 comments
4 participants
participants (4)
-
Adrian Aichner -
Hrvoje Niksic -
Steve Youngs -
Vin Shelton