February 2007 - XEmacs-Beta - XEmacs Mailing List Archives

[Bug: 21.4.20] Network Drives 17 years, 9 months

Stephen J. Turnbull

Steve Higham writes: > I have just reinstalled latest stable version of Xemacs. However any file > opened on a network drive (e.g. S:\Misc\ToDo.txt) opens as a read-only > buffer regardless of whether the file has the read only attribute set. The patch described in the log below is one of the main reasons for the release of 21.4.20, and it was intended to *fix* these access problems. 2006-11-19 Benson Margulies <benson(a)dchbk.us> * fileio.c: Add code to use full Win32 API to check for write access. Win32 has the general design policy that you aren't supposed to ask this question, since security checks change depending on asynchronous processes. Nonetheless, there is a way, by acting as if we are a server doing interpretive access control. Feel free to weep. Any ideas, Benson? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

XEmacs Packages have been pre-released (2007-02-27-21) 17 years, 9 months

Norbert Koch

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey there everyone. I have just added the following packages to the 'Pre-Releases' directory: New Packages in Pre-Release: =========================== bbdb-1.32-pkg.tar.gz upstream version: 2.35 Previously Announced Packages Still in Pre-Release: ================================================== auctex-1.47-pkg.tar.gz upstream version: 11.55 calendar-1.31-pkg.tar.gz upstream version: none docbookide-0.08-pkg.tar.gz upstream version: 0.1 ediff-1.68-pkg.tar.gz upstream version: 2.75 edit-utils-2.37-pkg.tar.gz upstream version: none latin-unity-1.20-pkg.tar.gz upstream version: 1.20 mail-lib-1.79-pkg.tar.gz upstream version: none misc-games-1.19-pkg.tar.gz upstream version: none net-utils-1.51-pkg.tar.gz upstream version: N/A prog-modes-2.10-pkg.tar.gz upstream version: none sh-script-1.22-pkg.tar.gz upstream version: 2.0f tramp-1.35-pkg.tar.gz upstream version: 2.0.55 viper-1.55-pkg.tar.gz upstream version: 3.09 Detailed Changes: ================ - ------- ChangeLog Entries from xemacs-packages/bbdb/ChangeLog ------- 2007-02-27 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.32 released. Installing These: ================ Manually: - -------- 1) Download the packages that you want to install from: /ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/ 2) Unpack them to: [1] /usr/local/lib/xemacs/xemacs-packages/ 3) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.[245].x): - ---------------------------------------------- 1) Tools -> Packages -> Add Download Site -> Pre-Releases 2) Tools -> Packages -> List and Install 3) Select the packages you wish to install (there are brief instructions at the bottom of the packages buffer). 4) Packages -> Install/Remove Selected 5) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.1.14): - ------------------------------------------- 1) Options -> Manage Packages -> Add Download Site -> Pre-Releases 2) Options -> Manage Packages -> List and Install 3 - 5) As per XEmacs 21.[245].x. norbert - XEmacs Package Release Manager. Footnotes: [1] Note: Mule packages should be installed into: /usr/local/lib/xemacs/mule-packages/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFF5JJXgu3ywdHdhM0RAsvMAJ4qivvXpv08faXQhvHyoq/7ewbFmACg8n9F BfpgW6jpPWp/wVbn2vfx8dc= =H25E -----END PGP SIGNATURE----- _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

xemacs issue 17 years, 9 months

Anish Arora

Hi, I get: Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. Your version of XEmacs was distributed with a PROBLEMS file that may describe your crash, and with luck a workaround. Please check it first, but do report the crash anyway. Please report this bug by invoking M-x report-emacs-bug, or by selecting `Send Bug Report' from the Help menu. If necessary, send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the XEmacs configuration from M-x describe-installation, or equivalently the file Installation in the top of the build tree. *Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely to be able to analyze the problem. Locate the core file produced as a result of this crash (often called `core' or `core.<process-id>', and located in the directory in which you started XEmacs or your home directory), and type gdb /usr/bin/xemacs core then type `where' at the debugger prompt. No GDB on your system? You may have DBX, or XDB, or SDB. (Ask your system administrator if you need help.) If no core file was produced, enable them (often with `ulimit -c unlimited' in case of future recurrance of the crash. Lisp backtrace follows: # bind (frame-being-created) make-frame(nil #<x-device on "msi-pa-2059.marvell.com:1.0" 0xa8f>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " Â§" ... 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) [1] Segmentation fault /usr/bin/xemacs aarora(pegastx)＠lca-205[8]> Please help. Anish _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

