December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Didier Verna

I vaguely remember Steve saying that the tag for 21.2 had changed, or something. Can somebody tell me what's the status of the following information (particularily which stuff is obsolete), and what I should do to update ? Thanks. CVS/Repository: /usr/CVSroot/XEmacs/xemacs-20 CVS/Root: :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot CVS/Tag: Trelease-21-2 -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

3 participants
4 comments

Re: prevent FAQ for 21.0 on sparc+gcc 26 years, 4 months

Didier Verna

Gunnar Evermann writes: Gunnar> I think this will hit *many* of our users with the release of 21.0, as Gunnar> nowadays gcc >=2.8 is pretty widespread. We should write an entry for Gunnar> PROBLEMS (in fact I will do that later today!), but I think almost Gunnar> nobody reads that file anyway. People should. As well as the NEWS file. Gunnar> This will give us a nice answer for comp.emacs.xemacs to the crash Gunnar> reports ('we told you so!'), but doesn't prevent the crashes. Add this to the jargon file: `RTFPF' :-) Gunnar> Isn't there anything else we can do? like, some smart logic in Gunnar> configure that screams at the user when he's trying such a build or Gunnar> some nifty #pragmas in search.c to work around this or a fix for Gunnar> gcc... In general, I think it's a bad idea to increase the hack complexity of one application in order to fix another application. Obviously, there are exceptions. Personaly, I see at least three of them: - you need extensively a feature which is broken by concept (e.g. X11 doesn't support loosing a display connection even if another one is still ok). - you *absolutely* need a feature, but some implemetations are broken. - you need a feature, and you have nothing but one only implementation (e.g. a system call). In those cases, it is acceptable to hack your own app. However, in the case of a compiler bug (especially when it can be avoided by tuning the compiler itself), I think it's a bad idea. Users can avoid it at a low cost, if they don't read the PROBLEMS file, well, next time they'll know, and hopefully, some of them will scream at the compiler developpers. So we cumulate 3 pedagogical advantages ;-) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: cus-dep.el broken 26 years, 4 months

Christoph Wedler

