June 2003 - XEmacs-Beta - XEmacs Mailing List Archives

Lawrence Paulson

Users may recall my continual tribulations with running xemacs with Apple's X11 Beta 3, where if one goes so far as to click on the "open file" icon, it crashes with the attached messages appearing on the calling xterm. (Version 21.4 patch 9, installed by fink. OS version 10.2.6.) A colleague of mine was able to install xemacs on his Mac. I took a copy of his /sw directory, moving my /sw out of the way. It works perfectly for him, but on my computer it fails in exactly the same way. This happens even if I create a new user on my machine, so it can't have anything to do with my .emacs file or environment settings. It must have something to do with other system files. Does anybody have any idea where to start looking for the culprit? Larry Paulson xemacs: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 55 (X_CreateGC) Serial number of failed request: 1253 Current serial number in output stream: 1266 xemacs: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 55 (X_CreateGC) Serial number of failed request: 1254 Current serial number in output stream: 1266 xemacs: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 55 (X_CreateGC) Serial number of failed request: 1277 Current serial number in output stream: 1301 Xlib: unexpected async reply (sequence 0x515)! xemacs: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 55 (X_CreateGC) Serial number of failed request: 1276 Current serial number in output stream: 1301

2 participants
1 comments

Bug: Couldn't find an obvious default for the root of the XEmacs hierarchy 16 years, 2 months

Moore, Paul

Built on Windows 2000 Pro, MSVC6, XEmacs version 21.5.14 (this was in 13 as well). No changes to the base stuff, just built (with optimisation on, no debugging, but that makes no difference). Starting XEmacs from anywhere other than the directory of the executable gives error WARNING: Couldn't find an obvious default for the root of the XEmacs hierarchy. WARNING: Couldn't find obvious defaults for: doc-directory data-directory exec-directory mule-lisp-directory lisp-directory Perhaps some directories don't exist, or the XEmacs executable, c:\Apps\XEmacs\XEmacs-21.5-b14\i586-pc-win32\xemacs.exe is in a strange place? The following patch seems to fix it, but is probably wrong :-( There is no lib-src directory in an NT installed copy. --- setup-paths.el.orig 2003-03-09 01:37:38.000000000 +0000 +++ setup-paths.el 2003-06-06 16:09:45.000000000 +0100 ＠＠ -123,7 +123,7 ＠＠ ;; don't exist. instead, xemacs.mak points configure-lisp-directory and ;; configure-data-directory at the right places. (and - (or configure-exec-directory (paths-file-readable-directory-p (paths-construct-path (list directory "lib-src")))) +; (or configure-exec-directory (paths-file-readable-directory-p (paths-construct-path (list directory "lib-src")))) (or configure-lisp-directory (paths-file-readable-directory-p (paths-construct-path (list directory "lisp")))) (or configure-data-directory (paths-file-readable-directory-p (paths-construct-path (list directory "etc")))))))

1 participants
0 comments

Need Debt Relief? We Can Help! dowg x wfx 16 years, 2 months

Melissa Lawson

1 participants
0 comments

Re: Associating assembly mode with .asm 16 years, 2 months

Adrian Aichner

>>>>> "James" == James Liang <Liang> writes: James> By default, xemacs associates .s files with assembly source. James> How do I get it to associate .asm files with assembly source? James, this should do it (in .emacs): (add-to-list 'auto-mode-alist '("\\.asm\\'" . asm-mode)) Norbert, should we add an autoload cookie for this to asm-mode.el? James> James -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

2 participants
2 comments

Modules on Windows: help with dlltool 16 years, 2 months

Jerry James

I've decided to have a go at fixing module support on Windows platforms. I've reluctanly set up my home machine to dual-boot Windows and Linux, and have installed cygwin on the Windows side. I came up with a test to see if I correctly understand the linking problems involved. It didn't work out quite as I expected, though, and I wonder if anybody can give me a boost in the right direction. The test.c file is supposed to be an analog of XEmacs: it is self-contained, has a function that can be used by modules, and opens and attempts to use some user-specified DLL. On the other hand, dll.c is the source for a simple dll.c that provides a function needed by test.c, and uses a support function provided by test.c. The Makefile attempts to compile these to an executable, test.exe, and a DLL, my.dll. With the Makefile as given, the result is: $ ./test.exe my.dll "This is a test" Unable to open library my.dll If the use of dlltool is removed in favor of the two commented lines below it, namely: gcc -o junk -shared -Wl,--out-implib -Wl,libtest.a test.o rm junk.exe then the result is: $ ./test my.dll "This is a test" The string is This is a test Its reverse is tset a si sihT Also, I note that when gcc is used to create junk.exe as above, it says "Creating library file: libtest.a", but dlltool does not. When the "-shared" is omitted from the gcc line above, to create the actual test.exe executable, then libtest.a is NOT created. And finally, the junk.exe created above really is junk: it is actually a DLL, not an executable. I'd rather not create a junk XEmacs DLL just to get the import library. Can anybody show me how to use dlltool appropriately to make this work? -- Jerry James http://www.ittc.ku.edu/~james/

1 participants
0 comments

[comp.emacs] Re: why i use xemacs 16 years, 2 months

Adrian Aichner

FYI -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

File mode specification error 16 years, 2 months

Dieter Mellet

