August 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Vin Shelton

I'm trying to code an interactive function which I want to run under both XEmacs and FSFmacs. I want this function to maintain the region, so under XEmacs, I would use: (interactive "_") "_" is not a valid argument for (interactive) in FSFmacs, however, so how can I write this function? Thanks, vin -- In a minute there is time For decisions and revisions which a minute will reverse. T.S. Eliot [URL: http://www.cs.amherst.edu/~ccm/prufrock.html]

3 participants
2 comments

Re: (interactive "_") 24 years, 3 months

Adrian Aichner

>>>>> "Vin" == Vin Shelton <acs(a)xemacs.org> writes: Vin> I'm trying to code an interactive function which I want to run under Vin> both XEmacs and FSFmacs. I want this function to maintain the region, Vin> so under XEmacs, I would use: Vin> (interactive "_") Vin> "_" is not a valid argument for (interactive) in FSFmacs, however, so Vin> how can I write this function? Hi Vin, following can be found in emacs-20.6\src\callint.c. Another reason to use XEmacs? :-) Hope this helps, Adrian /* This comment supplies the doc string for interactive, for make-docfile to see. We cannot put this in the real DEFUN due to limits in the Unix cpp. DEFUN ("interactive", Ffoo, Sfoo, 0, 0, 0, "Specify a way of parsing arguments for interactive use of a function.\n\ For example, write\n\ (defun foo (arg) \"Doc string\" (interactive \"p\") ...use arg...)\n\ to make ARG be the prefix argument when `foo' is called as a command.\n\ The \"call\" to `interactive' is actually a declaration rather than a function;\n\ it tells `call-interactively' how to read arguments\n\ to pass to the function.\n\ When actually called, `interactive' just returns nil.\n\ \n\ The argument of `interactive' is usually a string containing a code letter\n\ followed by a prompt. (Some code letters do not use I/O to get\n\ the argument and do not need prompts.) To prompt for multiple arguments,\n\ give a code letter, its prompt, a newline, and another code letter, etc.\n\ Prompts are passed to format, and may use % escapes to print the\n\ arguments that have already been read.\n\ If the argument is not a string, it is evaluated to get a list of\n\ arguments to pass to the function.\n\ Just `(interactive)' means pass no args when calling interactively.\n\ \nCode letters available are:\n\ a -- Function name: symbol with a function definition.\n\ b -- Name of existing buffer.\n\ B -- Name of buffer, possibly nonexistent.\n\ c -- Character (no input method is used).\n\ C -- Command name: symbol with interactive function definition.\n\ d -- Value of point as number. Does not do I/O.\n\ D -- Directory name.\n\ e -- Parametrized event (i.e., one that's a list) that invoked this command.\n\ If used more than once, the Nth `e' returns the Nth parameterized event.\n\ This skips events that are integers or symbols.\n\ f -- Existing file name.\n\ F -- Possibly nonexistent file name.\n\ i -- Ignored, i.e. always nil. Does not do I/O.\n\ k -- Key sequence (downcase the last event if needed to get a definition).\n\ K -- Key sequence to be redefined (do not downcase the last event).\n\ m -- Value of mark as number. Does not do I/O.\n\ M -- Any string. Inherits the current input method.\n\ n -- Number read using minibuffer.\n\ N -- Raw prefix arg, or if none, do like code `n'.\n\ p -- Prefix arg converted to number. Does not do I/O.\n\ P -- Prefix arg in raw form. Does not do I/O.\n\ r -- Region: point and mark as 2 numeric args, smallest first. Does no I/O.\n\ s -- Any string. Does not inherit the current input method.\n\ S -- Any symbol.\n\ v -- Variable name: symbol that is user-variable-p.\n\ x -- Lisp expression read but not evaluated.\n\ X -- Lisp expression read and evaluated.\n\ z -- Coding system.\n\ Z -- Coding system, nil if no prefix arg.\n\ In addition, if the string begins with `*'\n\ then an error is signaled if the buffer is read-only.\n\ This happens before reading any arguments.\n\ If the string begins with `＠', then Emacs searches the key sequence\n\ which invoked the command for its first mouse click (or any other\n\ event which specifies a window), and selects that window before\n\ reading any arguments. You may use both `＠' and `*'; they are\n\ processed in the order that they appear." */ /* ARGSUSED */ DEFUN ("interactive", Finteractive, Sinteractive, 0, UNEVALLED, 0, 0 /* See immediately above */) (args) Lisp_Object args; { return Qnil; } Vin> Thanks, Vin> vin Vin> -- Vin> In a minute there is time Vin> For decisions and revisions which a minute will reverse. T.S. Eliot Vin> [URL: http://www.cs.amherst.edu/~ccm/prufrock.html]

1 participants
0 comments

Re: Patch: NAS_LITTLE_ENDIAN [was: NAS related source code error?] 24 years, 3 months

Edwin Wiles

On Thu, Aug 03, 2000 at 09:23:14PM +0900, Stephen J. Turnbull wrote: > Third times the charm? Last patch was missing the diff for > src/config.h.in. Patch is confirmed working! Many Thanks Stephen! -- Edwin Wiles | Computer Associates | McLean, VA, USA Preferred..: ewiles(a)mclean.sterling.com Alternative: Edwin_Wiles(a)sterling.com "The light at the end of the History Tunnel, is the oncoming train of events."

1 participants
0 comments

[BUG] introduced in supercite ? 24 years, 3 months

Didier Verna

I don't use supercite myself, but I'm reporting a problem encountered by a friend of mine whom I just convinced to switch to XEmacs. He has the following variable set, which is compliant with what the doc says. (setq sc-attrib-selection-list '(("sc-from-address" ((".*" . (bbdb/sc-consult-attr (sc-mail-field "sc-from-address"))) )))) However, this doesn't work. A diff between stallmacs's supercite and ours shows this (the function sc-select-attribution is unchanged): [...] (defun sc-scan-info-alist (alist) "Find a match in the info alist that matches a regexp in ALIST." (let ((sc-mumble "") rtnvalue) (while alist (let* ((elem (car alist)) (infokey (car elem)) (infoval (sc-mail-field infokey)) (mlist (car (cdr elem)))) (while mlist (let* ((ml-elem (car mlist)) (regexp (car ml-elem)) (thing (cdr ml-elem))) (if (string-match regexp infoval) ;; we found a match, time to return - (setq rtnvalue thing + (setq rtnvalue (if (consp thing) + (car thing) + thing) mlist nil alist nil) ;; else we didn't find a match (setq mlist (cdr mlist)) ))) ;end of mlist loop (setq alist (cdr alist)) )) ;end of alist loop rtnvalue)) Moreover, I found this ChangeLog entry in *our* source: 1999-03-18 Raymond Toy <toy(a)rtp.ericsson.se> * supercite.el: The wrong thing was returned when the match was a list. This ChangeLog is very imprecise, but looks like it is related to this problem. I'm suspecting that this change was made to the function in order to match a bogus value for the variable above, namely, were the dot between REGEXP and ATTRIBUTION was missing. How is it that we have a divergent version of supercite anyway ? It is supposed to be maintained externally. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

