XEmacs-Beta July 2000

xemacs-beta@xemacs.org

98 participants
357 discussions

Michael Sperber

>>>>> "Simon" == Simon Josefsson <simon(a)josefsson.org> writes: Simon> Using PCL-CVS and pressing `=' on a file brings out this message: Simon> (1) (error/warning) Error in process sentinel: (wrong-type-argument stringp nil) Simon> with "Parsing differences..." in the modeline. Seem to be `diff-mode' Simon> that's having problems. Definitely. PCL-CVS is meant to go with a diff-mode incompatible with ours. I've postponed fixing this because of the inherent trickiness. However, I've hacked around most of the differences in subsequent versions. Simon> This is with "xemacs -no-init-file". I would check if my XEmacs Simon> packages are up to date, You might at least post the version of the package you have. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

diff-mode 23 years, 10 months

Simon Josefsson

Using PCL-CVS and pressing `=' on a file brings out this message: (1) (error/warning) Error in process sentinel: (wrong-type-argument stringp nil) with "Parsing differences..." in the modeline. Seem to be `diff-mode' that's having problems. This is with "xemacs -no-init-file". I would check if my XEmacs packages are up to date, but I get the following error when I select "Update package index" from the Options menu. (1) (error/warning) Error in process filter: (ftp-error FTP Error: CWD 550 /pub/gnu/xemacs/packages/package-index.LATEST.pgp/: Not a directory. failed: )

1 participants
0 comments

xemacs 21.1 cvs compile fail 23 years, 10 months

Simon Josefsson

Do I need read/write permissions to the xemacs-package directory in order to build a xemacs binary? XEmacs 21.2 in cvs builds fine though. (No big issue, but thought you'd might want to know) ... Dumping under the name xemacs Purespace usage: 775672 of 775672 (100%). Testing for Lisp shadows ... This site has duplicate Lisp libraries with the same name. If a locally-installed Lisp library overrides a library in the Emacs release, that can cause trouble, and you should probably remove the locally-installed version unless you know what you are doing. /usr/local/lib/xemacs/xemacs-packages/lisp/vc/vc hides /usr/local/lib/xemacs/xemacs-packages/lisp/vc -cc/vc /usr/local/lib/xemacs/xemacs-packages/lisp/vc/vc-hooks hides /usr/local/lib/xemacs/xemacs-packages/l isp/vc-cc/vc-hooks /usr/local/lib/xemacs/xemacs-packages/lisp/xemacs-base/xpm-button hides /home/jas/src/xemacs-21.1/o/ lisp/xpm-button 3 Emacs Lisp load-path shadowings were found make[2]: Leaving directory `/home/jas/src/xemacs-21.1/o/src' make[1]: Leaving directory `/home/jas/src/xemacs-21.1/o/src' Building finder database ... xemacs exiting.Opening input file: Permission denied, /usr/local/lib/xemacs/xemacs-packages/lisp/edi t-utils/icomplete.el make: *** [lisp/finder-inf.el] Error 255 [jas＠localhost o]$

1 participants
0 comments

Re: return value of gettext() needs to be MULE-converted? 23 years, 10 months

Hrvoje Niksic

Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > for example, what about this code in fileio.c: > > error ("IO error reading %s: %s", > XSTRING_DATA (filename), strerror (saverrno)); > > now surely *this* is wrong or am I missing something again? Obviously noone thought about strerror() returning non-ASCII stuff. The correct way to write the above would be something like: Bufbyte *internal_strerror; TO_INTERNAL_FORMAT (C_STRING, strerror (saverrno), C_STRING_ALLOCA, internal_strerror, Qnative); error ("IO error reading %s: %s", XSTRING_DATA (filename), internal_strerror); Even better, the code should be modified to use report_file_error() or one of its relatives (if possible.)

2 participants
1 comments

SURVEY: Locales on your system 23 years, 10 months

Ben Wing

I'm trying to implement locale support in XEmacs, and it's the worst goddamn mess i've ever seen because each system has its own names for locales and there's no sense to it. So ... I'd like to find out what the locale names on each system are, and what encodings are used. For now let's just concentrate on Chinese, Japanese, Korean, and Russian, which are the stickiest problems. So ... What system [exactly!] are you running, and what are the names of the locales [look in /usr/share/locale or /usr/lib/locale], and what are the encodings [if you know this and it's not obvious from the name]? Thanks muchly, -- Ben In order to save my hands, I am cutting back on my mail. I also write as succinctly as possible -- please don't be offended. If you send me mail, you _will_ get a response, but please be patient, especially for XEmacs-related mail. If you need an immediate response and it is not apparent in your message, please say so. Thanks for your understanding. See also http://www.666.com/ben/chronic-pain/

2 participants
3 comments

Re: SURVEY: Locales on your system 23 years, 10 months

Matt Curtin

>>>>> "Ben" == Ben Wing <ben(a)666.com> writes: Ben> What system [exactly!] are you running, and what are the names Ben> of the locales [look in /usr/share/locale or /usr/lib/locale], Ben> and what are the encodings [if you know this and it's not Ben> obvious from the name]? FreeBSD 3.0-RELEASE #0: ru_RU.KOI8-R IRIX 6.5: ru [Uses iso-8859-5] Solaris 2.6 seems to call its Russian locale `ru' like IRIX, but it isn't clear what character set it wants as someone didn't want to install all of the necessary fonts and the oh-so-useful 2.6 locale files don't say. I seem to remember that iso-8859-5 would be used, but I can't find anything definitive for Solaris at the moment. It's also worth noting that the locale for FreeBSD worked for me in all releases of 2.2.x and 3.x. -- Matt Curtin cmcurtin(a)interhack.net http://www.interhack.net/people/cmcurtin/

1 participants
0 comments

feature request: library versioning 23 years, 10 months

Stephen J. Turnbull

>>>>> "Bruce" == Bruce Ingalls <bruce(a)conde-dev.com> writes: Bruce> After talking with fellow emacs developers, we would like Bruce> to see a shared system (i.e. common to x & fsf/gnu emacs) Bruce> for tracking versions of elisp libraries. Bruce> I am recommending a syntax with 3 new optional arguments: Bruce> (provide 'my-package 1 2 34) #'provide is about features, not about libraries. Many libraries provide multiple features; provision of some features often requires multiple libraries. I don't know of any off hand, but there probably are virtual features that are provided by multiple libraries. Coordinating all this with version numbers seems hairy, to say the least. I would say implement library- (or file-) versioning separately from #'provide. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

3 participants
2 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 July 2000