June 2002 - XEmacs-Beta - XEmacs Mailing List Archives

Affordable web hosting 8829YZtA9-257jOLu0453-20 21 years, 11 months

jefghfghfrrycrve＠aol.com

* Dear Clients, This message is regarding some recent changes taking place at Host Year. Due to popular demand we have added a new hosting package. We are now offering the newly released Economy Package which is as follows: Economy Package: -200 MB Disk Space -FREE Unlimited Bandwidth -FREE Traffic/Hits -99.9% Uptime Guarantee -Unlimited POP3 Email Acounts -Easy Site Manager -FREE Search Engine Submission -FREE Shopping Cart -NO banners/pop-ups placed on your site -and much more! You may now receive this hosting package for only $3 per month with continued free technical support. Please contact tech(a)hostyearinc.com for technical support or further inquires. http://www.hostyear.com *Notice: You are receiving this message because you are either a current client, you have shown interest in our services in the past, or you have been referred though our affiliates. If you wish to be removed from future mailings please reply to this message with the subject line "Re-move". ACookbook(a)btamail.net.cn Name8867 3968piZH8-040CYjJ4860zEYk1-807SAae3401pl37

1 participants
0 comments

Re: [C] Re: [PATCH] packages: Convert distclean to double-colon throughout 21 years, 11 months

Vin Shelton

Adrian Aichner <adrian(a)xemacs.org> writes: > COMMIT > > Vin, do packages build for you again now? > Yes, thank you - modulo the ps-print bug I just submitted a patch for and the ilisp-mak.el patch I previously submitted. Idle thought: when building ilisp, why does no one else see this problem: While compiling toplevel forms in file /opt/build/xemacs-packages-2002-06-10/xemacs-packages/ilisp/ilisp-cl-easy-menu.el: !! File error (("Cannot open load file" "thingatpt")) Cannot open load file: thingatpt xemacs exiting This is the symptom that caused me to submit a patch for ilisp-mak.el: http://list-archive.xemacs.org/xemacs-patches/200206/msg00021.html 'thingatpt' comes from fsf-compat, so somehow fsf-compat needs to be loaded when ilisp-mak.el is run. - Vin

3 participants
5 comments

a couple issues with call-process-region... 21 years, 11 months

Josh Huber

