December 2001 - XEmacs-Beta - XEmacs Mailing List Archives

[PATCH] generalizing redisplay_output_display_block() 23 years

William M. Perry

One of the things that confused me when doing the GTK work initially was that xxx_output_display_block was 99% the same on all the various backends. The only thing different were calls to output the horizontal lines, eol cursor, and blank areas. This patch fixes the problem for X11 & GTK by introducing a few new methods to the device/console structure: output_eol_cursor(struct window *w, struct display_line *dl, int xpos, face_index findex) output_blank(struct window *w, struct display_line *dl, struct rune *rb, int start_pixpos, int cursor_start, int cursor_width) output_horizontal_line(struct window *w, struct display_line *dl, struct rune *rb) The X and GTK builds both run and seem to display things quite nicely with this. Layouts, text, toolbars, gutters, etc. The mswindows stuff is partially done, but not in this patch. The cursor handling and output_string would need to be modified more than I am comfortable with at the moment. The TTY redisplay would need to change more than I am comfortable with as well. This falls back and uses the device-specific output_display_block() method if it is available. So this code uses the generic code for the X display, but tty specific routines on the TTY. Comments? Vetoes? Anybody willing to fix up the MSW and TTY backends to deal with this? This would allow the TTY code to spit out at least the text strings from layouts, etc, if it exposed output_string(). -bp -- Ceterum censeo vi esse delendam

3 participants
3 comments

Minor documentation/comment patch for 21.5 23 years

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

This has been a whoops *forever*. Not strictly a bug (unless somebody decides the underlying problem is a bug). I've always preferred the Athena-style scrollbar bindings for left/right mouse, but under XEmacs right-mouse would always lock the keyboard up (while left-mouse was OK, and in fact would UNlock the keyboard for me). The *underlying* problem is that the comment in lwlib/xlwscrollbar.c says "add these translations", but is missing one translation. There's *already* a <Btn1Up> translation that does Release() - so left-mouse works. As listed, Bnt3Down would do a PageUpOrLeft - but when you release the mouse button, Release() doesn't happen, causing a keyboard wedge. Possible bug: Should there be a <Btn3Up>: Release() in the default_translations table in xlwscrollbar.c (there's already Release() for Btn1Up and Btn2Up)? Patch for the comment attached. Feel free to reject if the consensus is that default_translations[] needs fixing instead... /Valdis Index: lwlib/xlwscrollbar.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lwlib/xlwscrollbar.c,v retrieving revision 1.14 diff -u -r1.14 xlwscrollbar.c --- lwlib/xlwscrollbar.c 2001/04/12 18:21:56 1.14 +++ lwlib/xlwscrollbar.c 2001/12/16 09:50:29 ＠＠ -30,7 +30,8 ＠＠ * * Emacs*XlwScrollBar.translations: #override \n\ * <Btn1Down>: PageDownOrRight() \n\ - * <Btn3Down>: PageUpOrLeft() + * <Btn3Down>: PageUpOrLeft() \n\ + * <Btn3Up>: Release() * */

2 participants
1 comments

Re: [QUERY] Re: [PATCH] packages: Thou shalt obey shell-file-name and shell-command-switch II 23 years

Stephen J. Turnbull

Deleting XEmacs patches from the discussion. >>>>> "SY" == Steve Youngs <youngs(a)xemacs.org> writes: SY> So I'll say it again. This works fine, but what happens if SY> the user has set 'shell-file-name' and/or SY> 'shell-command-switch' to something other than the default? That's the user's problem, of course. We should make sure that defaults for 'shell-file-name' and 'shell-command-switch' are sensible on each platform (ie, "/bin/sh" and "-c" resp on Unix). On my Linux box it's "/bin/bash" which I guess is harmless (although it encourages people to use bash-isms in generic code). The docstring should warn the user that use of non-default values can cause problems, as most XEmacs commands are going to expect POSIX behavior from the shell. We should cross reference those variables in the documentation. This is not yet done. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Don't ask how you can "do" free software business; ask what your business can "do for" free software.

2 participants
1 comments

xemacs-21.4.5 hangs on recompile 23 years

Rene Rebe

