April 2018 - XEmacs-Beta - XEmacs Mailing List Archives

Hauke Fath

Hi, I nave been banging a bit on vc-fossil.el from <http://chiselapp.com/user/venks/repository/emacs-fossil/doc/tip/doc/index...>, and got it to work with Xemacses "slightly-older vc. Provided there is interest: What would be the procedure to include the fuke with the XEmacs vc? Cheerio, hauke -- The ASCII Ribbon Campaign Hauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344

2 participants
4 comments

is speed a concern? 5 years, 3 months

Julian Bradfield

Another possibly silly question arising from perusal of the great Mule merge... Is speed (or small linear factors in memory) ever actually a concern nowadays? The whole deal of supporting multiple internal buffer formats seems to be justified by speed for multi-lingual processing, and there are various tricky things scattered around the rest of the code to improve speed. The last time I can remember being disturbed by XEmacs' slowness was sometime in the mid 90s when I was running Lucid Emacs 19 on a 68040. (The days when a full compile was a go-out-for-long-dinner job rather than a you-may-just-have-time-to-make-coffee job.) On the other hand, I don't do extensive non-English processing. Do people find XEmacs noticeably slow in any normal usage pattern? -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

6 participants
9 comments

What to do with #'split-char. 5 years, 11 months

Aidan Kehoe

Previous to Ben’s unicode-internal work, if split-char was available on any emacs, it never gave nil for a valid character. And so a certain amount of code was written with that assumption. My code has been particularly impacted by this change; see the error provoked with C-u C-x = for any remotely exotic Unicode character for an example. To clarify what I mean, this code: (mapcar #'split-char (list ?\U000130bA (max-char) (- (max-char) #xff))) Gives (nil nil nil) on current unicode-internal XEmacs, and the following on a current GNU Emacs: ((unicode 1 48 186) (eight-bit 255) (emacs 63 255 0)) My working plan at the moment is to emulate GNU’s behaviour in those situations where we currently give nil. Thoughts? Details of the GNU build: GNU Emacs 27.0.50 (build 2, i386-apple-darwin10.8.0, NS appkit-1038.36 Version 10.6.8 (Build 10K549)) of 2018-04-29 built on bonbon Repository revision: bf12cc6c7830937b4c1a3df46294e74bea749a5f -- ‘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

Summary of XEmacs Issue Tracking System Issues 5 years, 12 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2018-04-17 - 2018-04-24) 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: 3118 days. Median duration of open issues: 3329 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

Buildbot down due to hardware problems 6 years

Mats Lidell

Hi XEmacs, The xemacs build bot is down due to hardware failure. I will replace the machine but I can't say when it will be up again. I'll let you know. Yours -- %% Mats

2 participants
3 comments

Font problem 6 years

Dr Rainer Woitok

Greetings, running on Xubuntu 16.4 I'm currently still using XEmacs 21.4.22 which is the version officially provided by Xubuntu (I have yet to have the spare time to compile XEmacs directly from the Mercurial repository ... sigh)-: Whenever I start XEmacs I receive the following warning message: Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct In my "~/.Xresources" file I have several fonts specified for quite a few Xemacs resources, but I'm not using any "helvetica" font. So I'm assuming XEmacs is falling back to some default here for some resource I did not specify. Since it's a bold font, it's probably for some weird menu I'm not even using ... In file "/etc/X11/fonts/misc/xfonts-base.alias" I found the following line: variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-1 so XEmacs could also use "variable" as a default for some unspecified resource. If somebody could point me to the resource name associated with that de- fault font in XEmacs, I could update my "~/.Xresources" file according- ly, get rid of this annoying warning message, and would again be very happy :-) Sincerely, Rainer

4 participants
14 comments

Summary of XEmacs Issue Tracking System Issues 6 years

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2018-04-10 - 2018-04-17) 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: 3111 days. Median duration of open issues: 3322 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

Account Final Warning Your Email xemacs-beta@xemacs.org Will Be Shutdown Soon 6 years

Account Edministrator

Spam detection software, running on the system "mars.taur.is", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see ＠＠CONTACT_ADDRESS＠＠ for details. Content preview: Server Message Dear xemacs-beta(a)xemacs.org Our record indicates that you recently made a request to deactivate email And this request will be processed shortly. If this request was made accidentally and you have no knowledge of it, you are advised to cancel the request now [...] Content analysis details: (8.7 points, 4.7 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: xemacs.org] 1.3 RCVD_IN_RP_RNBL RBL: Relay in RNBL, https://senderscore.org/blacklistlookup/ [212.60.66.6 listed in bl.score.senderscore.com] 1.4 RCVD_IN_BRBL_LASTEXT RBL: No description available. [212.60.66.6 listed in bb.barracudacentral.org] 0.8 FROM_NO_USER From: has no local-part before ＠ sign 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] 0.0 HTML_FONT_SIZE_HUGE BODY: HTML font size is huge 0.0 HTML_FONT_LOW_CONTRAST BODY: HTML font color similar or identical to background 0.0 HTML_MESSAGE BODY: HTML included in message 0.5 MISSING_MID Missing Message-Id: header 3.0 URI_WP_HACKED URI for compromised WordPress site, possible malware 0.9 URI_PHISH Phishing using web form The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 participants
0 comments

Summary of XEmacs Issue Tracking System Issues 6 years

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2018-04-03 - 2018-04-10) 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: 3104 days. Median duration of open issues: 3315 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta April 2018