May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [PATCH] Tooolbar in buffer change fix 26 years, 6 months

Paul Bibilo

Kirill M. Katsnelson writes: > | > | this does fix the problem i was seeing. > | > | Thanks Kirill! > |- > > Huh, you are rewarding a vainglorious person: I introduce a bug, then fix it, > and then people say me thanks... Fixed for me too in "Saanen-pre2". > For this toolbar bug I deserve spanking, > not thanks :) > THWACKK!! -- Paul

1 participants
0 comments

Re: font-lock and shell scripts 26 years, 6 months

Adrian Aichner

>>>>> "Andy" == Andy Piper <andyp(a)parallax.co.uk> writes: Andy> I get fon't lock errors when editing shell scripts - does anyone else see Andy> this? Andy> andy Hello Andy, I have this in my site-start.el which might be worth trying: (setq interpreter-mode-alist (cons '("^#!.*/csh\\b" . csh-sh-mode) interpreter-mode-alist)) (setq interpreter-mode-alist (cons '("^#!.*/ksh\\b" . ksh-sh-mode) interpreter-mode-alist)) (setq interpreter-mode-alist (cons '("^#!.*/sh\\b" . sh-sh-mode) interpreter-mode-alist)) (setq auto-mode-alist (append '(("\\.C$" . c++-mode) ("\\.cc$" . c++-mode) ("\\.hh$" . c++-mode) ("\\.t$" . c++-mode) ("\\.c$" . c-mode) ("\\.h$" . c++-mode) ("\\.s$" . asm-mode) ("\\.n?awk$" . awk-mode) ;;; It's not the extension, it's the magic number that counts! ;;; Ideally they agree. ("\\.csh$" . csh-sh-mode) ("\\.ksh$" . ksh-sh-mode) ("\\.sh$" . sh-sh-mode) ; <lines deleted by Adrian> ) auto-mode-alist)) ; <lines deleted by Adrian> (defun csh-sh-mode () (add-hook 'sh-mode-hook '(lambda () (sh-set-shell "/bin/csh"))) (sh-mode)) (defun ksh-sh-mode () (add-hook 'sh-mode-hook '(lambda () (sh-set-shell "/bin/ksh"))) (sh-mode)) (defun sh-sh-mode () (add-hook 'sh-mode-hook '(lambda () (sh-set-shell "/bin/sh"))) (sh-mode)) (autoload 'sh-mode "sh-script" "Major mode for editing shell scripts.") ;; Begin of fixes for sh-script by Martin Buchholz (require 'sh-script) (setq sh-font-lock-keywords-only nil) (defun sh-font-lock-keywords (&optional keywords) "Function to get simple fontification based on `sh-font-lock-keywords'. This adds rules for comments and assignments." (sh-feature sh-font-lock-keywords (lambda (list) `((,(sh-feature sh-assignment-regexp) 1 font-lock-variable-name-face) ,＠keywords ,＠list)))) (add-hook 'sh-mode-hook 'my-sh-mode-syntax-table) (defun my-sh-mode-syntax-table () (set-syntax-table (make-syntax-table (standard-syntax-table))) (modify-syntax-entry ?\# "<") (modify-syntax-entry ?\n ">") (modify-syntax-entry ?\" "\"") (modify-syntax-entry ?\' "\"") (modify-syntax-entry ?\` "$") (modify-syntax-entry ?_ "_") (modify-syntax-entry ?$ "_")) ;; End of fixes for sh-script by Martin Buchholz ;; The following hook is for `shell' and `shell-mode' defined in ;; `comint/shell.el' implementing a mode for interactive shells. ;; (add-hook 'shell-mode-hook 'install-shell-fonts) ;; This just doesn't work right: Has no notion of shell-input[-face]. ;; Cannot co-exist with above shell-mode-hook 'install-shell-fonts. (add-hook 'shell-mode-hook 'turn-on-font-lock) (setq shell-prompt-pattern (purecopy "^[^#$%>)\n]*[#$%>)] $")) Good Luck, Adrian -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Straße 2 Fax +49/89/41861-217 D-81673 MÜNCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Re: Startup speed: Still too many stats? 26 years, 6 months

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Now that we are closed to code freeze, I've looked at the startup Hrvoje> speed again, and here is what I got: Hrvoje> $ truss -t stat -o out xemacs -q -nw -f kill-emacs Hrvoje> I tried this with XEmacs 20.3 (the default configuration), and with my Hrvoje> 21.0 installation containing a moderate number of packages (probably Hrvoje> less than there were in 20.3). Hrvoje> Basically, 20.3 performs 96 stats, while 21.0 performs 651 stats. The Hrvoje> ones in 21.0 are mostly spent to stat the `.el' and `.elc' files. Hrvoje> Michael, what was your opinion about the optimization we discussed, Hrvoje> which would forbid directories ending with `.el' or `.elc'? I think Hrvoje> it would be worth implementing it, especially for non-Unix systems, Hrvoje> where a stat is extremely costly. I finally understand what's causing the difference between 21.0 and previous versions: The organization of the Core Lisp directory has changed. Previously, it contained *only* subdirectories. Now, it contains lots of files and only one subdirectory---term. So all this stat'ing is just for term's benefit. Options: 1. I hack as Hrvoje suggests. 2. We move the stuff from term one level up and change `paths-load-path-depth' to 0. 3. We move the stuff in Core Lisp one level down (to "prim" or something) and presto. Of course, *I* would like 3. Steve? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

font-lock and shell scripts 26 years, 6 months

Andy Piper

I get fon't lock errors when editing shell scripts - does anyone else see this? andy

1 participants
0 comments

Re: [BUG] Null EMACSPACKAGEPATH causes an error 26 years, 6 months

Michael Sperber

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: Martin> $ env EMACSPACKAGEPATH= ./xemacs -no-site-file -no-init-file -f kill-emacs Martin> ^GWrong type argument: stringp, nil Then I'll fix it. Martin> The environment variable EMACSPACKAGEPATH doesn't seem to be Martin> documented. I've been holding off on the documentation until the design is finished. Due RSN. Martin> There doesn't seem to be an equivalent command-line flag to Martin> set it, either. Why should there be? (Actually, there was a long discussion about this question back then, but we rejected the idea.) -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

RE: [Success] 21.0 "Russian White" XEmacs Lucid (beta39) on i386- pc-c ygwin32 26 years, 6 months

Michael Hill

I just realized that NT didn't crash while I ran 'make' this time (it's been at least a couple of betas since I could say that). Mike

2 participants
1 comments

Re: XEmacs 20.4 find-func.el: find-function-noselect and newline 26 years, 6 months

Jens-Ulrik Petersen

>>>>> "ME" == Michael Ernst <mernst(a)cs.washington.edu> writes: ME> Because \\s- doesn't match newline, `find-function-noselect' ME> insists that there is a space after the function name. As a ME> result, it fails to find function whose arguments appear on a ME> separate line, as for `vm-mail-internal' in vm-reply.el: ME> (defun vm-mail-internal ME> (&optional buffer-name to subject in-reply-to cc ME> references newsgroups) ME> This patch fixes the problem by permitting either space or ME> end-of-line to appear immediately after the function name. Thanks but this has already been fixed in the current version in the XEmacs-21-beta packages. "find-func" used to be a core library, and unfortunately the current version doesn't work with older XEmacsen as far as I know, so since you're using 20.4 this doesn't help you much. Ok, I will try to put some back-compatibility back into "find-func" soonish. Thanks, -- Jens-Ulrik Holger Petersen <http://www.kurims.kyoto-u.ac.jp/~petersen/> Research Institute for Mathematical Sciences, Kyoto University

1 participants
0 comments

[Success] b40-pre2 on Intel/Linux 26 years, 6 months

Kazuyoshi Furutaka

[i686-GNU-linux] Source : patched up from 21.0 beta39 Patch : patch 2.4 Make : GNU Make version 3.76.1 CC : pgcc-2.90.27 980315 (egcs-1.0.2 release) OS : Linux 2.0.34pre13 (RedHat 5.0) X : X11R6.3 (Accelerated-X ver.4.1 w/ XFree86 3.3.1) gdb : GDB 4.16 From: SL Baur <steve(a)xemacs.org> Subject: Re: [Success] b40-pre1 on Intel/Linux Date: 11 May 1998 20:21:32 -0700 > Kazuyoshi Furutaka <furutaka(a)tokai.pnc.go.jp> writes: > > > (I can't invoke Mew-1.93b31 w/ xemacs-b40-pre1. > > Xemacs complains 'Wrong type argument: sequencep, 40' when invoking mew.) > > Please (setq debug-on-error t) and get a Lisp backtrace. Mew is > trying to concat an integer pretending it is a character and that > hasn't been a correct thing to do for awhile. It happens at a line I've made a modification, and when I replaced back to the original code it works... Strange thing is that the modified code worked w/ XEmacsen before b40-pre1. -- Kazuyoshi Furutaka furutaka(a)tokai.pnc.go.jp furutaka(a)jb3.so-net.ne.jp

1 participants
1 comments

Compilation woes for DnD 26 years, 6 months

Martin Buchholz

As a data point, here are the changes I had to make to get C++ compilability. (Using incompatible pointers in the source code is not acceptable; if introduced, I will eventually fix them when I C++-ize the source code.) This is NOT a recommended patch. This is merely to suggest to Oliver what kinds of changes I had to make. They must be resolved eventually. Oliver, you may choose to keep the casts I made, but think about whether making casts at all casts doubt on some of the code, esp. regarding mule-ized-ness. Happy hurling! --- src/event-Xt.c.old +++ src/event-Xt.c ＠＠ -1166,7 +1166,7 ＠＠ { len = strlen ((char*)data); hurl = dnd_url_hexify_string ((char *)data, "file:"); - l_item = make_string (hurl, strlen (hurl)); + l_item = make_string ((Bufbyte *) hurl, strlen (hurl)); l_dndlist = Fcons (l_item, l_dndlist); data += len + 1; xfree (hurl); ＠＠ -1176,8 +1176,8 ＠＠ break; case DndText: l_type = Qdragdrop_MIME; - l_dndlist = list1 ( list3 ( make_string ("text/plain", 10), - make_string ("8bit", 4), + l_dndlist = list1 ( list3 ( make_string ((Bufbyte *) "text/plain", 10), + make_string ((Bufbyte *) "8bit", 4), make_ext_string (data, strlen((char *)data), FORMAT_CTEXT) ) ); ＠＠ -1199,9 +1199,9 ＠＠ case DndLink: case DndExe: { - char *hurl = dnd_url_hexify_string (data, "file:"); + char *hurl = dnd_url_hexify_string ((char *) data, "file:"); - l_dndlist = list1 ( make_string (hurl, strlen (hurl)) ); + l_dndlist = list1 (make_string ((Bufbyte *) hurl, strlen (hurl)) ); l_type = Qdragdrop_URL; xfree (hurl); ＠＠ -1210,15 +1210,15 ＠＠ case DndURL: /* as it is a real URL it should already be escaped and escaping again will break them (cause % is unsave) */ - l_dndlist = list1 ( make_ext_string ((char *)data, + l_dndlist = list1 ( make_ext_string ((Extbyte *)data, strlen ((char *)data), FORMAT_FILENAME) ); l_type = Qdragdrop_URL; break; default: /* Unknown, RawData and any other type */ - l_dndlist = list1 ( list3 ( make_string ("application/octet-stream", 24), - make_string ("8bit", 4), - make_ext_string ((char *)data, size, + l_dndlist = list1 ( list3 ( make_string ((Bufbyte *) "application/octet-stream", 24), + make_string ((Bufbyte *) "8bit", 4), + make_ext_string ((Extbyte *)data, size, FORMAT_BINARY) ) ); l_type = Qdragdrop_MIME; break; --- src/frame-x.c.old +++ src/frame-x.c ＠＠ -1125,7 +1125,7 ＠＠ filePath = transferInfo->dropData->data.files[ii]; hurl = dnd_url_hexify_string ((char *)filePath, "file:"); /* ### Mule-izing required */ - l_data = Fcons ( make_string (hurl, strlen (hurl)), l_data ); + l_data = Fcons (make_string ((Bufbyte *) hurl, strlen (hurl)), l_data ); xfree (hurl); } } ＠＠ -1144,9 +1144,9 ＠＠ path = (filePath == NULL) ? Qnil : make_string ((Bufbyte *)filePath, strlen (filePath)); */ /* what, if the data is no text, and how can I tell it? */ - l_data = Fcons ( list3 ( make_string ("text/plain", 10), - make_string ("8bit", 4), - make_ext_string (transferInfo->dropData->data.buffers[ii].bp, + l_data = Fcons ( list3 ( make_string ((Bufbyte *) "text/plain", 10), + make_string ((Bufbyte *) "8bit", 4), + make_ext_string ((Extbyte *) transferInfo->dropData->data.buffers[ii].bp, transferInfo->dropData->data.buffers[ii].size, FORMAT_CTEXT) ), l_data );

1 participants
0 comments

Expensiveness of searching load-path 26 years, 6 months

Martin Buchholz

My XEmacs packages are installed on a Linux machine. Those packages are used from both Linux and from Solaris. The Linux NFS server is notoriously slow. Each find-file of a C source file on Solaris was annoyingly slow. I tracked it down to this ancient code in one of my cc-mode hooks: (ignore-errors (require 'cc-lobotomy) ...) There is no such .el file on my load-path, so a full load-path search was performed for every find-file. Anyways, the search of my load-path executes 158 stats, and takes anywhere from 3-12 seconds, averaging around 5 seconds. This is on fast machines with an unloaded network. Many of us on xemacs-beta are using XEmacs with all files on local disk. In the real world, XEmacs is much more likely to be housed on NFS-mounted filesystems on an overloaded network. We should work under the assumption that the price of the current load-path layout is TEN SECONDS in startup time. This is too expensive. Martin

3 participants
3 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 May 1998