Hi all. I'd like ot report a annoying problem I had for some time now with the XEmacs. Very often when I do a recompile in XEmacs (via F6 wich is: "(global-set-key [f6] 'recompile)" on my machine) the XEmacs simply hangs, does nothing and no window gets ever refreshed on my X dispplay. Often means every 4th to 7th time. Aproximately 30 times this weekend ... I have the XEmacs-21.4.5, under GNU/Linux 2.4.16, Glib-2.1.3, XFree-4.1.0. Here is a backtrace of such a freezed XEmacs: (gdb) bt #0 0x40509b1e in __select () from /lib/libc.so.6 #1 0x4037d55c in __DTOR_END__ () from /usr/X11/lib/libX11.so.6 #2 0x402d30aa in _XRead () from /usr/X11/lib/libX11.so.6 #3 0x402d3ad5 in _XReply () from /usr/X11/lib/libX11.so.6 #4 0x402ca78d in XQueryPointer () from /usr/X11/lib/libX11.so.6 #5 0x081723fa in Fx_ungrab_keyboard () #6 0x08173e9e in emacs_Xt_event_handler () #7 0x4025cb80 in XtDispatchEventToWidget () from /usr/X11/lib/libXt.so.6 #8 0x4025d21c in DispatchEvent () from /usr/X11/lib/libXt.so.6 #9 0x4025d48c in _XtDefaultDispatcher () from /usr/X11/lib/libXt.so.6 #10 0x4025d7a9 in XtDispatchEvent () from /usr/X11/lib/libXt.so.6 #11 0x402687b3 in XtAppProcessEvent () from /usr/X11/lib/libXt.so.6 #12 0x08173670 in emacs_Xt_handle_focus_event () #13 0x080dbac7 in Finput_pending_p () #14 0x080b0486 in Ffuncall () #15 0x0808bed9 in funcall_compiled_function () #16 0x0808bbc9 in funcall_compiled_function () #17 0x080b0654 in Ffuncall () #18 0x080b15ff in run_hook_with_args_in_buffer () #19 0x080b52d1 in run_hook_with_args () #20 0x080b70fd in Frun_hook_with_args_until_failure () #21 0x080b1f32 in safe_run_hook_trapping_errors () #22 0x080db9e1 in Fnext_command_event () ---Type <return> to continue, or q <return> to quit--- #23 0x080d9add in Fset_recent_keys_ring_size () #24 0x080da154 in Fdispatch_event () #25 0x080940da in Fcommand_loop_1 () #26 0x0809433d in call_command_loop () #27 0x080b5f0f in condition_case_1 () #28 0x080944a7 in Freally_early_error_handler () #29 0x080b5ddc in internal_catch () #30 0x08093e1e in initial_command_loop () #31 0x080aa14d in xemacs_21_4_5_i686_pc_linux () #32 0x080abe25 in main () #33 0x40463c52 in __libc_start_main (main=0x80abd1c <main>, argc=2, argv=0xbffff8c4, init=0x807d81c <_init>, fini=0x81a9470 <_fini>, rtld_fini=0x4000c474 <_dl_fini>, stack_end=0xbffff8bc) at ../sysdeps/generic/libc-start.c:92 This are some lines of the info/config XEmacs produced during compilation: XEmacs 21.4.5 "Civil Service" configured for `i686-pc-linux'. Compilation / Installation: Source code location: /rock-linux/src/xemacs-21.4.5 Installation prefix: /usr Operating system description file: `s/linux.h' Machine description file: `m/intel386.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wshadow Relocating allocator for buffers: no GNU version of malloc: yes - Using Doug Lea's new malloc from the GNU C Library. Window System: Compiling in support for the X window system: - X Windows headers location: /usr/X11/include - X Windows libraries location: /usr/X11R6/lib - Handling WM_COMMAND properly. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Using Motif native widgets. TTY: Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). I hope this helps you to figure out where this problem might be;-)! Thanks and k33p h4ck1n6 René Rebe -- René Rebe (Registered Linux user: #248718 <http://counter.li.org>) eMail: rene.rebe(a)gmx.net rene(a)rocklinux.org Homepage: http://www.tfh-berlin.de/~s712059/index.html Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms.

2 participants
1 comments

abbrev case sensitive 23 years

Uwe Brauer

Hello Are there any plans for future xemacs releases to make abbrev case sensitive? I use flyspell a lot, which automatically adds corrected words to an abbrev list, but since abbrev is not case sensitive the result can sometimes be annoying. Regards Uwe Brauer

