Spam, and so forth.
6 years, 5 months
Aidan Kehoe
Aidan Kehoe
Some spam has got through to the list and into the archives since the lists
were restored (though of course much less than was sent to the list
addresses). I have tightened up the posting rules and list membership rules;
now only members can post (as was previously the case) and any membership
requests need to be confirmed (which is new). Sorry about the spam, and the
resultant confusing situation of the archives, and thank you Uwe Brauer for
pointing out to me how confusing this is!
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
- 1 participants
- 0 comments
XEmacs on Fedora 26, Ubuntu 17.10
6 years, 5 months
Raymond Toy
Raymond Toy
My primary systems are Fedora 25 and Ubuntu 14, and latest xemacs runs fine
there. (One minor nit: menus are displayed with strange colors and
backgrounds. I worked around that by using --with-xft=emacs,menubars.)
However, I've been trying to build on 26 and 17.10. (And some random
Debian test at work). It doesn't work.
On fedora 26 and ubuntu, I configure using --with-mule
--with-xft=emacs,menubars
In both systems, I gt errors that __getpagesize is implicitly declared and
that sbrk has conflicting types.
I just removed the erroneous declaration of sbrk (in favor of the
definition from unistd.h), and just changed __getpagesize to getpagesize.
This allows compile to finish, but running
xemacs -no-packages -batch -no-autoloads -l update-elc-2.el -f
batch-update-elc-2
causes a segfault. Indeed, just src/xemacs segfaults.
Any ideas? Configuring with --with-system-malloc gets around the problem
but it still segfaults in the same place.
--
Ray
- 3 participants
- 5 comments
Summary of XEmacs Issue Tracking System Issues
6 years, 5 months
XEmacs Issue Tracking System
XEmacs Issue Tracking System
ACTIVITY SUMMARY (2017-10-31 - 2017-11-07)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
574 open ( +0) / 323 closed ( +0) / 897 total ( +0)
Open issues with patches: 13
Average duration of open issues: 2950 days.
Median duration of open issues: 3161 days.
Open Issues Breakdown
new 266 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 57 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
- 1 participants
- 0 comments
Re: --with-unicode-internal?
6 years, 5 months
Aidan Kehoe
Aidan Kehoe
Ar an cúigiú lá de mí na Samhain, scríobh Raymond Toy:
> Ok, cool. I can wait for that.
>
> Is there any advantage/disadvantage in using unicode-internal instead of
> just plain old mule internals?
Plain old Mule internals is limited to about 400,000 Unicode code points in
one XEmacs process (beyond those code points already allocated for Big5, CNS
11643, iso8859, etc). This is due to a limitation on the number of
just-in-time charsets that can be created. This isn’t an issue in daily use,
whence the lack of urgency about merging the unicode-internal code over the
last few years.
Most of the upside has been already achieved, with the fixed-width coding
systems avoiding the latin-disunification problem, and decent X11 redisplay
for the just-in-time charsets. An issue for you may be the CJK
disunification inherent in Unicode becomes a more evident issue.
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
- 1 participants
- 0 comments