October 1999 - XEmacs-Beta - XEmacs Mailing List Archives

replace-match: GNU vs XEmacs 25 years, 1 month

Darryl Okahata

Has anyone given any thought to fixing the replace-match incompatibility between GNU Emacs and XEmacs? The optional fifth argument is different: * GNU Emacs 20.4: The optional fifth argument SUBEXP specifies a subexpression of the match. It says to replace just that subexpression instead of the whole match. This is useful only after a regular expression search or match since only regular expressions have distinguished subexpressions. * XEmacs: When fourth argument is a string, fifth argument STRBUFFER specifies the buffer to be used for syntax-table and case-table lookup and defaults to the current buffer. (When fourth argument is not a string, the buffer that the match occurred in has automatically been remembered and you do not need to specify it. I've been trying to port diff-mode.el to XEmacs, and it's difficult, as the subexpression-replacement capability of GNU Emacs is used extensively. I could managle diff-mode.el to work, but it would require a lot of effort, and I'm wondering if we can somehow fix replace-match, instead. The best solution is would be to shift the XEmacs-specific option over once place (make it the sixth option), but I don't know how much XEmacs code would have to be changed (especially, privately-written code). An ugly, kludgy solution would be to test the type of the fifth parameter; if it's a number, treat it as a subexpression index, otherwise treat it as a buffer. However, this means that you can't specify a buffer to use for syntax and case tables if a subexpression is specified. Comments, anyone? -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

1 participants
0 comments

Completion and partial width windows 25 years, 1 month

Raymond Toy

A colleague pointed this out. Split a frame vertically to get two side-by-side windows. Assume that truncate-lines is T and truncate-partial-width-windows is T, the defaults values, I think. Do a C-x b TAB to try to complete on a buffer name. If the number of buffers is very large and the windows are narrow, many of the buffer names are not visible because the lines have been truncated. There's no way, using the keyboard, to see names that have scrolled off to the right. On a normal full-width screen, pressing tab causes the completion window to scroll so you can see more. Should we momentarily bind truncate-lines and truncate-partial-width-windows to NIL for any completion window? This bug doesn't happen in 20.4. Ray

1 participants
0 comments

Re: 21.2.19 crash in ldap on Solaris 2.7 25 years, 1 month

Raymond Toy

>>>>> "Raymond" == Raymond Toy <toy(a)rtp.ericsson.se> writes: Raymond> I think this really is due to an invalid bytecode. As a quick test, I Raymond> removed all of the elc files for eudc and re-did the test. Everything Raymond> works as expected! Raymond> My eudc files were obtained from the 1999-07-29 sumo tarballs. Raymond> I'll try recompiling these files with 21.2.19 or perhaps some other Raymond> version. (Has the byte-compiler changed between 21.1.x and 21.2.19?) That was it! I byte-compiled all of the eudc files with 21.1.7, and everything seems to be working again. Ray

1 participants
0 comments

Re: bad widget! 25 years, 1 month

Michael Harnois

I don't know if this is relevant or not ... xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 22204 Current serial number in output stream: 22272 xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 22205 Current serial number in output stream: 22272 xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 26300 Current serial number in output stream: 26333 xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 28153 Current serial number in output stream: 28221 xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 28154 Current serial number in output stream: 28221 xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 29625 Current serial number in output stream: 29693 xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 29626 Current serial number in output stream: 29693 Error: Widget *Group* has zero width and/or height Program exited with code 01. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mharnois(a)willinet.net aa0bt(a)aa0bt.ampr.org God shows his contempt for wealth by the kind of person He selects to receive it. -- Austin O'Malley

2 participants
1 comments

Re: bad widget! 25 years, 1 month

Michael Harnois

Interesting, I thought I could get a stack trace by running under gdb ... but when it dies gdb says "Program exited with code 01" and when I ask where it says "No stack." -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mharnois(a)willinet.net aa0bt(a)aa0bt.ampr.org God shows his contempt for wealth by the kind of person He selects to receive it. -- Austin O'Malley

2 participants
1 comments

Re: 21.2.19 crash in ldap on Solaris 2.7 25 years, 1 month

Raymond Toy

>>>>> "Raymond" == Raymond Toy <toy(a)rtp.ericsson.se> writes: Raymond> I got a crash when trying to do an ldap access. 100% repeatable. Raymond> This is the first time I've tried to do that on Solaris 2.7, which Raymond> seems to come with it's own ldap libraries. Previously, I was using Raymond> the UMICH 3.3 ldap libraries on Solaris 2.5.1. I'll have to try using Raymond> the UMICH 3.3 ldap libraries instead of the Solaris 2.7 ones.... Raymond> The C backtrace is: Raymond> #0 0xfeb16870 in _libc_kill () from /usr/lib/libc.so.1 Raymond> #1 0xb1ca4 in fatal_error_signal (sig=6) at emacs.c:276 Raymond> #2 <signal handler called> Raymond> #3 0xfeb16870 in _libc_kill () from /usr/lib/libc.so.1 Raymond> #4 0xfeab92a4 in abort () from /usr/lib/libc.so.1 Raymond> #5 0xb5130 in assert_failed (file=0x29d3d0 "bytecode.c", line=1478, expr=0x29d0c0 "abort()") Raymond> at emacs.c:2672 Raymond> #6 0x7bc70 in execute_rare_opcode (stack_ptr=0xffbecf14, program_ptr=0x7c37be "", opcode=5) Raymond> at bytecode.c:1478 I think this really is due to an invalid bytecode. As a quick test, I removed all of the elc files for eudc and re-did the test. Everything works as expected! My eudc files were obtained from the 1999-07-29 sumo tarballs. I'll try recompiling these files with 21.2.19 or perhaps some other version. (Has the byte-compiler changed between 21.1.x and 21.2.19?) Ray

1 participants
0 comments

Re: xemacs 21.[12].x segfalut if you only put '-t' option 25 years, 1 month

Jan Vroonhof

Yasushi Shoji <yashi(a)yashi.com> writes: > It seems like that latest stable and beta version of XEmacs dies with > Segmentation fault on linux system. Please be more exact. What is the x in 21.1.x ? Was the 21.2 from CVS? If the answer is (x > 4) and yes, then please try.. http://www.xemacs.org/list-archives/xemacs-patches/9910/msg00015.html Jan

3 participants
3 comments

Re: xemacs 21.[12].x segfalut if you only put '-t' option 25 years, 1 month

Jan Vroonhof

Yasushi Shoji <yashi(a)yashi.com> writes: > oops. They are 21.1.7 and 21.2.19. I am not sure whether 21.2.19 already contains patch that introduces the problem so it might well be something different then. > Seems to me that the patch is against to 21.1.7. Am I right? Yes. Jan

1 participants
0 comments

RE: [PATCHES] Re: (call-process ...) to return correct exit-statu s on NT 25 years, 1 month

Bill Tutt

> From: Adrian Aichner [mailto:aichner＠ecf.teradyne.com] > >>>>> "Jonathan" == Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: > > I cannot interrupt > (apply 'call-process "sleep" nil nil nil (list "30")) > short of using Task Manager to "End Process". > Eh? Why not? You can call TerminateProcess() on the process handle you dig up via OpenProcess() &/or CreateProcess(). e.g.: if (!TerminateProcess(hProcess, (UINT)<forced exit code>)) { <insert error handling here> } Bill

1 participants
0 comments

xemacs 21.[12].x segfalut if you only put '-t' option 25 years, 1 month

Yasushi Shoji

hi, It seems like that latest stable and beta version of XEmacs dies with Segmentation fault on linux system. Others on linux-glibc ML and xemacs-users-ja ML can also reproduce this. All system I heard about is on linux with glibc.... This is the backtrace from gdb after you run xemacs with '-t' option only. (gdb) bt #0 0x4010a5f5 in chunk_free () from /lib/libc.so.6 #1 0x4010a4c8 in free () from /lib/libc.so.6 #2 0x400da062 in exit () from /lib/libc.so.6 #3 0x8084c38 in fatal (fmt=0x8190e60 "Option `%s' requires an argument\n") at emacs.c:293 #4 0x8085df8 in sort_args (argc=2, argv=0xbffff904) at emacs.c:1894 #5 0x8085224 in xemacs_21_2_b19_i586_pc_linux (argc=2, argv=0xbffff904, envp=0xbffff910, restart=0) at emacs.c:588 #6 0x80867f4 in main (argc=2, argv=0xbffff904, envp=0xbffff910) at emacs.c:2188 -- yashi

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 October 1999