2 participants
1 comments

Re: display-time-mail question 23 years

greg＠visiontech-dml.com

nbecker(a)fred.net writes: > Can display-time-mail-file point to an imap or pop mailbox? If so, > what is the syntax? Gnu emacs time.el has display-time-mail-function variable and there are some add-ons that work with pop (maybe imap) mailboxes. Alas, xemacs doesn't have this feature. -- Greg

2 participants
1 comments

[ANNOUNCE] Updated packages in Pre-Release - Dec 19 23 years

Steve Youngs

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Heads Up: Peter B. & Norbert K. Let me know if this doesn't fix your problems with prog-modes. Thanks, guys. Hey there everyone. I have just added the following packages to the 'Pre-Releases' directory: New Packages in Pre-Release: =========================== prog-modes-1.46-pkg.tar.gz psgml-1.24-pkg.tar.gz Previously Announced Packages Still in Pre-Release: ================================================== mule-ucs-1.00-pkg.tar.gz (Mule) vc-1.30-pkg.tar.gz Detailed Changes: ================ prog-modes-1.46-pkg.tar.gz - -------------------------- 2001-12-19 Steve Youngs <youngs(a)xemacs.org> * Makefile (REQUIRES): Add dired for p4. * p4.el (p4-running-xemacs): Autoload 'timerp', 'cancel-timer' and 'dired-get-filename'. * php-mode.el (php-file-patterns): Add autoload cookie. psgml-1.24-pkg.tar.gz - --------------------- 2001-12-18 Steve Youngs <youngs(a)xemacs.org> * package-info.in: (provides): Update to include all provides. 2001-11-20 Dr. Volker Zell <Dr.Volker.Zell(a)oracle.com> * psgml-html.el (html-helper-expert-menu): Take into account if the value of `browse-url-browser-function' is not a function but a list of pairs. 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. Footnotes: [1] Note: Mule packages should be installed into: /usr/local/lib/xemacs/mule-packages/ - -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---| -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: The XEmacs Development Team. iD8DBQE8H6ZXjNKQaxDVycURAgvXAKCNCOSlZl8P+WB4KRz/TcN1+Tq00wCdEsCN DSEAeibRQdY98z+6yljlxiU= =HJmG -----END PGP SIGNATURE-----

2 participants
2 comments

Re: CPerl 4.32 23 years

Adrian Aichner

The following message is a courtesy copy of an article that has been posted to comp.emacs.xemacs as well. >>>>> "Scott" == Scott Grosch <Grosch> writes: cperl-invalid-face is the variable governing this. I can't see a clean way to turn this feature off. I shall note, however, that I find this a valuable feature. It shows trailing whitespace garbage in perl script which I wouldn't notice otherwise. I get rid of these by entering and exiting picture-mode. In keeping with the spirit of Emacs it should still be possible to turn this feature off for those who don't like it. Best regards, Adrian Scott> I'm using cperl-mode 4.32 within xemacs 21.1.12 I really Scott> dislike the _____ that are put at the start of lines which Scott> are just spaces. Those are clearly being put in by Scott> cperl-mode as those underscores aren't part of the saved Scott> file. How do I turn that off? -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

3 participants
2 comments

