April 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Ben Wing

I've compiled a short list of bugs that I consider to be showstoppers for the 21.0 release. It's located at: http://devel.xemacs.org/xemacs/showstoppers.html Ben (typed by Martin)

6 participants
6 comments

Re: Commenting out code in lisp 7 years, 6 months

Adrian Aichner

>>>>> "Paul" == Paul Krause <paulkrause1(a)mediaone.net> writes: Paul> Adrian Aichner <adrian(a)xemacs.org> writes: >> >> Do we want to make C-u M-x comment-region smarter? >> Paul> No! Make indentation smarter. If a comment begins in column Paul> 1, don't Paul> indent it when reindenting a region. This solves the Paul> problem without Paul> style-changes or hacks to comment-region. >> … [View More] Paul> Have I overlooked anything? >> >> This, maybe? >> >> (Info-goto-node "(xemacs)Comments") >> >> Adrian Paul> Could you be a little more specific? I don't what you're Paul> referring to. Maybe this? Paul> You can also use `Meta-;' to align an existing comment. If a line Paul> already contains the string that starts comments, `M-;' just moves Paul> point after it and re-indents it to the conventional place. Paul> Exception: Paul> comments starting in column 0 are not moved. Yes, that, and also the following paragraph. Some major modes have special rules for indenting certain kinds of comments in certain contexts. For example, in Lisp code, comments which start with two semicolons are indented as if they were lines of code, instead of at the comment column. Comments which start with three semicolons are supposed to start at the left margin. Emacs understands these conventions by indenting a double-semicolon comment using TAB and by not changing the indentation of a triple-semicolon comment at all. You have a valid point, though. single-; comments srarting in column 0 should not be moved and comment-region would work as advertised! You opened my eyes! To All: Isn't this what we should do? Martin? Stephen? Best regards, Adrian Paul> The trouble is, it doesn't work as documented. Here's a sample. Paul> ;;; header comment Paul> ;; This function is just an example. Paul> ;;; Here either two or three semicolons are appropriate. Paul> (defun foo (x) Paul> ;;; And now, the first part of the function: Paul> (lambda (foo bar) Paul> (if (foo bar) Paul> 'bif Paul> 'baz)) Paul> ;; The following line adds one. Paul> (1+ x)) ; This line adds one. Paul> ;; This function is just an example. Paul> ;;; Here either two or three semicolons are appropriate. Paul> (defun foo (x) Paul> ;;; And now, the first part of the function: Paul> ;; The following sexp is commented out using comment-region. Paul> ; (lambda (foo bar) Paul> ; (if (foo bar) Paul> ; 'bif Paul> ; 'baz)) Paul> ;; The following line adds one. Paul> (1+ x)) ; This line adds one. Paul> I get the same indentation using either M-; or C-M-q. Paul> Testing using xemacs -vanilla on Paul> XEmacs 21.2 (beta37) "Pan" (win32) of Sun Dec 03 2000 on PAULKRAUSE Paul> as well as Paul> XEmacs 21.0 "20 minutes to Nikko" (win32) of Fri Mar 26 1999 on Paul> BLACKBIRD Paul> (which I just happen to have lying around) -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/ [View Less]

4 participants
3 comments

pcl-cvs buglet 23 years, 2 months

Neal D. Becker

I marked a bunch of files in pcl-cvs mode. Then I chose "undo changes" from the menu. It prompts "Delete 8 files?". Rather misleading.

4 participants
13 comments

GTK+ and 21.2 23 years, 9 months

Doug Alcorn

After seeing the "Call for Testers" for 21.2/22.0, I thought I would jump on the bandwagon. I'm primarily interested in the GTK+ port. So, I went out and grabbed the latest xemacs from cvs with: $ cvs -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout -d xemacs-21.2 -r release-21-2 xemacs When I run ./configure, I don't see anything about enabling gtk+. Has the gtk+ port been merged in with 21.2 yet? Is it the default toolkit? How do I compile xemacs with GTK+ support? -- (__) Doug … [View More]

4 participants
3 comments

gtkrc (stupid?) questions 23 years, 9 months

Andrew W. Nosenko

For XEmacs 2.1.12 "GTK" I can set default font from gtkrc by next lines: style "XEmacsText" { font = "-cronyx-courier-medium-r-*-*-*-120-*-*-*-*-*-*" } widget_class "*GtkXEmacs" style "XEmacsText" But for XEmacs 2.4.0 configured --with-gtk this not work. Question: How I can do this? Additional info: 1. Full name of required font is -Cronyx-Courier-Medium-R-Normal--17-120-100-100-M-90-KOI8-R 2. Both XEmacses builded without MULE. Second Question: from where apart … [View More]

2 participants
1 comments

Re: gud.el broken or is it just me? 23 years, 9 months

SL Baur

Aki Vehtari <Aki.Vehtari(a)hut.fi> writes in xemacs-beta(a)xemacs.org: ... > Btw. gud.el in XEmacs is dated 1993 and gud.el in emacs-20.3 is > dated 1998. Unfortunately gud.el in emacs-20.3 does not work in > XEmacs and I don't know much work it would need to make it work and I've done the initial port of gud.el to XEmacs. It mostly works[1], but it sorely lacks the functionality in gdbsrc.el. Making a gudsrc.el mode is on my list of things to do. It was in ftp://altair.… [View More]

2 participants
1 comments

Digital UNIX and regex.c with REGEX_MALLOC defined. 23 years, 9 months

Aki Vehtari

Last week I asked about XEmacs-21.4.0 crashing on Digital Unix and Gunnar Evermann pointed out that this problem is already reported in PROBLEMS file. As Stephen just told that bug reports should be preferably sent to xemacs-beta list, below is copy of article sent to comp.emacs.xemacs few days ago. And my question is that should the REGEX_MALLOC definition work? "Gunnar" == Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: Gunnar> maybe this entry from the PROBLEMS file helps: … [View More]Gunnar> ** Digital UNIX/OSF/VMS/Ultrix Gunnar> *** XEmacs crashes on Digital Unix within font-lock, or when dealing Gunnar> with large compilation buffers. Yes, this entry describes the problem, but... Gunnar> 1) Increase your stack size, using `ulimit -s 8192' or a (t)csh Gunnar> equivalent; In our current environment it is not easy to set this for our all users. Moreover, it would not prevent crashing, just make it more unprobable. So I would prefer other solution... Gunnar> 2) Recompile regex.c with REGEX_MALLOC defined. I configured with --cppflags=-DREGEX_MALLOC but... gcc -c -O3 -I. -I../src -I/proj/ave/xemacs/xemacs-21.4.0/lib-src -I/proj/ave/xemacs/xemacs-21.4.0/src -DREGEX_MALLOC -DHAVE_CONFIG_H -I/usr/local/include \ -DINHIBIT_STRING_HEADER /proj/ave/xemacs/xemacs-21.4.0/src/regex.c /proj/ave/xemacs/xemacs-21.4.0/src/regex.c: In function `sys_re_compile_fastmap': /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3412: `DECLARE_NOTHING' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3412: (Each undeclared identifier is reported only once /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3412: for each function it appears in.) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3415: parse error before `char' /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3439: `fastmap' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3445: `p' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3445: `pend' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3450: `path_can_be_null' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:3822: `succeed_n_p' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c: In function `re_match_2_internal': /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:5053: `DECLARE_NOTHING' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:5053: parse error before `int' /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:5053: `this_reg' undeclared (first use this function) /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:5204: parse error before `int' /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:5257: parse error before `int' /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:5460: parse error before `int' /proj/ave/xemacs/xemacs-21.4.0/src/regex.c:5473: parse error before `int' make[1]: *** [regex.o] Error 1 make[1]: Leaving directory `/tmp_mnt/chaos.lce.hut.fi/proj/ave/ave/xemacs/build/alpha-dec-osf4.0/lib-src' make: *** [lib-src] Error 2 Aki [View Less]

7 participants
11 comments

Question about bug reporting 23 years, 10 months

Aki Vehtari

Sending bug report using menu entry "Help - Send Bug Report" would send bug report to xemacs(a)xemacs.org (at least in XEmacs 21.4). In wep page <http://cvs.xemacs.org/XEmacs-bugs> it says that bug resports should be sent to xemacsbugs(a)cvs.xemacs.org. Which one I should use? I suppose that xemacsbugs(a)cvs.xemacs.org would be more appropriate? Aki

2 participants
3 comments

mule question 23 years, 10 months

John A. Turner

I've always build w/o mule, but a colleague needs mule he's building his own executable, but I thought we might as well share the same packages tree, since we saw that the mule-sumo tarball just has the extra mule stuff in it - it un-tars nicely into its own mule-packages subdir in lib/xemacs, parallel to the xemacs-packages I was already using but now when I start my non-mule xemacs I see these warnings: (1) (warning/warning) Autoload error in: /usr/net/rnd/lib/xemacs/mule-packages/lisp/skk/… [View More]

4 participants
5 comments

make-charset doesn't handle 'short-name' properly 23 years, 10 months

Yoshiaki Kasahara

Accidentally I noticed that 'make-charset' doesn't handle a property 'short-name' correctly. Here is a patch for that. Index: mule-charset.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/mule-charset.c,v retrieving revision 1.19 diff -u -r1.19 mule-charset.c --- mule-charset.c 2001/04/12 18:24:03 1.19 +++ mule-charset.c 2001/04/25 08:03:28 ＠＠ -693,7 +693,7 ＠＠ short_name = value; } - if (… [View More]

3 participants
5 comments

2025

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 2001