3 participants
2 comments

XEmacs-21.1.12 24 years, 3 months

Vin Shelton

I will be releasing the code currently checked in to the 21.1 branch as 21.1.12, probably on Friday or Saturday unless I hear of any problems with the code as it now stands. This is, therefore, an urgent plea for people to build and install the latest 21.1 from CVS. - vin

3 participants
3 comments

Supercite orphaned [was: [BUG] introduced in supercite ?] 24 years, 3 months

Stephen J. Turnbull

Well, there we go: supercite is officially orphaned. (I was gonna quote it, but didier did already <mux7l9ywwdj.fsf(a)uzeb.lrde.epita.fr>.) We should remove the reference to supercite-help(a)python.org in our package source, and set the maintainer to XEmacs Developers, I guess. We ought to find out if anybody is taking responsibility over at the FSF. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

Re: [BUG] introduced in supercite ? 24 years, 3 months

Didier Verna

I wrote: > I must say that facing XEmacs packages externally maintained, and yet > divergent in our package source tree rather upsets me :-( Unless there are > very good reasons for it, we should be much more careful about the > packages-related patches that are submitted to us and force people to > communicate with the real maintainers first. Of course, the following message that I just received pretty much relativize my feelings expressed above :-) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

Re: [BUG] introduced in supercite ? 24 years, 3 months

Didier Verna

Stephen J. Turnbull wrote: > Been there, done that, it doesn't work with the XEmacs version, and I > made the change below, which works for me. Now, tell me about it! :-) > Unless either Raymond or Barry has something to say about it, I would > say submit a patch to xemacs-patches revert that section to the > upstream original. [...] > Probably because Bob Weiner wanted some changes for Infodock (see the > top of the XEmacs version of the file). Steve Baur also added a > function. Why they didn't get integrated upstream I can't guess. I must say that facing XEmacs packages externally maintained, and yet divergent in our package source tree rather upsets me :-( Unless there are very good reasons for it, we should be much more careful about the packages-related patches that are submitted to us and force people to communicate with the real maintainers first. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

popup-mode-menu in 21.2.35 24 years, 3 months

Dmitry Yaitskov

I had Sh-f1 mapped to popup-mode-menu, to be able to invode context menus w/out using the mouse. In 21.2.35, this stopped working - now I get the message "popup-mode-menu must be bound to a mouse or misc-user event". My question is - why can't I have it also assigned to a key? And if that's a feature, how can I do what I did before? Thanks. -- Cheers, -Dima.

2 participants
1 comments

cperl faces 24 years, 3 months

Sean MacLennan

I have just started to learn perl and was going through the cperl faces to darken one. I stumbled across two faces that looked very interesting and very out of place (the default background is the emacs lightyellow2). These where `Cperl Array Face' and `Cperl Hash Face'. This looked very useful to us extreme perl novices. However, the faces where not showing up on my screen. I did a quick check in the cperl-mode.el file and on line 5802 found the following code: (and (fboundp 'turn-on-font-lock) ; Check for newer font-lock (not cperl-xemacs-p) ; not yet as of XEmacs 19.12 If you comment out the (not cperl-xemacs-p) line, the two faces seem to work. Does anybody remember/know why this was put in and whether it is safe to remove it now. I am running the lotsa ones release (21.1.11) of XEmacs and prog-modes version 1.28. Also, the comment for the `Cperl Nonoverridable Face' seems to come from the `Cperl Array Face' and does not really describe what the face does. Thanks, Sean "Perl Peon" MacLennan --

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 August 2000