>>>>>"sb" == SL Baur <steve(a)xemacs.org> writes: >> Thanks for the patch. Hopefully, it will be in 21.0-b58 (BTW, when?). sb> I don't know. I had hoped that "I don't know" is the answer to "when?", not "Hopefully, it will be in 21.0-b58"... :-( Thanks for b59 anyway... - Christoph 1998-11-30 Hrvoje Niksic <hniksic(a)srce.hr> * cus-dep.el (Custom-make-dependencies): Be smarter about trapping errors. --- lisp/cus-dep.el.orig Mon Nov 30 21:03:24 1998 +++ lisp/cus-dep.el Mon Nov 30 21:03:43 1998 ＠＠ -131,15 +131,21 ＠＠ (file-name-nondirectory file)))) ;; Search for defcustom/defface/defgroup ;; expressions, and evaluate them. - (ignore-errors - (while (re-search-forward - "^(defcustom\\|^(defface\\|^(defgroup" - nil t) - (beginning-of-line) - (let ((expr (read (current-buffer)))) - (eval expr) - ;; Hash the file of the affected symbol. - (setf (gethash (nth 1 expr) hash) name))))))) + (while (re-search-forward + "^(defcustom\\|^(defface\\|^(defgroup" + nil t) + (beginning-of-line) + (let ((expr (read (current-buffer)))) + ;; We need to ignore errors here, so that + ;; defcustoms with :set don't bug out. Of + ;; course, their values will not be assigned in + ;; case of errors, but their `custom-group' + ;; properties will by that time be in place, and + ;; that's all we care about. + (ignore-errors + (eval expr)) + ;; Hash the file of the affected symbol. + (setf (gethash (nth 1 expr) hash) name)))))) (cond ((zerop (hash-table-count hash)) (princ "(No customization dependencies")

1 participants
0 comments

docstrings vs Mule/no-Mule coexistence 26 years, 4 months

Christoph Wedler

Hi, I like to have both XEmacs-21.0/Mule and XEmacs-21.0/no-Mule. I had hoped that this would be possible without two completly independent (= redundant) installations. I.e., I made both XEmacsen by 1. ./configure .... `--with-mule' 2. make 3. mv src/xemacs src/xemacs-mule 4. ./configure .... 5. make The problem now is that the docstrings are incorrect for XEmacs/Mule, e.g., I get `set-face-property' is a compiled Lisp function -- loaded from "/home/clstaff/wedler/xemacs/xemacs-21.0.59/lisp/faces.elc" (set-face-property FACE PROPERTY VALUE &optional LOCALE TAG-SET HOW-TO-ADD) Documentation: turned), 'all (all specifications will be returned), or nil (the actual specifier object will be returned). See `glyph-property' for more information. Any idea how I get correct docstrings in both XEmacs-21.0/Mule and XEmacs-21.0/no-Mule? Thanks, - Christoph

1 participants
0 comments

[OK] 21.0 "Poitou59" XEmacs Lucid (beta59) on i586-pc-linux 26 years, 4 months

Larry Ayers

Built from fresh tar-files; looks good. With this version and also the most recent 21.2 I've noticed that the finder database isn't built properly; this has been happening for quite a few beta versions. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.0.59/Installation: > (Output from most recent run of ./configure) uname -a: Linux liatris 2.1.131 #18 Sat Dec 5 20:35:23 CST 1998 i586 unknown ./configure '--prefix=/usr/local/xemacs-beta' '--with-site-lisp' '--package-path=/usr/local/xemacs-beta/lib/xemacs/packages' '--gung-ho' '--with-xpm' '--with-tiff=no' '--with-dialogs=athena' '--error-checking=none' '--debug=no' '--with-pop' XEmacs 21.0-b59 "Poitou59" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.0.59 What installation prefix should install use? /usr/local/xemacs-beta What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) 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/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. > /usr/local/src/xemacs-21.0.59/beta.err does not exist!

1 participants
0 comments

Re: the splash buffer 26 years, 4 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > Why not just put the copyright notices at the end of the splash > screen, as Stallmacs does? Then they can just fall off the end if > the screen is insufficiently large. This is exactly what Didier has done.

1 participants
0 comments

Re: gud.el broken or is it just me? 26 years, 4 months

Aki Vehtari

There seems to be other problems in XEmacs' gud.el 1) comint-output-filter-functions do not work correctly. "Eric" == Eric Ludlam <eludlam(a)mathworks.com> writes: Eric> This is a bug in XEmacs' gud.el file. I checked the Eric> Emacs gud.el, and it's gud-filter explicitly calls Eric> comint-output-filter, which in turn calls the hooks. Eric> In XEmacs gud.el, gud-filter explicitly calls Eric> insert-before-markers, thus skipping the whole comint part. 2) - In one frame two windows, in other window there is matlab-shell buffer and in other window some m-file - In matlab-shell "dbstop if error" - Focus in m-file and use matlab-shell-run-region to run some code which calls some function having error - matlab-shell/gud combo fails to arrange windows correctly in this case. The file having error is opened in window where matlab-shell was and. I think that better way would be to change the focus in to the matlab-shell buffer and open the file having error to window where the m-file was. "Eric" == Eric Ludlam <eludlam(a)mathworks.com> writes: Eric> I also noticed similar behavior under XEmacs. I set a Eric> frame variable, and wrote a find-file function (which Eric> find-file-noselects the file) and then GUD pops the buffer Eric> forwards afterwards. My quick foray into gud-filter was Eric> unrevealing. I'm curious to know if other debuggers under Eric> XEmacs do the same thing. I'll have to poke around. These are fixed in Emacs' gud.el but as said it does not yet work in XEmacs... Ave

1 participants
0 comments

Re: gud.el broken or is it just me? 26 years, 4 months

Aki Vehtari

"APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: APA> I submitted a patch against gud.el yesterday to make perldb APA> work under WindowsNT. For the same problem? Against 1993 or 1998 version? APA> Patches should go to xemacs-patches(a)xemacs.org. Yes I know, but I did not want to submit patch. I wanted to discuss what is the situation concerning gud.el and is anyone going to make latest version of gud.el to be XEmacs compatible. I think that just fixing 1993 version of gud.el leads to maintenance problems and better way would be to submit XEmacs compatibility patches to current gud.el maintainer and start using same version in both emacsen. Ave

1 participants
0 comments

Re: gud.el broken or is it just me? 26 years, 4 months

Adrian Aichner

>>>>> "Aki" == Aki Vehtari <Aki.Vehtari(a)hut.fi> writes: Hello Aki, I submitted a patch against gud.el yesterday to make perldb work under WindowsNT. Patches should go to xemacs-patches(a)xemacs.org. Regards, Adrian Aki> There is some support for gud in matlab-mode too, but Aki> `C-x SPC' which runs `gud-break' caused following error Aki> Signaling: (wrong-type-argument sequencep 83) Aki> gud-format-command("dbstop at %l in %f" 1) Aki> gud-call("dbstop at %l in %f" 1) Aki> gud-break(1) Aki> call-interactively(gud-break) Aki> Following patch fixes this, but I just wonder why no one else has Aki> noticed this? concat accepts integer arguments in Emacs but not in Aki> XEmacs. I don't remember when this was changed in XEmacs, but Aki> apparently after that change, no one has used gud.el in XEmacs Aki> (until now). Aki> Btw. gud.el in XEmacs is dated 1993 and gud.el in emacs-20.3 is Aki> dated 1998. Unfortunately gud.el in emacs-20.3 does not work in Aki> XEmacs and I don't know much work it would need to make it work and Aki> I haven't yet asked maintainer of gud.el (Eric S. Raymond) if he Aki> would be interested to help making gud.el XEmacs compatible. Aki> --- lisp/debug/gud.el.orig Mon Jan 26 06:40:48 1998 Aki> +++ lisp/debug/gud.el Wed Dec 9 14:11:16 1998 Aki> ＠＠ -2953,7 +2953,8 ＠＠ Aki> (save-excursion Aki> (beginning-of-line) Aki> (save-restriction (widen) Aki> - (1+ (count-lines 1 (point))))) Aki> + (int-to-string Aki> + (1+ (count-lines 1 (point)))))) Aki> (cdr gud-last-frame)) Aki> (substring str (match-beginning 2) (match-end 2))))) Aki> (if (string-match "\\(.*\\)%e\\(.*\\)" str)

1 participants
0 comments

gud.el broken or is it just me? 26 years, 4 months

Aki Vehtari

There is some support for gud in matlab-mode too, but `C-x SPC' which runs `gud-break' caused following error Signaling: (wrong-type-argument sequencep 83) gud-format-command("dbstop at %l in %f" 1) gud-call("dbstop at %l in %f" 1) gud-break(1) call-interactively(gud-break) Following patch fixes this, but I just wonder why no one else has noticed this? concat accepts integer arguments in Emacs but not in XEmacs. I don't remember when this was changed in XEmacs, but apparently after that change, no one has used gud.el in XEmacs (until now). Btw. gud.el in XEmacs is dated 1993 and gud.el in emacs-20.3 is dated 1998. Unfortunately gud.el in emacs-20.3 does not work in XEmacs and I don't know much work it would need to make it work and I haven't yet asked maintainer of gud.el (Eric S. Raymond) if he would be interested to help making gud.el XEmacs compatible. --- lisp/debug/gud.el.orig Mon Jan 26 06:40:48 1998 +++ lisp/debug/gud.el Wed Dec 9 14:11:16 1998 ＠＠ -2953,7 +2953,8 ＠＠ (save-excursion (beginning-of-line) (save-restriction (widen) - (1+ (count-lines 1 (point))))) + (int-to-string + (1+ (count-lines 1 (point)))))) (cdr gud-last-frame)) (substring str (match-beginning 2) (match-end 2))))) (if (string-match "\\(.*\\)%e\\(.*\\)" str)

1 participants
0 comments

2025

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 1998