October 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Gleb Arshinov

Hi, I am using the latest beta of folding.el with XEmacs 21.0 "Finnish Landrace" [Lucid] (i386-pc-win32) (same bug is present with folding.el included with XEmacs). Being a big fan of zmacs-region, I was disappointed to find that folding mode caused my usual way of selecting regions (e.g. to select a line C-space, C-a, C-e) to break :( I discovered that the following 3 functions would unset my mark. Upon reading some documentation, this seems to be caused by an argument to interactive used by these functions. With the following tiny patch, the undesirable behaviour is gone. However, it looks like FSF Emacs does not know about _, so I am not sure which piece of code (XEmacs, FSF Emacs, folding.el) should be fixed. Gleb PS On an unrelated note, is there a way to make isearch open a fold, without entering it, when it finds a match? *** c:\TEMP\orig_folding.el Thu Oct 1 17:24:44 1998 --- c:\TEMP\folding.el7AAFcA Thu Oct 1 17:24:44 1998 *************** *** 2826,2832 **** "Move point right ARG characters, skipping hidden folded regions. Moves left if ARG is negative. On reaching end of buffer, stop and signal error." ! (interactive "p") (if (eq arg 1) ;; Do it a faster way for arg = 1. (if (eq (following-char) ?\r) --- 2826,2832 ---- "Move point right ARG characters, skipping hidden folded regions. Moves left if ARG is negative. On reaching end of buffer, stop and signal error." ! (interactive "_p") (if (eq arg 1) ;; Do it a faster way for arg = 1. (if (eq (following-char) ?\r) *************** *** 2863,2869 **** "Move point left ARG characters, skipping hidden folded regions. Moves right if ARG is negative. On reaching beginning of buffer, stop and signal error." ! (interactive "p") (if (eq arg 1) ;; Do it a faster way for arg = 1. ;; Catch the case where we are in a hidden region, and bump into a \r. --- 2863,2869 ---- "Move point left ARG characters, skipping hidden folded regions. Moves right if ARG is negative. On reaching beginning of buffer, stop and signal error." ! (interactive "_p") (if (eq arg 1) ;; Do it a faster way for arg = 1. ;; Catch the case where we are in a hidden region, and bump into a \r. *************** *** 2904,2910 **** ends with some hidden folded text (represented by an ellipsis), the point is positioned just before it. This prevents the point from being placed inside the folded text, which is not normally useful." ! (interactive "p") (if (or (eq arg 1) (not arg)) (beginning-of-line) --- 2904,2910 ---- ends with some hidden folded text (represented by an ellipsis), the point is positioned just before it. This prevents the point from being placed inside the folded text, which is not normally useful." ! (interactive "_p") (if (or (eq arg 1) (not arg)) (beginning-of-line)

1 participants
0 comments

XEmacs 21.2-beta2 "Aether" is released 26 years, 2 months

SL Baur

[This release was informally announced on xemacs-beta earlier this week] Available from the usual places: ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.2/ CVS sources are at http://cvs.xemacs.org/ Use the release tag `release-21-2' to get this branch. The default branch is XEmacs 21.0. Installable Lisp packages are in: ftp://ftp.xemacs.org/pub/xemacs/packages/ See the 21.0-pre14 announcement for instructions about dealing with the most recent Lisp package updates. XEmacs 21.2 is an experimental, alpha developmental branch of XEmacs. If you haven't installed XEmacs 21.0 and are not comfortable with the packaging system don't try installing it. Currently the differences from 21.2 are fairly slight. ~user completion works in the minibuffer, a large number of obsolete variables has been removed and indirect buffers have been implemented. There is no currently scheduled date for beta3 and it probably won't arrive any time in the very near future. to 21.2 beta2 "Aether" -- Synched with 21.0-pre14 "Poitou" -- isearch improvements from Hrvoje Niksic -- bytecompiler fix from Martin Buccholz -- shadow.el speedup from Martin Buchholz -- clash detection update from Jan Vroonhof -- Indirect buffers from Hrvoje Niksic -- ~user completion cleanup from Greg Klanderman -- New face property from Didier Verna -- ~user completion and fixes from Greg Klanderman -- casefiddle.c speedup from Martin Buchholz

1 participants
0 comments

Success 21.2-mumble on AIX 4.3.1 26 years, 2 months

Valdis Kl=?iso8859-4?Q?=BA?=tnieks

The announcement on Sep 29 said '21.2-pre7', but the tarball on ftp.xemacs.org is labelled 21.2-b2. I patched up from a 21.2-b1, and it seems to be working OK, modulo a few gotchas: 1) I needed --with-dialogs=athena --with-dragndrop=no to keep it from dying an early death. 2) Preliminary testing shows that IBM xlc at -O4 does Bad Things to the configure script (namely, the tests that check for a routine 'main()' in a library. I'll dig more into this once I get ibmcxx 3.6.4 in. /Valdis uname -a: AIX black-ice 3 4 003260504C00 ./configure '-with-gcc=no' '--compiler=xlc' '--cflags=-O3 -qstrict -qlibansi -qarch=ppc -qtune=604 -qproto' '--with-dialogs=athena' '--with-dragndrop=no' '--x-includes=/usr/X11R6.4/include' '--x-libraries=/usr/X11R6.4/lib' '--gung-ho' '--dynamic=yes' '--debug=no' '--error-checking=none' '--with-mule=no' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' XEmacs 21.2-b2 "Aether" configured for `powerpc-ibm-aix4.3.1.0'. Where should the build process find the source code? /home/valdis/src/xemacs-21.2-b1/src What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/aix4-2.h' and `m/ibmrs6000.h' What compiler should XEmacs be built with? xlc_r -O3 -qstrict -qlibansi -qarch=ppc -qtune=604 -qproto Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/dt/include /usr/X11R6.4/include Where do we find X Windows libraries? /usr/dt/lib /usr/X11R6.4/lib Additional header files: /usr/local/include Additional libraries: /usr/local/lib Compiling in support for XAUTH. Compiling in support for XPM images. -------------------------------------------------------------------- WARNING: Compiling without PNG image support. WARNING: You should strongly consider installing the PNG libraries. WARNING: Otherwise certain images and glyphs may not display. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in support for GNU DBM. Compiling in support for ToolTalk. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "lockf" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation.

1 participants
0 comments

Re: package update bug 26 years, 2 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > It's not handling an obsolete package format properly (ie. lack of > pkginfo files). Not it isn't. It is breaking on the fact that the package include the MANIFEST file in the MANIFEST file and therefore it already has been removed in the previous loop deleting all listed files. Anyway this should all be condition-cased. For instance I might have deleted some .el files by hand. I sent a patch to that effect to xemacs-patches. Jan

2 participants
1 comments

package update is not idempotent 26 years, 2 months

Andy Piper

I get auctex installed every time I do an update. Starting and stopping xemacs makes no difference. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

2 participants
1 comments

Re: Can _pkg.el come back? 26 years, 2 months

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > I might need to get at the '(provides-package data for a freshly > installed package. Moreover it is very convenient if the > auto-autoloads.el can be regenerated from the binary package. O.K. This was initially an oversight, but seemed like it might be a good idea. I agree that regenerating the auto-autoloads.el file from the binary package is something that should be doable. If you can deal with getting some but not all of them back, I'll start migrating them back in today's Lisp package update. I'm not going to have time to regenerate all packages until later in the week. O.K.?

3 participants
2 comments

package system is too fragile 26 years, 2 months

Andy Piper

The current package delete is great but too optimistic in its operation. I often end up having the delete fail so that the install doesn't work, but the delete has worked enough so that I don't have the package adn so I am left with a subfucntional XEmacs. Package delete whould try and do all its housekeeping *before* actually nuking the package. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

2 participants
1 comments

[Crash] while expunging messages in vm 6.61 26 years, 2 months

Marcus Thiessel

This is the second time in 10 minutes I had to recover my session. :-( I am wondering if this is Motif related? --[[text/plain]] Reading symbols from /usr/lib/libcanna.sl...done. Reading symbols from /usr/lib/libRKC.sl...done. Reading symbols from /usr/dt/lib/libDtSvc.3...done. Reading symbols from /usr/lib/libXm.4...done. Reading symbols from /usr/lib/libXp.2...done. Reading symbols from /usr/dt/lib/libtt.3...done. Reading symbols from /usr/lib/libnsl.1...done. Reading symbols from /usr/lib/libxti.2...done. Reading symbols from /usr/lib/X11R6/libXt.3...done. Reading symbols from /usr/lib/X11R6/libXext.3...done. Reading symbols from /usr/lib/X11R6/libX11.3...done. Reading symbols from /usr/lib/X11R6/libSM.2...done. Reading symbols from /usr/lib/X11R6/libICE.2...done. Reading symbols from /usr/lib/libm.2...done. Reading symbols from /usr/lib/libc.2...done. Reading symbols from /usr/lib/libdld.2...done. Reading symbols from /usr/lib/libnss_dns.1...done. #0 0xc00f0a10 in kill () from /usr/lib/libc.2 #0 0xc00f0a10 in kill () from /usr/lib/libc.2 (gdb) where #0 0xc00f0a10 in kill () from /usr/lib/libc.2 #1 0x9920c in fatal_error_signal () #2 <signal handler called> #3 0x16bca8 in bufpos_to_bytind_func () #4 0x913d4 in beginning_of_line_p () #5 0x24009c in Fset_window_buffer () #6 0xa58d4 in funcall_recording_as () #7 0xa5af8 in Ffuncall () #8 0x67ce4 in $00000048 () --[[text/plain]] Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. Please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /opt/src/xemacs-21.0-b57/src/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: set-window-buffer(#<window on "INBOX" 0x4d83> #<buffer "INBOX">) # bind (delete-me done all-frames start w obj-2 obj-1 action) vm-window-loop(replace #<buffer "INBOX Presentation"> #<buffer "INBOX">) # bind (new old) vm-replace-buffer-in-windows(#<buffer "INBOX Presentation"> #<buffer "INBOX">) # (unwind-protect ...) # bind (vm-sbe-buffer) vm-preview-current-message() # bind (buffer) #<compiled-function (buffer) "...(73)" [symbol-name buffer vm-system-state vm-garbage-collect-message vm-message-pointer nil vm-folder-type vm-update-summary-and-mode-line vm-preview-current-message major-mode vm-virtual-mode vm-message-order-changed vm-message-order-header-present vm-clear-expunge-invalidated-undos] 2>(INBOX) mapatoms(#<compiled-function (buffer) "...(73)" [symbol-name buffer vm-system-state vm-garbage-collect-message vm-message-pointer nil vm-folder-type vm-update-summary-and-mode-line vm-preview-current-message major-mode vm-virtual-mode vm-message-order-changed vm-message-order-header-present vm-clear-expunge-invalidated-undos] 2> [INBOX 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]) # (unwind-protect ...) # bind (use-marks mp virtual buffers-altered prev virtual-messages shaddap) #<compiled-function (&optional shaddap) "...(964)" [vm-mail-buffer buffer-name error "Folder buffer has been killed." vm-check-for-killed-summary vm-folder-read-only signal folder-read-only vm-update-summary-and-mode-line shaddap message "Expunging..." last-command vm-next-command-uses-marks vm-message-list major-mode vm-virtual-mode make-vector 29 0 nil virtual-messages prev buffers-altered virtual mp use-marks 2 1 vm-thread-obarray vm-unthread-message 5 4 curr vms 9 6 intern vm-set-numbering-redo-start-point t vm-set-summary-redo-start-point vm-message-pointer vm-system-state vm-last-message-pointer inhibit-quit vm-set-deleted-flag-of expunged 3 vm-modification-counter vm-set-buffer-modified-p old-delq vm-numbering-redo-start-point buffer-size vm-sr-max vm-sr-min vm-sr-clip make-marker (...) buffer-read-only vm-display (vm-expunge-folder) (vm-expunge-folder) mapatoms #<compiled-function ... "...(73)" ... 2> "Deleted messages expunged." "No messages are flagged for deletion."] 7 "Expunge messages with the `deleted' attribute.\nFor normal folders this means that the deleted messages are\nremoved from the message list and the message contents are\nremoved from the folder buffer.\n\nFor virtual folders, messages are removed from the virtual\nmessage list. If virtual mirroring is in effect for the virtual\nfolder, the corresponding real messages are also removed from real\nmessage lists and the message contents are removed from real folders.\n\nWhen invoked on marked messages (via vm-next-command-uses-marks),\nonly messages both marked and deleted are expunged, other messages are\nignored." nil>() call-interactively(vm-expunge-folder) # (condition-case ... . error) # (catch top-level ...)

2 participants
2 comments

Re: Doumentation fix request (semi-sorta-urgent) 26 years, 2 months

Greg Klanderman

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Hrvoje> jareth(a)camelot.co.jp (P. E. Jareth Hein) writes: >> I just got a 'bug-report' complaining that regexp-opt generates >> incorrect regexps. Well, asside from the fact that I'm not sure >> regexp-opt should generate shy groups by default, I do notice that >> there is no mention of the shy groups functions or the minimal >> matching operators in the info files. Hrvoje> Hrvoje> Huh? My info files contain this: The problem is that they are documented in the lispref but not the XEmacs manual.

1 participants
0 comments

Re: Doumentation fix request (semi-sorta-urgent) 26 years, 2 months

John Jones

>>>>> Hrvoje Niksic writes: > Huh? My info files contain this: > `*?' > works just like `*', except that rather than matching the > longest match, it matches the shortest match. `*?' is known > as a "non-greedy" quantifier, a regexp construct borrowed from > Perl. > This construct very useful for when you want to match the text > inside a pair of delimiters. For instance, `/\*.*?\*/' will > match C comments in a string. This could not be achieved > without the use of greedy quantifier. Shouldn't that last line be "without the use of a non-greedy quantifier". John Jones jj(a)asu.edu

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 1998