March 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, 7 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. >> 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/

4 participants
3 comments

pcl-cvs buglet 23 years, 4 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, 10 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 Alcorn (mailto:doug＠lathi.net http://www.lathi.net) oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543 |_/ If you're a capitalist and you have the best goods and they're free, you don't have to proselytize, you just have to wait.

4 participants
3 comments

Re: gud.el broken or is it just me? 23 years, 11 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.xemacs.org/pub/xemacs-futures/ when I was on the 'net. It was delayed integration into the XEmacs packages pending 21.0 release. I also have a ported cua-mode.el to integrate. NOTE: The gud.el and cua-mode.el XEmacs portings are courtesy of Altrasoft, Inc. Thank you Altrasoft. Footnotes: [1] I have a report that my port does not work on Solaris with dbx.

2 participants
1 comments

New Package for inclusion into XEmacs: Build 24 years

Adrian Aichner

I have talked about this so long. Now is the time to let it see the harsh light of day (it actually night here, so it shouldn't be too bad). My CVS repository for build is also available if Steve Youngs wants to put in on cvs.xemacs.org as a whole (it's only 110 Kbytes). I'd actually prefer that. It's currently a comm package but that's negociably, of course. For others to test and give me feedback, here is a source kit for the package and the overview page of the included documentation. For those who don't want to hack on it, but would like to try it, here is the familiar binary distribution package: M-x build will get you started and will bring up a harmless widget-based interface. Best regards, Adrian File: build.info, Node: Build Overview, Next: Build Installation, Prev: Top, Up: (dir) Build Overview ************** `build' supports the building process of the `XEmacs' editor from its sources. The build process consists of following steps: 1. Download source code from FTP server or CVS repository. 2. Configure any attributes of the build process, of the resulting XEmacs executable, and of the XEmacs environment. 3. Start the make process to build XEmacs, install it, and run the regression tests. 4. Report on the success or failure of the build, using build-report. The `build' command generates a widget-based interface to configure and build XEmacs either using GNU Tools (`configure', `make') or Microsoft Tools (`nmake' with command-line options (<= 21.2-b32) or `config.inc' configuration file (> 21.2-b32)). -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

5 participants
21 comments

more gtk-xemacs issues 24 years

Isaac Hollander

To add to what hniksic provided yesterday, here are my experiences building xemacs-gtk. I hope this information is useful; I'll keep on digging deeper to figure out what exactly the correct fix. The main issues are: 1) the strange [non]scrollbars; see the attached png. The appended Installation shows that XEmacs thinks it's built with GTK scrollbars. 2) (unimplemented/notice) GTK does not support XPM cursors. If xpm and gtk don't mix then configure should warn to that effect. I tried with both a block cursor and a 1 pixel bar cursor, but the error still occurs. 3) I got the same GTK 1.2.9 error that hniksic reported; somehow configure finds my gtk and gnome libraries anyway. However... 4) Looking at the configure output, we see the following: checking for glade/glade.h... no checking for glade.h... no And in config.log, we see configure:5245: checking for glade/glade.h configure:5253: gcc -E conftest.c >/dev/null 2>conftest.out In file included from /usr/include/glade/glade.h:55, from configure:5249: /usr/include/glade/glade-xml.h:25: glib.h: No such file or directory /usr/include/glade/glade-xml.h:26: gtk/gtkdata.h: No such file or directory /usr/include/glade/glade-xml.h:27: gtk/gtkwidget.h: No such file or directory /usr/include/glade/glade-xml.h:28: gtk/gtktooltips.h: No such file or directory configure: failed program was: #line 5248 "configure" #include "confdefs.h" #include <glade/glade.h> configure:5245: checking for glade.h configure:5253: gcc -E conftest.c >/dev/null 2>conftest.out configure:5249: glade.h: No such file or directory configure: failed program was: #line 5248 "configure" #include "confdefs.h" #include <glade.h> So glade doesn't work because the output of gtk-config and gnome-config wasn't passed by configure to the conftest program. And to make things even more interesting, XEmacs built with -lglade anyway (!). So I'm confused. I was able to force configure to use the correct includes by adding ${GTK_INCLUDES} and ${GNOME_INCLUDES} to the command line used to build the conftest, but that's obviously not the right answer. Installation: uname -a: Linux yitzchak 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown ../gx/configure '--with-xfs' '--with-gtk=yes' '--with-gnome=yes' '--with-xface' '--extra-verbose' '-debug' '--cache-file=/dev/null' '--external-widget' XEmacs 21.2-b46 "Urania" configured for `i686-pc-linux'. Compilation / Installation: Source code location: /home/ysh/xecvs/gx Installation prefix: /usr/local Operating system description file: `s/linux.h' Machine description file: `m/intel386.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wshadow Relocating allocator for buffers: no GNU version of malloc: yes - Using Doug Lea's new malloc from the GNU C Library. Window System: Using GTK menubars. Using GTK scrollbars. Using GTK dialog boxes. Using GTK native widgets. TTY: Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. Compiling in support for PNG images. Compiling in support for JPEG images. Compiling in support for TIFF images. Compiling in support for X-Face message headers. Sound: Compiling in support for sound (native). Compiling in support for ESD (Enlightened Sound Daemon). Databases: Compiling in support for Berkeley database. Compiling in support for LDAP. Internationalization: - Using XFontSet to provide bilingual menubar. Mail: Compiling in support for "dot-locking" mail spool file locking method. Other Features: Compiling in support for dynamic shared object modules. Compiling in support for extra debugging code. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- PNG image of fresh gtk-xemacs:

4 participants
3 comments

[comp.emacs.xemacs,comp.emacs] vc problems in XEmacs 21.1.14 24 years

Steve Youngs

Could somebody please take a look at this. Adrian, you were the last person to sync VC, perhaps you could give it a look. Thanks. -- |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---|

4 participants
9 comments

Re: Seen in configure.usage 24 years

Jan Vroonhof

Valdis.Kletnieks(a)vt.edu writes: > Not sure if that's a bug or a feature. Anybody want to get configure.in > and configure.help into sync? That would be very nice for the release... Jan

4 participants
3 comments

make gnus failed 24 years

zhaoway

Hi, When I type make under xemacs-packages/comm/gnus/, I have following fail message. Even after I export LC_ALL=C, it's all the same. But if I load it in <<XEmacs 21.1 (patch 13) "Crater Lake" [Lucid] (i386-debian-linux, Mule)>> then byte compile it, it's okay. Please, any hints are welcome! Thanks! -- �� <http://www.zhaoway.com/> make: Circular gnus/lisp/auto-autoloads.el <- gnus/lisp/auto-autoloads.el dependency dropped. /usr/local/bin/xemacs -no-autoloads -batch -l /home/zw/xemacs/xemacs-packages/package-compile.el -- gnus w3 mh-e mailcrypt rmail eterm mail-lib xemacs-base fsf-compat -- gnus/lisp/gnus-async.el Loading /usr/local/lib/xemacs-21.2-b45/lisp/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/libs/fsf-compat/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/libs/xemacs-base/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/libs/mail-lib/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/os/eterm/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/comm/rmail/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/comm/mailcrypt/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/comm/mh-e/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/comm/w3/lisp/auto-autoloads... Loading /.q2/xemacs/xemacs-packages/comm/gnus/ gnus/lisp/auto-autoloads... Compiling /.q2/xemacs/xemacs-packages/comm/gnus/gnus/lisp/gnus-async.el... While compiling toplevel forms in file /.q2/xemacs/xemacs-packages/comm/gnus/gnus/lisp/gnus-async.el: !! Invalid read syntax (("\")\" in a vector")) backtrace(nil t) # bind (error-info) byte-compile-report-error((invalid-read-syntax "\")\" in a vector")) # bind (error-info) #<compiled-function (error-info) "...(4)" [error-info byte-compile-report-error] 2>((invalid-read-syntax "\")\" in a vector")) # bind (current-load-list) # (unwind-protect ...) # bind (load-file-name) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load-internal("gnus-group" nil t nil undecided) # bind (path handler filename nosuffix nomessage noerror file) load("gnus-group" nil t nil) # (unwind-protect ...) require(gnus-group) # bind (current-load-list) # (unwind-protect ...) # bind (load-file-name) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load-internal("gnus-sum" nil t nil undecided) # bind (path handler filename nosuffix nomessage noerror file) load("gnus-sum" nil t nil) # (unwind-protect ...) require(gnus-sum) eval((require (quote gnus-sum))) # bind (form) byte-compile-file-form-eval-boundary((require (quote gnus-sum))) # bind (byte-compile-current-form handler form) byte-compile-file-form((require (quote gnus-sum))) # (unwind-protect ...) #<compiled-function nil "...(43)" [byte-compile-unresolved-functions byte-compile-inbuffer 1 " \n" nil looking-at ";" byte-compile-file-form read byte-compile-flush-pending byte-compile-warn-about-unresolved-functions] 3>() # (unwind-protect ...) call-with-condition-handler(#<compiled-function (error-info) "...(4)" [error-info byte-compile-report-error] 2> #<compiled-function nil "...(43)" [byte-compile-unresolved-functions byte-compile-inbuffer 1 " \n" nil looking-at ";" byte-compile-file-form read byte-compile-flush-pending byte-compile-warn-about-unresolved-functions] 3>) # (unwind-protect ...) # bind (byte-compile-warnings-beginning byte-compile-point-max-prev byte-compile-log-buffer byte-compile-macro-environment byte-compile-function-environment byte-compile-autoload-environment byte-compile-unresolved-functions byte-compile-bound-variables byte-compile-free-references byte-compile-free-assignments byte-compile-verbose byte-optimize byte-compile-emacs19-compatibility byte-compile-dynamic byte-compile-dynamic-docstrings byte-compile-warnings byte-compile-file-domain byte-compile-outbuffer float-output-format case-fold-search print-length print-level byte-compile-constants byte-compile-variables byte-compile-tag-number byte-compile-depth byte-compile-maxdepth byte-compile-output eval filename byte-compile-inbuffer) byte-compile-from-buffer(#<buffer " *Compiler Input*"> "/.q2/xemacs/xemacs-packages/comm/gnus/gnus/lisp/gnus-async.el") # bind (byte-compile-current-file target-file input-buffer output-buffer byte-compile-dest-file load filename) byte-compile-file("gnus/lisp/gnus-async.el") byte-code("..." [file byte-compile-file t] 2) # (condition-case ... . ((error (byte-code "XXXXXXX deleted because I can't send it from Gnus ??? XXXXXXX" ... 3)))) # bind (file) batch-byte-compile-1("gnus/lisp/gnus-async.el") # bind (error file-to-process) batch-byte-compile-one-file() # bind (error) batch-byte-compile() # bind (current-load-list) # (unwind-protect ...) # bind (load-file-name) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load-internal("/home/zw/xemacs/xemacs-packages/package-compile.el" nil t nil undecided) # bind (path handler filename nosuffix nomessage noerror file) load("/home/zw/xemacs/xemacs-packages/package-compile.el" nil t) # bind (file arg) command-line-do-load("-l") # bind (dir file-count line end-of-options file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) >>Error occurred processing gnus/lisp/gnus-async.el: Invalid read syntax: "\")\" in a vector" Done make: *** [gnus/lisp/gnus-async.elc] Error 1

2 participants
1 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 March 2001