April 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Ian MacKinnon

I am trying to create some html files When I edit a .html file I go into psgml with hm--html-menus When I right click, I get an Element Menu, When I pick an element nothing happens Should it insert the element ? This is on 21.2 beta 46 on win2k under cygwin -- Ian

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

xemacs vc suggestion 24 years

Albert Ting

So that I don't look like I'm always submitting bugs, here's a vc suggestion. ;) I submitted this patch to the regular xemacs mailing list, but didn't hear anything. In any case, I find this useful. It highlights the RCS/CVS text in the modeline if the file is checked out. Much easier to detect a changed file instead of looking for a "-" vs. a ":" in the modeline. It's currently defined as a defadvice. Thanks, Albert (when xemacs-p (defvar vc-mode-ext (detach-extent (make-extent 0 0 ""))) (set-extent-face vc-mode-ext 'highlight) (defadvice vc-mode-line (after highlight activate) "highlight CVS/RCS tag if file is modified locally" (let* ((str vc-mode) (hdr "^ \\(CVS\\|RCS\\)") (locked-hdr (concat hdr "-"))) (when (and str ;; initial version may start with nil (string-match hdr str) (not (string-match locked-hdr str))) (let ((substr (substring str 1))) ;; normally modeline displays whatever is in the minor-mode-alist, ;; indexed by mode. The cdr can be either a string or (extent ;; . str) or a list of them. vc-mode is normally set to a string. ;; Change the variable to specify an extent, preceded by a regular ;; space (setq vc-mode (list " " (cons vc-mode-ext substr))))))) )

2 participants
1 comments

Experimental ilisp package installation fails 24 years

Adrian Aichner