xemacs glyph clipping effect 17 years, 9 months

Klaus Reim

Dear Bug Team! this defect shows with any xemacs version I tried from 21.4 to 21.5.27. It is easily reproduced by evaluating the following lisp code. (attached you find a screen shot of a xemacs session showing the buffer produced by this code, both correctly and incorrectly drawn): --- start of sample --- (let* ((pattern "0123456789ABCDEF") (max (length pattern)) (buffer (get-buffer-create "*glyph-clipping-bug*")) i) (switch-to-buffer buffer) (erase-buffer) (setq i 0) ;; 4 is sufficient to see the effect. ;; 50 shows the same in slow motion, and you may scroll ;; several times to see variations of the theme (while (< i 50) (insert "Scroll down\nwith mouse wheel\nand watch\nclipping effect.\n") (setq i (1+ i))) ;; create test glyphs (goto-char (point-min)) (while (not (eobp)) (setq i (1+ (% i max))) (let ((extent (make-extent (point) (point-at-eol)))) (set-extent-property extent 'end-glyph (make-glyph (vector 'layout :orientation 'horizontal :vertically-justify 'top :horizontally-justify 'left :pixel-height 16 :items (list (vector 'button :descriptor (substring pattern 0 i) :callback '(message "hello world") :pixel-height 16 :face 'bold) (vector 'button :descriptor (substring pattern 0 i) :callback '(message "hello world") :pixel-height 16 :face 'bold) (vector 'button :descriptor (substring pattern 0 i) :callback '(message "hello world") :pixel-height 16 :face 'bold))))) (set-extent-property extent 'end-glyph-layout 'inside-margin) (forward-line))) (goto-char (point-min))) -- end of sample --- The example is overdoing things to make the effect more dramatic. Anyway, just eval the code to get a buffer with glyphs running down the right window margin. As soon as you scroll downwards with the mouse wheel (i.e. 5 lines of text in one go) you will see for yourself ... Besides the clipping defect, the example also makes a rather bad performance of the redisplay of glyphs evident. There is a noticeable flickering of the button windows until the redisplay comes to a rest after each scroll, while from the X11-point of view basically only a movement of the X-windows without any need for a redisplay or geometry changes seems necessary. Hope you can do something about the clipping at least. Many thanks for your efforts. Cheers, Klaus _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

2 participants
1 comments

Re: [Failure] The Package Smoketest 17 years, 9 months

Norbert Koch

* The XEmacs Package Smoketest <matsl(a)xemacs.org>: Robert, > These are the results from the XEmacs Package Smoketest: > > 21.5-mule -- errors > 21.4-mule -- errors > 21.4-nomule -- errors BBDB can't be built at the moment. bbdb-rmail requires rmailsum which we don't provide. Could you please fix this error? Compiling /home/nk/cvs/xprm/xemacs-packages/bbdb/lisp/bbdb-rmail.el... While compiling toplevel forms in file /home/nk/cvs/xprm/xemacs-packages/bbdb/lisp/bbdb-rmail.el: !! error (("Required feature rmailsum was not provided")) backtrace(nil t) # bind (error-info) byte-compile-report-error((error "Required feature rmailsum was not provided")) # bind (error-info) #<compiled-function (error-info) "...(4)" [error-info byte-compile-report-error] 2>((error "Required feature rmailsum was not provided")) # (unwind-protect ...) si:require(rmailsum nil) # bind (noerror filename feature) require(rmailsum) eval((require (quote rmailsum))) # bind (form) byte-compile-file-form-eval-boundary((require (quote rmailsum))) # bind (byte-compile-current-form handler form) byte-compile-file-form((require (quote rmailsum))) # (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*"> "/home/nk/cvs/xprm/xemacs-packages/bbdb/lisp/bbdb-rmail.el") # bind (byte-compile-current-file target-file input-buffer output-buffer byte-compile-dest-file load filename) byte-compile-file("lisp/bbdb-rmail.el") byte-code("..." [file byte-compile-file t] 2) # (condition-case ... . ((error (byte-code "ÂÃ!��!��Ä!��Æ!«�� Ç\"�� ＠ÈN®�＠!��Ê A\"��Ë!�� ... 3)))) # bind (file) batch-byte-compile-1("lisp/bbdb-rmail.el") # bind (error file-to-process) batch-byte-compile-one-file() # bind (error) batch-byte-compile() # bind (arg) command-line-do-funcall("-f") # bind (dir file-count line end-of-options file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " Â� ... 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) >>Error occurred processing lisp/bbdb-rmail.el: Required feature rmailsum was not provided Thanks, norbert. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