I've noticed a couple issues with call-process-region: 1) It's not returning the exit code from the called process: (call-process-region 1 1 "ls" nil) => nil 2) Calling it with invalid arguments causes xemacs to become unstable and lock up several seconds later: (call-process-region 1 1 "ls" nil nil nil '()) Try that one... I get the following output on the console: Xlib: sequence lost (0x12474 > 0x2474) in reply type 0x0! xemacs: X Error of failed request: BadImplementation (server does not implement operation) Major opcode of failed request: 20 (X_GetProperty) Serial number of failed request: 9332 Current serial number in output stream: 9332 Xlib: unexpected async reply (sequence 0x247f)! Xlib: unexpected async reply (sequence 0x24c4)! Xlib: sequence lost (0x124b9 > 0x24b9) in reply type 0x0! xemacs: X Error of failed request: BadImplementation (server does not implement operation) Major opcode of failed request: 20 (X_GetProperty) Serial number of failed request: 9401 Current serial number in output stream: 9401 Any ideas? -- Josh Huber

2 participants
3 comments

[ANNOUNCE] Unsupported Package Directory in CVS 21 years, 11 months

Steve Youngs

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi People! Following the recent discussion on this list about "unofficial" packages I have set up a new directory hierarchy in the packages CVS module. The new hierarchy has this format: .../packages/unsupported/$developer-name/$package-name The idea is to have a place for people to keep XEmacs packages that, for one reason or another, aren't ready for distribution with the mainline packages. We, (The XEmacs Development Team), will not offer any user support for these packages. Neither will we recommend their use. All we are doing is offering a place for developers to store their work. Although I don't wish to put any restrictions or requirements on these packages, I must ask that they all: (a) Install to .../site-packages/ (b) Don't have a '_pkg.el' file because it will interfere with PUI and the official packages. (c) Don't use a 'package-index' file for installation, for the same reason as (b) Points (b) and (c) should only be a temporary thing, but PUI needs to be enhanced first.[1] If you'd like to have your own directory under 'unsupported' just drop me a line and I'll set it up for you. If you don't already have commit access to XEmacs CVS you'll need to send me your public SSH key (version 1 only) and your preferences for a user name (for CVS commit logging purposes). Footnotes: [1] This is something that I intend to work on. - -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---| -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: The XEmacs Development Team. iD8DBQE9BGECjNKQaxDVycURAlW4AJ9M0PF8Eh9A0nGtj6qm0BPODG7ljgCZAfj2 1+v2wb+8ubcw7r2802o0yPM= =cH5C -----END PGP SIGNATURE-----

5 participants
9 comments

Re: releasing 21.4 as stable 21 years, 11 months

Andy Piper

At 10:59 AM 6/12/02 -0700, Andy Piper wrote: >>The syntax table is a different matter entirely, of course. > >Right. Just to explain this. The implementation of syntax tables in 21.4 means that people are seeing something like a 15x slowdown in font-lock and indentation performance for largeish, font-locked files. Jan and Ben have done some work to provide reasonable caching of the syntax information so that the performance is much more comparable to 21.1. But these patches are not complete. I believe Stephen is going to take a look at Jan's patch to try and incorporate it into the main tree. andy

3 participants
4 comments

XEmacs 21.1.14 bug report 21 years, 11 months

Shripad Thite

Hello, I just installed xemacs 21.1.14 and tried to run it. The program crashes immediately after run. I couldn't find the problem in the PROBLEMS file, so please help. Attached is file "Installation" from the install directory and a backtrace produced by gdb. `uname -a` produces the following output (host name deleted): Linux [HOST] 2.4.18-6mdkenterprise #1 SMP Fri Mar 15 02:28:20 CET 2002 i686 unknown Thanks very much. -- Shripad.

1 participants
0 comments

symbol-near-point interactiveness 21 years, 11 months

Ken T Takusagawa

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. Please describe as succinctly as possible: - What happened. - What you thought should have happened. - Precisely what you were doing at the time. Please also include any C or lisp back-traces that you may have. ================================================================ Dear Bug Team! symbol-near-point in lisp/syntax.el ought NOT be (interactive)

1 participants
0 comments

ISO-8859-1 is the official coding system for ChangeLogs 21 years, 11 months

Stephen J. Turnbull

At least for now. This is simply a matter of continuing existing practice. My apologies to our many Japanese contributors, our growing list of Russian contributors, all others whose names cannot be correctly represented in ISO-8859-1, and Hrvoje Nikšić (who gets honorable mention here for all the effort he has gone to to increase awareness of the ISO 2022 Menace). When we change it, it will be to UTF-8. If you use Mule, please do (add-to-list 'file-coding-system-alist '("ChangeLog" . iso-8859-1)) in init.el or otherwise take steps to avoid spurious introduction of ISO 2022 DCS sequences in ChangeLogs. There is a similar problem with Windows and LF <-> CRLF for many kinds of files. This can be (and mostly has been) dealt with by use of the CVS binary file type. Please let us know if you observe similar weirdness with EOL behavior; we probably can arrange that Windows users get CRLFs and Unix users LFs as the gods of Redmond and Murray Hill, resp., intended. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py

1 participants
0 comments

Getting readline warning after every command in a Cygnus bash she ll inside Xemacs 21 years, 11 months

Sik Ngai

In XEmacs 21.2 (beta19) "Shinjuku" [Lucid] (i586-pc-win32) of Mon Aug 23 1999 on NEVERYON configured using `configure UNKNOWN' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I have upgrading to cygwin b20 and am having problem running a bash shell in xemacs. I get the following after executing a shell command (it came just before the prompt): warning: rl_prep_terminal: cannot get terminal settings Also, the output of executing a shell command is all screwed up. The following is the output of an "ls" command: ^[[0m^[[0mMakefile^[[0m ^[[0mclient-codegen.pj^[[0m ..... This communication is intended only for the use of the individual or entity to whom/which it is addressed, and information contained in this communication is privileged and confidential. If the receiver of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender of this email (so that we may correct our internal records) and delete this communication without making a copy of it. Thank you.

2 participants
1 comments

releasing 21.4 as stable 21 years, 11 months

Kyle Jones

What are the things that need to be done before 21.4 is considered fit to be released as the stable branch?

4 participants
4 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 June 2002