July 1998 - XEmacs-Beta - XEmacs Mailing List Archives

New supercite feature, anyone want it? 26 years, 4 months

SL Baur

SL Baur <steve(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: I have an extension to Supercite citation in response to a request on the Gnus devel list that makes lines like the above. Is anyone else interested in seeing this get integrated into Supercite? (defun sc-header-author-email-writes-in-group () "sc-author <email-addr> writes in group:" (let* ((sc-mumble "") (whofrom (sc-whofrom)) (group (or gnus-newsgroup-name "")) (group-name (or (gnus-group-find-parameter group 'to-address) (gnus-group-find-parameter group 'to-list) (gnus-group-find-parameter group 'to-group) (message-fetch-field "newsgroups")))) (if whofrom (insert sc-reference-tag-string (sc-hdr "" (sc-mail-field "sc-author") " ") (or (sc-hdr "<" (sc-mail-field "sc-from-address") ">" t) (sc-hdr "<" (sc-mail-field "sc-reply-address") ">" t) "") (if group-name (format " writes in %s" group-name) " writes") ":\n")))))

2 participants
1 comments

Re: [PATCH] XEmacs obsolete function 26 years, 4 months

Didier Verna

Colin Rafferty <craffert(a)ms.com> writes: > In which version of XEmacs did `extent-property' get created? AFAICS, extent-property is here since at least 19.14 --didier

1 participants
0 comments

Re: [PATCH] XEmacs obsolete function 26 years, 4 months

Colin Rafferty

Didier Verna writes: > This patch avoids using extent-data, a function that is obsolete at > least from XEmacs 20.3 and will completely disapear in XEmacs 21.2 > and later. > [... s/extent-data/extent-property/g ...] In which version of XEmacs did `extent-property' get created? We're trying to be backwards-compatible, so I need to know whether to apply the patch as-is, or do a song-and-dance function. -- Colin

1 participants
0 comments

Re: no inline mime images :-( 26 years, 4 months

Holger Schauer

>>>>"sb" == SL Baur schrieb am 24 Jul 1998 18:23:45 -0700: >> Boom... that showed up as content-type text/plain (as opposed to >> multipart/mixed), with the jpeg inline, as follows: >> [2 <image/jpeg>] sb> This image did not display for me in either XEmacs or xv. Displays fine for me in "21.0 \"Zhong Wei\" XEmacs Lucid", "Gnus v5.6.24", libjpeg-6a. Holger -- --- http://www.coling.uni-freiburg.de/~schauer --- "Aus dem gleichen Grund gefällt mir auch Babylon5 besser als Star Trek." -- Aus "Wie starte ich einen Endlosthread ?", Teil 666

1 participants
0 comments

Re: scheme - my opinion 26 years, 4 months

Holger Schauer

>>>>"SJT" == Stephen J Turnbull schrieb am Fri, 17 Jul 1998 12:28:15 +0900 (JST): SJT> We want an engine that will be usable on all platforms we SJT> support, an efficiency improvement on most of them, and a big SJT> efficiency improvement on as many as possible. How many of the Scheme implementations mentioned does are ruled out by this commitment (to which I totally agree) ? Holger -- --- http://www.coling.uni-freiburg.de/~schauer --- "Aus dem gleichen Grund gefällt mir auch Babylon5 besser als Star Trek." -- Aus "Wie starte ich einen Endlosthread ?", Teil 666

1 participants
0 comments

Re: Core dump in Benadir 26 years, 4 months

Gunnar Evermann

Carsten Leonhardt <leo(a)arioch.oche.de> writes: > By doing a > > M-x apropos-value RET latin-iso RET > > from a vanilla XEmacs I get a core dump. I can't reproduce that on linux or solaris. Are you using MULE? Please post your Installation file. Gunnar -- Gunnar Evermann Natural Language Systems Group, University of Hamburg EMail: Gunnar.Evermann(a)nats.informatik.uni-hamburg.de

1 participants
0 comments

Re: [crash] GC-bug in Fcall-interactive 26 years, 4 months

Gunnar Evermann

SL Baur <steve(a)xemacs.org> writes: > Gunnar Evermann <Gunnar.Evermann(a)nats.informatik.uni-hamburg.de> writes in xemacs-beta(a)xemacs.org: > > > try this with "Benadir": > > - xemacs -vanilla > > > - C-h k > > > - click on the Options/Fonts menu entry (generating the list of fonts) > > and wait for the submenu to pop up > > > - click somewhere in the window outside the menus > > > - watch XEmacs dump core. > > Reproduced with 21.0. Cannot reproduce in 20.4. Hm, indeed same here, but then here on my sun "Benadir" doesn't crash either -- strange... > If there are still problems, the 20.4 code is likely to be > enlightening. Not really, I don't see a significant change in the source. I only protected the prompt in the '[kK]' cases, in all the others callN is used and provides the gcpro. This violates 'caller protects' but I guess that's acceptable here. BTW, the nested version of GCPRO isn't documented in the internals manual. I only found it by chance in lisp.h. I'll send a patch for internals.texi later this week. Anyway here's the patch: 1998-07-27 Gunnar Evermann <Gunnar.Evermann(a)nats.informatik.uni-hamburg.de> * callint.c (Fcall_interactively): GCPRO prompt string before passing it to Fread_key_sequence --- callint.c.orig-21.0-b50 Wed May 6 11:46:26 1998 +++ callint.c Mon Jul 27 12:22:26 1998 ＠＠ -715,7 +715,14 ＠＠ } case 'k': /* Key sequence (vector of events) */ { - Lisp_Object tem = Fread_key_sequence (PROMPT (), Qnil, Qnil); + struct gcpro ngcpro1; + Lisp_Object tem; + Lisp_Object key_prompt = PROMPT (); + + NGCPRO1(key_prompt); + tem = Fread_key_sequence (key_prompt, Qnil, Qnil); + NUNGCPRO; + visargs[argnum] = Fkey_description (tem); /* The following makes `describe-key' not work with extent-local keymaps and such; and anyway, it's ＠＠ -728,7 +735,14 ＠＠ case 'K': /* Key sequence (vector of events), no automatic downcasing */ { - Lisp_Object tem = Fread_key_sequence (PROMPT (), Qnil, Qt); + struct gcpro ngcpro1; + Lisp_Object tem; + Lisp_Object key_prompt = PROMPT (); + + NGCPRO1(key_prompt); + tem = Fread_key_sequence (key_prompt, Qnil, Qt); + NUNGCPRO; + visargs[argnum] = Fkey_description (tem); /* The following makes `describe-key' not work with extent-local keymaps and such; and anyway, it's

1 participants
0 comments

Re: Other packaging issues I've been slapped in the face with 26 years, 4 months

Michael Sperber

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes in xemacs-beta(a)xemacs.org: >>>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> 1. My decision to base primary package searching off of $prefix appears sb> to be have a suboptimal one, but probably too late to fix for 21.0. >> Could you elaborate? I seem to've missed something, and this sounds >> as if it affects my code. sb> I'm not sure I fully like the package-path hard-coding from $prefix. sb> It makes it somewhat difficult to transport binaries. Fortunately the sb> relative path searching appears quite adequate. Now, we went around and around with this issue in the original discussion, and you finally convinced me it was necessary. Too bad :-) You could easily avoid hard-coding $prefix into the binary kit if you only propagated it to src/paths.h. This is a trivial change but, IMHO, too late for 21.0, and not terribly important. I'll submit a patch for 21.1. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

try-completion buglet? 26 years, 4 months

Darryl Okahata

finds an "exact" match but with differing case? For example: (let ((completion-ignore-case t)) ;; ignore case (try-completion "foo" '(("Foo" . 1))) ;; Returns "Foo" (try-completion "Foo" '(("Foo" . 1))) ;; Returns t ) I think `t' should be returned for both cases. Is this the desired action, or is this a bug? -- Darryl Okahata Internet: darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

1 participants
0 comments

21.0 elc not readable by 20.4 (when using dolist) 26 years, 4 months

Christoph Wedler

When I load an elc file, compiled by XEmacs-21.0-b47, in XEmacs-20.4, I get the following error Invalid read syntax: "#" Loading /home/clstaff/wedler/emacs/.bugs/bug-elc.elc... The source file looks like: bug-elc.el: (dolist (dummy '(1 2 3))) The elc file from XEmacs-21.0 contains: (byte-code "ÀÁ«＠A¬w*Á" [(1 2 3) nil dummy #1=#:--dolist-temp--35781] 3) The culprit is #1=#. This is at least something for the NEWS file... - Christoph

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 July 1998