XEmacs Packages have been pre-released (2007-02-25-22) 17 years, 9 months

Norbert Koch

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey there everyone. I have just added the following packages to the 'Pre-Releases' directory: New Packages in Pre-Release: =========================== haskell-mode-1.11-pkg.tar.gz upstream version: 2.1 latin-unity-1.20-pkg.tar.gz upstream version: 1.20 Previously Announced Packages Still in Pre-Release: ================================================== auctex-1.47-pkg.tar.gz upstream version: 11.55 bbdb-1.31-pkg.tar.gz upstream version: 2.35 calendar-1.31-pkg.tar.gz upstream version: none docbookide-0.08-pkg.tar.gz upstream version: 0.1 ediff-1.68-pkg.tar.gz upstream version: 2.75 edit-utils-2.37-pkg.tar.gz upstream version: none mail-lib-1.79-pkg.tar.gz upstream version: none misc-games-1.19-pkg.tar.gz upstream version: none net-utils-1.51-pkg.tar.gz upstream version: N/A prog-modes-2.10-pkg.tar.gz upstream version: none sh-script-1.22-pkg.tar.gz upstream version: 2.0f tramp-1.35-pkg.tar.gz upstream version: 2.0.55 viper-1.55-pkg.tar.gz upstream version: 3.09 Detailed Changes: ================ - ------- ChangeLog Entries from mule-packages/latin-unity/ChangeLog ------- 2007-02-25 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.20 released. 2007-02-16 Stephen J. Turnbull <stephen(a)xemacs.org> * latin-unity.el (latin-unity-representations-present-region): Assume C1 characters map to themselves, as is true for all ISO-8859-X coding systems. Should fix the bug reported by Joachim Schrod and Fabrice Popineau. See <ire6dxp3.fsf(a)esemetz.metz.supelec.fr>. 2007-02-16 Stephen J. Turnbull <stephen(a)xemacs.org> * latin-unity.el: Documentation clarification. Installing These: ================ Manually: - -------- 1) Download the packages that you want to install from: /ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/ 2) Unpack them to: [1] /usr/local/lib/xemacs/xemacs-packages/ 3) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.[245].x): - ---------------------------------------------- 1) Tools -> Packages -> Add Download Site -> Pre-Releases 2) Tools -> Packages -> List and Install 3) Select the packages you wish to install (there are brief instructions at the bottom of the packages buffer). 4) Packages -> Install/Remove Selected 5) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.1.14): - ------------------------------------------- 1) Options -> Manage Packages -> Add Download Site -> Pre-Releases 2) Options -> Manage Packages -> List and Install 3 - 5) As per XEmacs 21.[245].x. norbert - XEmacs Package Release Manager. Footnotes: [1] Note: Mule packages should be installed into: /usr/local/lib/xemacs/mule-packages/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFF4f/vgu3ywdHdhM0RAnHfAJ9g43daYb6rVIyW3jiqUFD0O5/QLwCfZoxQ E3swGe28aB/P+4WwVJoeud8= =BQO0 -----END PGP SIGNATURE----- _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Same xemacs file for different versions 17 years, 9 months

Asfand Yar Qazi