Hello Steve, ilisp installation with package-get-remote of (("ftp.xemacs.org" "xemacs/beta/experimental/packages/")) just failed with this output: ./pkginfo/MANIFEST.ilisp ./lisp/ilisp/COPYING ./lisp/ilisp/ChangeLog ./lisp/ilisp/GETTING-ILISP ./lisp/ilisp/HISTORY ./lisp/ilisp/INSTALLATION ./lisp/ilisp/Makefile ./lisp/ilisp/README ./lisp/ilisp/Welcome ./lisp/ilisp/_pkg.el ./lisp/ilisp/allegro.lisp ./lisp/ilisp/auto-autoloads.el ./lisp/ilisp/auto-autoloads.elc ./lisp/ilisp/bridge.el ./lisp/ilisp/bridge.elc ./lisp/ilisp/cl-chs-init.lisp ./lisp/ilisp/cl-ilisp.lisp ./lisp/ilisp/cmulisp.lisp ./lisp/ilisp/comint-ipc.el ./lisp/ilisp/comint-ipc.elc ./lisp/ilisp/comint-v18.el ./lisp/ilisp/completer.el ./lisp/ilisp/completer.elc ./lisp/ilisp/custom-ilisp.el ./lisp/ilisp/custom-ilisp.elc ./lisp/ilisp/ilcompat.el ./lisp/ilisp/ild.el ./lisp/ilisp/ilfsf18.el ./lisp/ilisp/ilfsf19.el ./lisp/ilisp/ilfsf20.el ./lisp/ilisp/ilisp-acl.el ./lisp/ilisp/ilisp-acl.elc ./lisp/ilisp/ilisp-aut.el ./lisp/ilisp/ilisp-aut.elc ./lisp/ilisp/ilisp-bat.el ./lisp/ilisp/ilisp-bug.el ./lisp/ilisp/ilisp-chs.el ./lisp/ilisp/ilisp-chs.elc ./lisp/ilisp/ilisp-cl-easy-menu.el ./lisp/ilisp/ilisp-cl.el ./lisp/ilisp/ilisp-cl.elc ./lisp/ilisp/ilisp-cmp.el ./lisp/ilisp/ilisp-cmp.elc ./lisp/ilisp/ilisp-cmt.el ./lisp/ilisp/ilisp-cmt.elc ./lisp/ilisp/ilisp-cmu.el ./lisp/ilisp/ilisp-cmu.elc ./lisp/ilisp/ilisp-def.el ./lisp/ilisp/ilisp-def.elc ./lisp/ilisp/ilisp-dia.el ./lisp/ilisp/ilisp-dia.elc ./lisp/ilisp/ilisp-doc.el ./lisp/ilisp/ilisp-doc.elc ./lisp/ilisp/ilisp-ext.el ./lisp/ilisp/ilisp-ext.elc ./lisp/ilisp/ilisp-hi.el ./lisp/ilisp/ilisp-hi.elc ./lisp/ilisp/ilisp-hlw.el ./lisp/ilisp/ilisp-hlw.elc ./lisp/ilisp/ilisp-hnd.el ./lisp/ilisp/ilisp-hnd.elc ./lisp/ilisp/ilisp-imenu.el ./lisp/ilisp/ilisp-ind.el ./lisp/ilisp/ilisp-ind.elc ./lisp/ilisp/ilisp-inp.el ./lisp/ilisp/ilisp-inp.elc ./lisp/ilisp/ilisp-kcl.el ./lisp/ilisp/ilisp-kcl.elc ./lisp/ilisp/ilisp-key.el ./lisp/ilisp/ilisp-key.elc ./lisp/ilisp/ilisp-kil.el ./lisp/ilisp/ilisp-kil.elc ./lisp/ilisp/ilisp-low.el ./lisp/ilisp/ilisp-low.elc ./lisp/ilisp/ilisp-luc.el ./lisp/ilisp/ilisp-luc.elc ./lisp/ilisp/ilisp-mak.el ./lisp/ilisp/ilisp-menu.el ./lisp/ilisp/ilisp-mnb.el ./lisp/ilisp/ilisp-mnb.elc ./lisp/ilisp/ilisp-mod.el ./lisp/ilisp/ilisp-mod.elc ./lisp/ilisp/ilisp-mov.el ./lisp/ilisp/ilisp-mov.elc ./lisp/ilisp/ilisp-out.el ./lisp/ilisp/ilisp-out.elc ./lisp/ilisp/ilisp-pkg.lisp ./lisp/ilisp/ilisp-prc.el ./lisp/ilisp/ilisp-prc.elc ./lisp/ilisp/ilisp-prn.el ./lisp/ilisp/ilisp-prn.elc ./lisp/ilisp/ilisp-rng.el ./lisp/ilisp/ilisp-rng.elc ./lisp/ilisp/ilisp-s2c.el ./lisp/ilisp/ilisp-sbcl.el ./lisp/ilisp/ilisp-sbcl.elc ./lisp/ilisp/ilisp-sch.el ./lisp/ilisp/ilisp-sch.elc ./lisp/ilisp/ilisp-scheme-easy-menu.el ./lisp/ilisp/ilisp-snd.el ./lisp/ilisp/ilisp-snd.elc ./lisp/ilisp/ilisp-src.el ./lisp/ilisp/ilisp-sym.el ./lisp/ilisp/ilisp-sym.elc ./lisp/ilisp/ilisp-utl.el ./lisp/ilisp/ilisp-utl.elc ./lisp/ilisp/ilisp-val.el ./lisp/ilisp/ilisp-val.elc ./lisp/ilisp/ilisp-xfr.el ./lisp/ilisp/ilisp-xfr.elc ./lisp/ilisp/ilisp-xls.el ./lisp/ilisp/ilisp-xls.elc ./lisp/ilisp/ilisp.el ./lisp/ilisp/ilisp.elc ./lisp/ilisp/ilisp.emacs ./lisp/ilisp/illuc19.el ./lisp/ilisp/ilxemacs.el ./lisp/ilisp/lispworks.lisp ./lisp/ilisp/lucid.lisp ./lisp/ilisp/sblisp.lisp ./lisp/ilisp/extra//README ./lisp/ilisp/extra//hyperspec-barlow.el ./lisp/ilisp/extra//hyperspec-carney.el ./lisp/ilisp/extra//hyperspec-naggum.el ./lisp/ilisp/extra//hyperspec.el ./;ELC Error: unknown type flag 2. Exiting. Error: incorrect magic number in tar header. Exiting Error: unknown type flag ;. Exiting. Error: cannot create file ./;ELC. Exiting. This with (emacs-version) "XEmacs 21.1 (patch 13) \"Crater Lake\" [Lucid] (i386-pc-win32) of Thu Jan 11 2001 on ANDYP" Adrian -- Adrian Aichner <adrian(a)xemacs.org>