request for comments: loadhist.el (define-error 'cannot-unload-feature "...") 23 years

Sean Champ

I'm writing something to try and help us cut down on the system resources used by emacsen, calling it 'load-manager-unload-feature', intending to eventually make a nice gui for it (but, for now, it's basically just a different interactive interface on `unload-feature') It would make it a heck of a lot easier to do this, if we added something like this to loadhist.el, where `unload-feature' is defined: (define-error 'cannot-unload-feature "error to signal when a feature cannot be unloaded") .. and modify `unload-feature', to make it signal that error, when a feature cannot be unloaded because some loaded libraries are depending on it. but i didn't think that was the best name for the error. any suggestions? -- sean champ here's a snapshot of the load-manager code so far: ;; load-manager.el (defvar load-manager-feature-history nil "history used by `load-manager-unload-feature") ;; haven't integrated this error type yet, but here it is: (define-error 'cannot-unload-feature "error to signal when a feature cannot be unloaded") (defun load-manager-unload-feature (feature) "attempt to unload FEATURE If the feature is required by any other loaded code, a warning will be signaled [was implemented, but presently isn't]. also see: `unload-feature' " (interactive (list (intern-soft (completing-read "unload feature: " obarray #'(lambda (obj) (and (featurep obj) (feature-file obj))) t nil 'load-manager-feature-history)))) ;; i need to use a `condition-case' here, instead, ;; but this hopefully makes the point of what i'm trying to do: ;; i'm trying to change what happens when a feature cannot be unloaded. (catch 'unable-to-unload (if (feature-file feature) (condition-case err (unload-feature feature) ;; the error-handler makes up the most of this (error (let ((errmsg (car (cdr err)))) ; DEBUG: (print errmsg (current-buffer)) ;; check to make sure it's the error that we're looking for ... (if (and errmsg (string-match (format "^Loaded libraries (\$.*\$) depend on %s" feature) errmsg)) (let ((dependents (split-string ;; we get "\"foo"\" for each thing that we want from ;; the the string-match. this isn't the best way to ;; get rid of those quotes, but it works. (replace-in-string (match-string 1 errmsg) "\"" "") " ")) dependv) ;; hope that the library name of the dependent library is the same as ;; that of a feature provided it; if it is, ask user if that ;; dependent feature should be unloaded. ; DEBUG: (print dependents (current-buffer)) (while (progn (setq dependv (intern-soft (car dependents)) dependents (cdr dependents)) (featurep dependv)) (if (yes-or-no-p (format "feature %s depends on %s ; unload %1$s?" dependv feature)) (load-manager-unload-feature dependv) (throw 'unable-to-unload "dependents still loaded")))) ;; else, it was a different error, so tell user about it: (apply #'error err))))) ;; this happens when the (feature-file feature) => nil (throw 'unable-to-unload (format "load-file of feature %s is not known" feature))))) ;(print features (current-buffer)) ;; test-case: ; (require 'bookmark) ;; requires pp , also ; (call-interactively #'load-manager-unload-feature) ; ;; now, try to make it unload pp ;; ;; it should work, but it's some ugly code that gets it to do so. ;; and it doesn't tell the user, yet, when a feature cannot be unloaded. ;; load-manager.el ends here

2 participants
1 comments

howto? : loop-detection in 'require' calls 23 years

Sean Champ

i've started on something that shows each loaded feature, and what features are required by the library in which that feature is provided, and so on down the chain. The point is 1) to show what's going on with features, and 2) to make it easier to unload a given feature. but, i've ran into a problem with loop-detection. i'm able to filter it out, easily enough, when a feature's library seems to require the feature itself, but i found another loop that i don't know how to handle, namely: apel-ver requires product, which requires pym, which requires apel-ver looking at it, i wonder how the heck any of 'em gets loaded in the first place, and I don't C well enough to make sense of how 'require' works. 1) so, which of those three gets loaded first? and how does the reader know when to return from the loop? 2) do you have any suggestions, on how i should avoid an endless iteration in that loop of feature-file requirements? this is what i've been using: `loadmanager-show-feature-tree', defined below. ;; just doing this should show the loop: ; (require 'apel-ver) ; (loadmanager-walk-feature-tree '(apel-ver)) ;; whose dependencies will be printed, cyclically, to the current ;; buffer, until `max-lisp-eval-depth' is exceeded. (require 'cl) (defvar *loadmanager-indent-step* 0 "used internally, by `loadmanager-show-feature-tree'") (defun loadmanager-show-feature-tree (&optional other-window) (interactive "P") (funcall (if other-window #'switch-to-buffer-other-window #'switch-to-buffer) (get-buffer-create "*Feature-tree*")) (erase-buffer) (setq *loadmanager-indent-step* 0) (loadmanager-walk-feature-tree features)) (defun loadmanager-walk-feature-tree (feature-list) (dolist (feature (copy-sequence feature-list)) (let* ((featfile (feature-file feature))) (indent-to-column *loadmanager-indent-step*) (insert-face (symbol-name feature) 'font-lock-reference-face) (indent-to-column 30) (insert ": ") (insert-face featfile 'font-lock-string-face) (newline 2) (when featfile (incf *loadmanager-indent-step* 2) (loadmanager-walk-feature-tree (remq feature (file-requires featfile))) (decf *loadmanager-indent-step* 2)))))

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