Dear Bug Team! I'm using and only really starting to learn the detail of xemacs recently. I am getting the following error message as in the recent messages window. I'm trying to use the vhdl-mode and quite succesfully up till today. I stumbled over a bug report 21.4.11 with a similar problem as in java. I'm running windows XP and have checked that the file c:\WINDOWS\system32\find.exe exists. Man, I've spent the while day trying to track the problem. I've even reinstalled the whole xemacs and yet it still gives this error. I'm not sure how to generate all the information needed to debug this but I can gice you this: eval-expr RET system-type RET returns window-nt Recent messages: Loading fast-lock... Loading fast-lock...done Loading time... Loading time...done Loading efs-cu... Loading efs-cu...done Loading vhdl-mode... File mode specification error: (file-error "Searching for program" "No such file or directory" "find") exec-path returned the following ("%SystemRoot%\\system32\\" "%SystemRoot%\\" "%SystemRoot%\\System32\\Wbem\\" "C:\\Program Files\\Xemacs\\XEmacs- 21.4.11\\i586-pc-win32\\" "C:\\Program Files\\Xemacs\\xemacs-packages\\lib- src\\" "c:\\Program Files\\XEmacs\\XEmacs-21.4.11\\i586-pc-win32\\") Please help, I can't continue my work with out this!! Greetings Dieter Dieter Mellet IC Design Engineer Tel: +27 21 863 0033 (GMT +2) www.azoteq.com

2 participants
1 comments

coding-detection failure on recent xemacs-beta(Mule). 16 years, 2 months

Fuyuhiko MARUYAMA

Hello guys, I think all recent xemacs have problem around MULE coding-detection codes since version 21.5.6 or 21.5.7 that fails coding-detection for some kinds of multi-byte character encodings in the iso_8_2 category, e.g. EUC-JP. Because of this problem, I was using version 21.5.5 for quite long time. Recently, I could have time to dig the problem and found what's hapeen when coding-detection fails. Here I try to write the problem. Please fix the problem. *PROBLEM* coding-detection fails to guess the coding-system under some condition *DESCRIPTION* Since MULE coding-detection are designed to find what coding-system is most appropriate one for a given text on user's current environment as quick as possible, the logic to guess the coding-system is implemented to analyze ONLY SMALL FRAGMENT OF TARGET TEXT. But, the implementation of iso_8_2 detection logic seems to be so stubborn that cannot allow mis-detection and forget the fact that it only analyzes small fragment of text. On coding-systems within iso_8_2 category, i.e. EUC-JP, texts usually include both of iso_8_2(multi-byte) characters and ascii(1-byte) characters, e.g. even pure Japanese text in EUC-JP usually includes 1-byte characters such as LF(0x0a), of course most of texts we write includes not only control-characters but also ascii characters such as 'XEmacs'. Because of this, the fragment of target text given for coding-detection logic can be incomplete string, i.e. the first byte and the last byte of text fragment can be incomplete multi-byte character and the logic must consider this fact. *SOLUTION* I made a very simple patch to relax the condition of iso_8_2 detection to allow sampling-error. Of course I know there may be more complete and smart way, but I didn't dig XEmacs entirely so that I can write such a smart solution. --- src/mule-coding.c.orig Mon Jan 13 17:46:44 2003 +++ src/mule-coding.c Thu Jun 5 04:49:22 2003 ＠＠ -2935,8 +2935,12 ＠＠ else DET_RESULT (st, iso_8_1) = DET_SOMEWHAT_LIKELY; } +#if 1 + else if (data->even_high_byte_groups > 0) +#else else if (data->odd_high_byte_groups == 0 && data->even_high_byte_groups > 0) +#endif { #if 0 SET_DET_RESULTS (st, iso2022, DET_SOMEWHAT_UNLIKELY); *For more complete solution* The logic counts data->odd_high_byte_groups must take the fact that 'text fragment (of DEFINITELY VALID TEXT represented in a coding-system of iso_8_2 category) can have incomplete multi-byte characters at the first and the last byte' under consideration. Especially, current logic increments data->odd_high_byte_groups even if the last byte of TEXT FRAGMENT is *eventually* a part of (incomplete) multi-byte character. If (data->odd_high_byte_groups != 0), current logic never guess the text can be in iso_8_2 category. There's another way such as to calculate the error-rate of data->odd_high_byte_groups for iso_8_2 to ignore some small value of data->odd_high_byte_groups as sampling-error. Anyway, I believe above description may help the maintainer to fix the problem. Thanks in advance, -- Fuyuhiko MARUYAMA <fuyuhik8(a)is.titech.ac.jp> Matsuoka laboratory, Department of Mathematical and Computing Sciences, Graduate School of Information Science and Engineering, Tokyo Institute of Technology.

1 participants
0 comments

Site on Psychology 16 years, 2 months

Anton Tyoplyi

Peace to you! The basis of fundamental psychology, the methodology of spiritual development, also healing and causes of diseases - on our web-site www.swami-center.org - books, poems, photos. Sincerely yours, Vladimir Antonov, Ph.D. swami(a)mail.ru

1 participants
0 comments

memory exhausted - ERROR MSG 16 years, 2 months

Art Singer

Please describe as succinctly as possible: - What happened. - What you thought should have happened. - Precisely what you were doing at the time. I am running xemacs XEmacs-21.4.3 on a win2000 machine. When I try and open a large text file > 100 mb, I get the error msg "memory exhausted". The machine itself has about 1 gb of free memory. Is there any way around this? Thanks, Art Singer

1 participants
0 comments

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 2003