2 participants
1 comments

Buffer Tab bug/feature? 24 years

Nickolay Pakoulin

Buffer Tab does not redraws when switching to buffer with leading space in name. test case: (switch-to-buffer " TMP") I expected the buffers tab to display buffers in Fundamantal mode including " TMP", but the buffer tab remained the same. I agree that usually the buffers tab should not display buffers with names with leading spaces. Nevertheless, if a user explicitly switches to a buffer with such name then the buffers tab should respect user and show the name of the current buffer. Nick. The patch introduces needed behaviour: ---------------------------------------------------------------------- diff -u -r1.1.2.60 gutter-items.el --- gutter-items.el 2001/03/15 16:28:42 1.1.2.60 +++ gutter-items.el 2001/04/10 13:59:49 ＠＠ -249,7 +249,12 ＠＠ ;; context buffer before they get run. (let* ((buffers (delete-if buffers-tab-omit-function (buffer-list frame))) - (first-buf (car buffers))) + first-buf) + (if (eq (minibuffer-window frame) (selected-window)) + (setq first-buf (car buffers)) + (setq first-buf (window-buffer (selected-window))) + (unless (memq first-buf buffers) + (push first-buf buffers))) ;; maybe force the selected window (when (and force-selection (not in-deletion)

1 participants
0 comments

Dired 7.10alpha package available for testing 24 years

Michael Sperber

I've finally zipped through most of the outstanding patches for Dired, applied them, did some work of my own, and checked a new Dired into the packages CVS repo, dubbed 7.10 AKA package version 1.10. Please give it a try and let me know how it goes, whether good or bad. Note that I need both success and failure reports to make an actual package release. Please try Dired on as many systems as you have access to, and use it via EFS to remotely edit directories on as many systems as possible. I'm especially interested in Windows, as I don't test on that platform myself. Let me know (via personal email) how it goes. Dired 7.10 no longer provides its own diff-parsing mode in diff.el but instead relies on Stefan Monnier's diff-mode which is not in the XEmacs package tree yet. I have finished a port of diff-mode and expect it to be integrated within the next few days. Until then, you can still use Dired, it's only the diff functionality which won't work. Since the absence of diff-mode also does affect compilability, I've put a binary package at http://www-pu.informatik.uni-tuebingen.de/users/sperber/software/efs/dire... Steve (Youngs, that is): Under no circumstances release the present code until I give the thumbs-up. I apologize for taking so long with this. It's not as easy as it looks. I appreciate your willingness to help test Dired. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

Lazy lock and new syntax stuff? 24 years

Raymond Toy

I use lazy lock all the time and it has worked beautifully for me until b46. Now, it incorrectly fontifies things. Is this due to the new syntax stuff? As an example, if you have some lisp code commented out with #| and |# that spans more than a screenful, and then scroll (by screens) past it, the comment is only partially highlighted and things past the terminating |# are highlighted as comments when they are, in fact, real code. This is somewhat annoying. Ray

1 participants
0 comments

New SUMO packages in Pre-Releases - April 8th 24 years

Steve Youngs

I've just uploaded new SUMO packages, 'xemacs-sumo-2001-04-08.tar.gz' & 'xemacs-mule-sumo-2001-04-08.tar.gz', to ftp.xemacs.org, you can find them in: /pub/xemacs/beta/experimental/packages/ This release does _not_ include either Eicq or JDE. Eicq has been left out because of compatibility issues, and JDE because of tar issues. You can still get both of these packages in the normal way. This SUMO release is what will be going into the upcoming 21.4 release so please let me know if anything is broken. The following individual packages are also currently in the Pre-Releases directory: cc-mode-1.24-pkg.tar.gz ediff-1.30-pkg.tar.gz edit-utils-1.57-pkg.tar.gz eicq-1.04-pkg.tar.gz eieio-1.01-pkg.tar.gz gnus-1.55-pkg.tar.gz ilisp-1.16-pkg.tar.gz jde-1.26-pkg.tar.gz mail-lib-1.36-pkg.tar.gz pcl-cvs-1.53-pkg.tar.gz prog-modes-1.35-pkg.tar.gz psgml-1.23-pkg.tar.gz semantic-1.05-pkg.tar.gz speedbar-1.19-pkg.tar.gz vhdl-1.13-pkg.tar.gz viper-1.25-pkg.tar.gz vm-6.92-pkg.tar.gz xemacs-base-1.51-pkg.tar.gz xslt-process-1.01-pkg.tar.gz -- |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---|

2 participants
2 comments

widget-button-click should use mouse-track 24 years

Ben Wing

hrvoje, it looks like you're the maintainer of wid-edit. i'm trying to modify about.el so that button1 as well as button2 selects a link. i notice a few problems with wid-edit: 1] it doesn't provide any obvious way of controlling which buttons do what. 2] all of the modal loops in it should be eliminated and rewritten using mouse-track hooks. i originally wrote the mouse-track hooks to be very flexible and allow for multiple simultaneous actions with different mouse gestures -- e.g. selection of text at the same time as doing something on a "click", i.e. down+up without significant movement. last year i extended mouse-track so it will work with all buttons, and changed the default binding of button2 to use it as well as button1. when drag/drop gets implemented, it can entirely be done using mouse-track hooks even if the dragging is to be done with button2. your code in wid-edit tries to do some of the same things, but not so well -- e.g. it doesn't handle text selection. rewriting it using mouse-track hooks will get you these benefits and others for free and make the code in wid-edit smaller and simpler. e.g. you won't have to manually apply mouse-face, glyph up/down, etc. i will gladly help you if you run into any problems with mouse-track in the process of making this change. btw point #1 comes for free if you use the activation mechanism i recently wrote, which sits on top of mouse-track and provides exactly the "do an action upon click" that you implement in wid-edit. -- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.

2 participants
1 comments

problematic change of 2000-11-07 for "Fix C-x @ h <scrollbar-drag> a crash" 24 years

Ben Wing

yoshiki, you made a change of 2000-11-07 to event-stream.c, commented: * event-stream.c (execute_command_event): Preserve current_events and the like when event is misc-user-event. Inhibit quit during the call to maybe_echo_keys. My patch "Fix C-x ＠ h <scrollbar-drag> a crash", <87ofzthdgr.fsf(a)sodan.org> unfortunately, this causes problems because [this-command-keys] returns bogus values after a misc-user-event. to see the problem, do Help->About XEmacs... and click on any of the hyperlinks with button1. part of your change looks like this: /* Emacs 18 doesn't unconditionally clear the echoed keystrokes, so we don't either */ - reset_this_command_keys (make_console (con), 0); + if (XEVENT (event)->event_type != misc_user_event) + reset_this_command_keys (make_console (con), 0); commenting this out fixes the problem. however, i have absolutely no idea if this interferes with the original patch. yoshiki, it's *extremely* important when you modify code as subtle as the event-stream code that you comment exactly why you did it. instead, your only comment is - reset_current_events (command_builder); + /* To fix C-x ＠ h <scrollbar-drag> x crash. */ + if (XEVENT (event)->event_type != misc_user_event) + reset_current_events (command_builder); which gives no information as to why you added this check. could you please explain what's going on here? -- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.

1 participants
0 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