September 2002 - XEmacs-Beta - XEmacs Mailing List Archives

21.4.6 hangs on X11 clipboard on HP-UX 10.20 7 years, 2 months

Gary Beckmann

Periodically, xemacs will "hang" (stop taking input, not refresh screen). When killed, the back traces look like: Lisp backtrace follows: own-selection-internal(CLIPBOARD "\n" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("\n" CLIPBOARD) # bind (push string) own-clipboard("\n" t) # bind (replace string) kill-new("\n") # bind (undo-high-threshold tail verbose end start) kill-region(558 559) # bind (entire-line arg) kill-line-1(nil nil) # bind (arg) kill-line(nil) # bind (command-debug-status) call-interactively(kill-line) # (condition-case ... . error) # (catch top-level ...) Lisp backtrace follows: own-selection-internal(CLIPBOARD "xemacs-beta-request(a)xemacs.org" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("xemacs-beta-request(a)xemacs.org" CLIPBOARD) # bind (push string) own-clipboard("xemacs-beta-request(a)xemacs.org" t) # bind (replace string) kill-new("xemacs-beta-request(a)xemacs.org") # bind (end start) copy-region-as-kill(403374 403404) # bind (end start) kill-ring-save(403374 403404) # bind (command-debug-status) call-interactively(kill-ring-save) # (condition-case ... . error) # (catch top-level ...) Lisp backtrace follows: own-selection-internal(CLIPBOARD "xemacs-beta-request(a)xemacs.org" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("xemacs-beta-request(a)xemacs.org" CLIPBOARD) # bind (push string) own-clipboard("xemacs-beta-request(a)xemacs.org" t) # bind (replace string) kill-new("xemacs-beta-request(a)xemacs.org") # bind (end start) copy-region-as-kill(403374 403404) # bind (end start) kill-ring-save(403374 403404) # bind (command-debug-status) call-interactively(kill-ring-save) # (condition-case ... . error) # (catch top-level ...) Lisp backtrace follows: own-selection-internal(CLIPBOARD "src/" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("src/" CLIPBOARD) # bind (push string) own-clipboard("src/" t) # bind (replace string) kill-new("src/") # bind (undo-high-threshold tail verbose end start) kill-region(27 23) # bind (count) kill-word(-1) # bind (count) backward-kill-word(1) # bi: gary＠rules[19] ; nd (command-debug-status) call-interactively(backward-kill-word) # (condition-case ... . error) # (unwind-protect ...) read-minibuffer-internal("Find file: ") byte-code("..." [standard-output standard-input prompt recursion-depth minibuffer-depth t read-minibuffer-internal] 2) # (catch exit ...) # bind (mouse-grabbed-buffer current-prefix-arg minibuffer-history-variable minibuffer-history-position minibuffer-scroll-window) # (unwind-protect ...) # bind (minibuffer-default _history_ oconfig mconfig frame buffer window oframe owindow dir default abbrev-table history readp keymap initial-contents prompt) read-from-minibuffer("Find file: " "~/cdev/RSAcore/dev/se/src/" #<keymap read-file-name-map size 2 0xd3c> nil file-name-history nil "~/cdev/RSAcore/dev/se/src/sePTVMgr.cxx") # bind (minibuffer-completion-table minibuffer-completion-predicate minibuffer-completion-confirm last-exact-completion insert completer initial-contents must-match default dir prompt history) read-file-name-2(file-name-history "Find file: " nil "~/cdev/RSAcore/dev/se/src/sePTVMgr.cxx" nil nil read-file-name-internal) # bind (completer initial-contents must-match default dir prompt history type) read-file-name-1(file file-name-history "Find file: " nil "~/cdev/RSAcore/dev/se/src/sePTVMgr.cxx" nil nil read-file-name-internal) # bind (history initial-contents must-match default dir prompt) read-file-name("Find file: " nil nil nil) call-interactively(find-file) # (condition-case ... . error) # (catch top-level ...) That's four of them. They all have in common the kill-new function. Has anyone else seen this? Any ideas what I can try? OS: HP-UX 10.20 compiled with HP's Ansi C compiler Motif 1.2 (from HP). gary

4 participants
3 comments

Why isn't packages/xemacs-packages/psgml/etc/cdtd in CVS? 7 years, 2 months

Stephen J. Turnbull

It seems that packages/xemacs-packages/psgml/etc/cdtd/.cvsignore _is_ in CVS, which causes cdtd to get created, but then after that I always get a move away xemacs-packages/psgml/etc/cdtd/.cvsignore; it is in the way message. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py

4 participants
5 comments

21.0 Showstoppers 7 years, 2 months

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, 3 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

Strange delays when running remotely 17 years, 11 months

David E Sigeti

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. Please describe as succinctly as possible: - What happened. - What you thought should have happened. - Precisely what you were doing at the time. Please also include any C or lisp back-traces that you may have. ================================================================ Dear Bug Team! When running Xemacs version 21 remotely (displaying on my local X server) I have found that any multicharacter kills (such as kill-line, kill-word, kill-ring-save, etc.) are extremely slow (maybe 15-30 seconds per kill). I only see this delay when I am running over a DSL connection where the ping times to the remote system are on the order of 100 milliseconds or more. When my local machine is on the same LAN as the remote machine (much shorter ping times), I do not notice any unusual delay in multicharacter kills. I also do not see this problem when running Xemacs version 20. My local X server when using the DSL connection is Exceed 3D running under Microsoft Windows 98SE. When using the LAN, my local X server is also Exceed 3D but running under Microsoft Windows 2000. Yours, David --- Dr. David E. Sigeti Phone: 505-667-9239 E-mail: sigeti(a)lanl.gov Surface mail: MS-F645, Los Alamos National Laboratory, Los Alamos, NM 87545 USA ================================================================ System Info to help track down your bug: --------------------------------------- uname -a: IRIX64 t01 6.5 04131233 IP27 ../../packages/xemacs-21.4.8/configure '--prefix=/users/sigeti/' '--exec-prefix=/users/sigeti/bin/mips-sgi-irix6.5/' '--pdump' XEmacs 21.4.8 "Honest Recruiter" configured for `mips-sgi-irix6.5'. Compilation / Installation: Source code location: /users/sigeti/packages/xemacs-21.4.8 Installation prefix: /users/sigeti/ Runtime library search path: /usr/lib32/mips3:/usr/lib32 Operating system description file: `s/irix6-0.h' Machine description file: `m/iris6d.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wshadow -Wpointer-arith Relocating allocator for buffers: yes GNU version of malloc: yes Window System: Compiling in support for the X window system: - X Windows headers location: - X Windows libraries location: - Handling WM_COMMAND properly. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Using Motif native widgets. TTY: Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. WARNING: ----------------------------------------------------------- WARNING: Compiling without PNG image support. Reason: PNG library version too old (pre 1.0.2)! 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) WARNING: ----------------------------------------------------------- Compiling in support for JPEG images. Compiling in support for TIFF images. Sound: Compiling in support for sound (native). Databases: Compiling in support for Berkeley database. Compiling in support for 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. Load-Path Lisp Shadows: ---------------------- nil Installed XEmacs Packages: ------------------------- ((xemacs-devel:version 1.44 :type single-file) (xemacs-base :version 1.63 :type regular) (w3 :version 1.23 :type regular) (vm :version 7.07 :type regular) (vc-cc :version 1.18 :type regular) (vc :version 1.33 :type regular) (tm :version 1.32 :type regular) (text-modes :version 1.46 :type single-file) (speedbar :version 1.23 :type regular) (sh-script :version 1.15 :type regular) (rmail :version 1.13 :type regular) (ps-print :version 1.04 :type regular) (prog-modes :version 1 .57 :type single-file) (pcl-cvs :version 1.63 :type regular) (net-utils :version 1.25 :type single-file) (mh-e :version 1.14 :type regular) (mailcrypt :version 2.11 :type regular) (mail-lib :version 1.46 :type regular) (ispell :version 1.24 :type regular) (ilisp :version 1.26 :type regular) (gnus :version 1.61 :type regular) (fsf-compat :version 1.11 :type single-file) (eterm :version 1.13 :type regular) (emerge :version 1.09 :type regular) (elib :version 1.1 :type single-file) (efs :version 1.29 :type regular) (edit-utils :version 1.88 :type single-file) (ediff :version 1.41 :type regular) (edebug :version 1.14 :type regular) (dired :version 1.12 :type regular) (cc-mode :version 1.28 :type regular) (apel :version 1.23 :type regular)) Features: -------- (mail-abbrevs xemacsbug shadow sendmail rfc822 dired-faces dired-xemacs dired font disp-table cus-face xemacs-devel-autoloads xemacs-base-autoloads w3-autoloads vm-autoloads vc-cc-autoloads vc-autoloads tm-autoloads text-modes-autoloads speedbar-autoloads sh-script-autoloads rmail-autoloads ps-print-autoloads prog-modes-autoloads pcl-cvs-autoloads net-utils-autoloads mh-e-autoloads mailcrypt-autoloads mail-lib-autoloads ispell-autoloads ilisp-autoloads gnus-autoloads fsf-compat-autoloads eterm-autoloads emerge-autoloads elib-autoloads efs-autoloads edit-utils-autoloads ediff-autoloads edebug-autoloads dired-autoloads cc-mode-autoloads apel-autoloads lisp-autoloads loadhist auto-show fontl-hooks x-iso8859-1 gutter-items menubar-items x-menubar mode-motion mouse itimer auto-save lisp-mode easymenu iso8859-1 page buff-menu lib-complete help-nomule cus-file derived frame text-props obsolete cus-start custom widget cl-extra mini-cl cl cl-19 packages backquote very-early-lisp lucid-scrollbars cut-buffer lucid-menubars motif-dialogs x c-balloon-help tty-frames tty toolbar native-sound scrollbar unix-processes multicast network-streams subprocesses modules menu-accelerator-support menubar berkeley-db dbm md5 xemacs gutter tiff gif jpeg xpm xbm lisp-float-type irix dialog devices window-system base64) Recent keystrokes: ----------------- C-x C-f RET M-x r e p SPC o SPC r SPC x SPC SPC RE T Recent messages (most recent first): ----------------------------------- Loading xemacsbug...done Loading xemacsbug... Making completion list... Making completion list... Reading directory /users/sigeti/...done Reading directory /users/sigeti/... Loading dired...done Loading dired... Loading font...done Loading font... Loading cus-face...done Loading cus-face...

13 participants
25 comments

Please test (and comment on) Euro support (ISO 8859/15) 21 years, 8 months

Stephen J. Turnbull

I've just added initial support for the Euro (and a half-dozen other characters) by adding the latin-iso8859-15 charset (ISO Latin-9) the iso-8859-15 coding system (ISO 8859/15 and ISO IRV 203) the latin-9 language environment to 21.5 CVS (check out the bleeding edge with update -A). Yes, I'm inclined to apply to 21.4, but I'd like it to be more complete and somewhat tested first. ;-) I need advice on (1) what, if anything, to do about the XK_EuroSign keysym for X (I know you can (global-set-key [EuroSign] (lambda () (interactive) (insert (make-char 'latin-iso8859-15 #xA4))) but does there need to be a default binding? Is that the right one? Should it be activated by the language environment? etc) (2) any other non-Quail input methods for the Euro and additional characters (3) I want to make Quail latin-9-prefix and -postfix methods compatible with the latin-1 methods. I need suggestions for keystroke bindings for the following characters: U+20AC euro sign U+0160 latin capital letter s with caron U+0161 latin small letter s with caron U+017D latin capital letter z with caron U+017E latin small letter z with caron U+0152 latin capital ligature oe U+0153 latin small ligature oe U+0178 latin capital letter y with diaeresis French and Finnish speakers, this one's for you! (4) plausible aliases for the language environment (5) did I get the ISO 2022 final byte correct? (ISO IRV 203 says it's ?b, ie, ASCII 0x62.) (6) What else did I miss? Please note that the Gnus in the XEmacs packages seems to be broken; it will not do QP-encoding of ISO 8859/15 (or ISO 8859/any, for any != 1) correctly. Not for me, anyway (it just doesn't know anything about XEmacs, period). I haven't tried VM yet. The following form may be of use: (insert (make-char 'latin-iso8859-15 #xA4)) That should give you a Euro sign (eg in *scratch*) out of the box in xemacs -vanilla. -- 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.

7 participants
7 comments

cvs mirroring 22 years, 1 month

Ilya N. Golubev

Hans-Guenter Weigand wrote in <http://list-archive.xemacs.org/xemacs-beta/199810/msg00634.html> <m0zUKrn-001lhlC(a)wiesbaden.netsurf.de> > If the cvs repository is distributed by ctm, people can use cvs locally > with all its features, without need for a leased line. This is optimal > for (us) poor modem users... Has ever downloading cvs repository contents (`,v' files) using cvsup or ctm or other been set up? It appears that that discussion ended up with nothing.

6 participants
10 comments

typo in TUTORIAL.fr 22 years, 2 months

juergen stuber

Dear Bug Team! The line M-x repls<Return>Remarquez<Return>Notez<Return>. in TUTORIAL.fr should read M-x repl<Return>s<Return>Remarquez<Return>Notez<Return>. Juergen ================================================================ System Info to help track down your bug: --------------------------------------- OS version: Microsoft Windows 2000 [Version 5.00.2195] OS: Windows_NT XEmacs 21.4.6 \"Common Lisp (Windows)\" configured for `i586-pc-win32'. Building XEmacs in \"f:\\xemacs\\xemacs-21.4-release\\nt\". Using compiler \"cl -nologo -W3 -O2 -G5 -ML\". Installing XEmacs in \"c:\\Program Files\\XEmacs\\XEmacs-21.4.6\". Package path is \"~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\xemacs-packages\".

2 participants
1 comments

A couple of problems with new module code. 22 years, 2 months

Steve Youngs

Hi Jerry! I just built XEmacs with your new module code (nice work, BTW) and noticed a couple of problems: - Autoloads are built for *everything* in ./modules unconditionally. If I don't have/build/install ldap, I don't want the ldap autoloads in ./modules/auto-autoloads.el. We should only build autoloads for those modules that we are actually going to build and install. - With '--error-checking=all' I got an undefined symbol error while trying to connect to a PostgreSQL database... "undefined symbol: error_check_pgconn" Can you take care of these, Jerry, or would you like me to? Probably be quicker if you do. :-) -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---|

4 participants
30 comments

custom.el shadow 22 years, 2 months

Neal D. Becker

Just installed xemacs-21.4.8. I see this: /usr/share/xemacs-21.4.8/lisp/custom hides /home/nbecker/.xemacs/custom Should I be worried?

7 participants
18 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 September 2002