Hi, I need to use xemacs 21.5 and 21.4 (beta and stable) depending on where I'm working. I keep a darcs repository (darcs is IMHO the best version control tool out there) of my .xemacs directory. I need to know if it's possible to do certain customizations differently for different versions of xemacs - is there a way of specifying a different custom.el file for different versions to use programatically via the init.el file, so that customize mode from different versions don't clash, for example? As a last resort, there has to be a variable or constant I can check that'll give me the current version of xemacs I'm using so I can base customizations on that. I realise I can just use different branches for different versions, and then synchronise shared patches between them (darcs makes that easy) but I'd prefer a more convenient way of doing it. Thanks _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

3 participants
3 comments

What the heck does this backtrace mean? 17 years, 9 months

Asfand Yar Qazi

Hi, I'm the emacs-lisp n00b who's audaciously decided to take over maintenance of ruby-modes. I'm having a great deal of difficulty figuring out what the dickens the backtrace means. I can't even see where it's telling me the line number or method name it failed on. Sorry if it's obvious, but although I'm an experienced programmer, lisp is completely new to me. /usr/bin/xemacs -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error t load-always-display-messages t load-ignore-out-of-date-elc-files t load-show-full-path-in-messages t)' -eval '(setq load-path (list lisp-directory))' -l /home/ayqazi/src/packages/xemacs/cvs/packages/package-compile.el -- xemacs-base debug -- -f batch-byte-compile ruby-electric.el Loading /usr/lib/xemacs-21.4.20/lisp/auto-autoloads... Loading /home/ayqazi/src/packages/xemacs/cvs/packages/xemacs-packages/debug/auto-autoloads... Loading /home/ayqazi/src/packages/xemacs/cvs/packages/xemacs-packages/xemacs-base/auto-autoloads... Compiling /home/ayqazi/src/packages/xemacs/cvs/packages/xemacs-packages/ruby-modes/ruby-electric.el... While compiling ruby-electric-mode in file /home/ayqazi/src/packages/xemacs/cvs/packages/xemacs-packages/ruby-modes/ruby-electric.el: ** reference to free variable ruby-electric-mode-hook ** reference to free variable ruby-electric-mode-on-hook ** reference to free variable ruby-electric-mode-off-hook While compiling toplevel forms: !! End of file or stream ((#<buffer " *Compiler Input*">)) backtrace(nil t) # bind (error-info) byte-compile-report-error((end-of-file #<buffer " *Compiler Input*">)) # bind (error-info) #<compiled-function (error-info) "...(4)" [error-info byte-compile-report-error] 2>((end-of-file #<buffer " *Compiler Input*">)) read(#<buffer " *Compiler Input*">) # (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*"> "/home/ayqazi/src/packages/xemacs/cvs/packages/xemacs-packages/ruby-modes/ruby-electric.el") # bind (byte-compile-current-file target-file input-buffer output-buffer byte-compile-dest-file load filename) byte-compile-file("ruby-electric.el") byte-code("..." [file byte-compile-file t] 2) # (condition-case ... . ((error (byte-code "ÂÃ!ˆÂ!ˆÂÄ!ˆÅÆ!«‡Æ Ç\"ˆª'Â ＠ÈN(r)‚ ＠!ˆÉÊ A\"ˆÂË!ˆÇ‡" ... 3)))) # bind (file) batch-byte-compile-1("ruby-electric.el") # bind (error file-to-process) batch-byte-compile-one-file() # bind (error) batch-byte-compile() # bind (arg) command-line-do-funcall("-f") # bind (dir file-count line end-of-options file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " Â‡" ... 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) >>Error occurred processing ruby-electric.el: End of file or stream: #<buffer " *Compiler Input*"> Done make: *** [ruby-electric.elc] Error 1 I've attached the ruby-electric.el file that this occurs on. Thanks _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

3 participants
5 comments

xemacs crash 17 years, 9 months

Ada Elizabeth Rubin

Hi, Xemacs craches on me evertime I choose Options->Syntaz Highlighting->In this buffer. I'm running Mac OS X 10.3.9 The xemacs configuration is uname -a: Darwin dirac.cgtp.duke.edu 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc ./configure '--prefix=/sw' '--with-dialogs=athena' '--with-widgets=athena' '--with-sound=none' '--with-database=gdbm' '--without-ldap' '--without-postgresql' '--with-athena=3d' XEmacs 21.4.15 "Security Through Obscurity" configured for `powerpc-apple-darwin7.9.0'. Compilation / Installation: Source code location: /Volumes/Backup/sw-build/xemacs-21.4.15-1/xemacs-21.4.15 Installation prefix: /sw Operating system description file: `s/darwin.h' Machine description file: `m/powerpc.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -fno-strict-aliasing -Wshadow -Wpointer-arith Compiler version: gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1640) Compiler specs file: /usr/libexec/gcc/darwin/ppc/3.3/specs Relocating allocator for buffers: no GNU version of malloc: no - The GNU allocators don't work with this system configuration. libc: system-provided libc on powerpc-apple-darwin7.9.0 Window System: Compiling in support for the X window system: - X Windows headers location: /usr/X11R6/include - X Windows libraries location: /usr/X11R6/lib - Handling WM_COMMAND properly. Compiling in support for the Athena widget set: - Athena headers location: X11/Xaw3d - Athena library to link: Xaw3d Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Using Athena native widgets. TTY: Compiling in support for ncurses. 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. Sound: Databases: Compiling in support for GNU DBM. Internationalization: Mail: Compiling in support for "dot-locking" mail spool file locking method. Other Features: Inhibiting IPv6 canonicalization at startup. Compiling in support for dynamic shared object modules. Using the new portable dumper. ------------------------------------------------------------------- No core file was dumped, but here's the back trace: Fatal error (10). Lisp backtrace follows: dispatch-non-command-events() # (condition-case ... . ((nil))) progress-feedback-dispatch-non-command-events() # bind (ext gutter-string val zmacs-region-stays inhibit-read-only frame value message) raw-append-progress-feedback("Fontifying .cshrc... (syntactically)" 5 #<x-frame "emacs" 0x682>) # bind (tmsg top frame value message label) append-progress-feedback(font-lock "Fontifying .cshrc... (syntactically)" 5 nil) # bind (frame value message label) display-progress-feedback(font-lock "Fontifying .cshrc... (syntactically)" 5) # bind (str) # (unwind-protect ...) # bind (args value fmt label) progress-feedback-with-label(font-lock "Fontifying %s... (syntactically)" 5 ".cshrc") # bind (loudly end start) font-lock-fontify-syntactically-region(1 661 nil) # (unwind-protect ...) # bind (modified buffer-undo-list inhibit-read-only old-syntax-table buffer-file-name buffer-file-truename loudly end beg) font-lock-default-fontify-region(1 661 nil) # bind (loudly end beg) font-lock-fontify-region(1 661) # (unwind-protect ...) byte-code("..." [font-lock-fontify-region] 3) # (condition-case ... . ((t (byte-code "???" ... 2)))) # bind (was-on font-lock-verbose font-lock-message-threshold aborted) # (unwind-protect ...) font-lock-default-fontify-buffer() # bind (font-lock-verbose) font-lock-fontify-buffer() # bind (on-p maximum-size arg) font-lock-mode() (progn (font-lock-mode) (customize-set-variable (quote font-lock-mode) font-lock-mode)) eval((progn (font-lock-mode) (customize-set-variable (quote font-lock-mode) font-lock-mode))) # (condition-case ... . error) # (catch top-level ...) Bus error _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

2 participants
1 comments

Recent bbdb ci breaks smoketest 17 years, 9 months

The XEmacs Package Smoketest

Hi, The recent update to bbdb breaks the smoketest. rmailsum isn't provided by the rmail package. README in rmail says it isn't supported so I guess that explains why it might be a bit behind. Simple patch below to illustrate what fixes the build. Index: lisp/bbdb-rmail.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/bbdb/lisp/bbdb-rmail.el,v retrieving revision 1.7 diff -u -r1.7 bbdb-rmail.el --- lisp/bbdb-rmail.el 23 Feb 2007 20:24:08 -0000 1.7 +++ lisp/bbdb-rmail.el 23 Feb 2007 22:45:44 -0000 ＠＠ -24,7 +24,7 ＠＠ (require 'bbdb) (require 'bbdb-com) (require 'rmail) -(require 'rmailsum) +;; (require 'rmailsum) (require 'mailheader) Yours -- %% Mats _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

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 February 2007