August 2000 - XEmacs-Beta - XEmacs Mailing List Archives

XEmacs Build Report for XEmacs-21.1.12 23 years, 8 months

XEmacs Build 'Bot

Hello XEmacs beta testers. I am in the process of building XEmacs-21.1.12 for distribution. I have tested the attached configuration. Have a great day! Sincerely, The XEmacs Build 'Bot (revision 2) -- uname -a: Linux zion.rcn.com 2.2.17pre14 #2 SMP Sun Jul 30 21:21:10 EDT 2000 i686 unknown ./configure '--prefix=/home/acs/cvsroot' '--cflags=-O' '--with-mule' '--without-x11' '--debug=no' '--error-checking=none' XEmacs 21.1.12 "Channel Islands" configured for `i686-pc-linux'. Where should the build process find the source code? /home/acs/cvsroot/xemacs-21.1 What installation prefix should install use? /home/acs/cvsroot 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 -O 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? none Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for LDAP. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits.

1 participants
0 comments

Re: popup-mode-menu in 21.2.35 23 years, 8 months

Dmitry Yaitskov

Yoshiki Hayashi <yoshiki(a)xemacs.org> wrote: > Dmitry Yaitskov <dimas(a)home.com> writes: > > > 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. > > I cannot reproduce it with latest CVS beta. Could you try > it and see what happens? If it still fails, posting lisp > backtrace would be nice. Updated from CVS approx at 3pm 4-Aug-2000 - got the same problem. Here's what I get with debug-on-error t: Signaling: (error "popup-mode-menu must be bound to a mouse or misc-user event") call-interactively(popup-mode-menu) -- Cheers, -Dima.

1 participants
0 comments

XEmacs 21.2 + OpenMotif crashes 23 years, 8 months

Martin Buchholz

If I start up an XEmacs built with OpenMotif I get two X errors, and a crash on C-x C-c. Perhaps Alastair (or Ben, or Andy) would like to try to debug this, since this is your area of expertise. See that X_ConvertSelection below. You can get access to my machine my sending me your ssh public key. It looks like this: xemacs: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 19 (X_DeleteProperty) Resource id in failed request: 0x0 Serial number of failed request: 80 Current serial number in output stream: 81 xemacs: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 24 (X_ConvertSelection) Resource id in failed request: 0x0 Serial number of failed request: 81 Current serial number in output stream: 81 Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. If you have access to the PROBLEMS file that came with your version of XEmacs, please check to see if your crash is described there, as there may be a workaround available. Otherwise, please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /local/xemacs/build/mo9OM/src/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: kill-emacs() # bind (arg) save-buffers-kill-emacs(nil) # bind (command-debug-status) call-interactively(save-buffers-kill-emacs) # (condition-case ... . error) # (catch top-level ...)

1 participants
0 comments

Re: [BUG] introduced in supercite ? 23 years, 8 months

Didier Verna

Raymond Toy <toy(a)rtp.ericsson.se> wrote: > Stephen> Unless either Raymond or Barry has something to say about > Stephen> it, I would say submit a patch to xemacs-patches revert > Stephen> that section to the upstream original. For discussion > Stephen> purposes, here's my diff. The > > Of course if you do this, you'll hose me! Unless customize handles > those lists better now.... Yes, but Ray, you should realize that breaking supercite is not the good way to improve customize ;-) How about just this instead ? Does that suit your needs (both of you) ? Index: comm/supercite/supercite.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-packages/comm/supercite/supercite.el,v retrieving revision 1.8 diff -u -w -r1.8 supercite.el --- supercite.el 1999/12/02 08:35:18 1.8 +++ supercite.el 2000/08/04 08:16:00 ＠＠ -454,9 +454,13 ＠＠ attribution. Note that the variable `sc-preferred-attribution-list' must contain an element of the string \"sc-consult\" for this variable to be consulted during attribution selection." - :type '(repeat (list string (repeat (cons regexp - (choice (repeat (repeat sexp)) - string))))) + :type '(repeat (group (string :tag "Infokey") + (repeat :format "\n%v%i\n" + (cons :format "\n%v" + (regexp :tag " Regexp") + (choice :tag "Attribution" + :format "%{%t%}: %[choice%] %v" + sexp string))))) :group 'supercite-attr) (defcustom sc-attribs-preselect-hook nil ＠＠ -789,9 +793,7 ＠＠ (thing (cdr ml-elem))) (if (string-match regexp infoval) ;; we found a match, time to return - (setq rtnvalue (if (consp thing) - (car thing) - thing) + (setq rtnvalue thing mlist nil alist nil) ;; else we didn't find a match -- / / _ _ 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

2 participants
1 comments

Options | Font vs. Options | Size 23 years, 8 months

Stephen J. Turnbull

Order matters. xemacs -vanilla & -> Courier 12.0 pt Options | Font | LucidaTypewriter -> LucidaTypewriter 12.0pt Options | Size | 16 -> Courier 16.0 pt Options | Font | LucidaTypewriter -> LucidaTypewriter 16.0pt It shouldn't. uname -a: Linux tleepslib 2.2.10 #2 Thu Jun 24 19:22:23 JST 1999 i686 unknown /coda/Projects/XEmacs/21.2-HEAD/configure '--srcdir=/coda/Projects/XEmacs/21.2-HEAD' '--with-widgets=athena' '--with-athena=3d' '--with-sound=none,nas' '--with-mule' '--with-xim=xlib' '--with-xfs' '--use-union-type' '--pdump' XEmacs 21.2-b35 "Nike" configured for `i686-pc-linux'. Compilation / Installation: Source code location: /coda/Projects/XEmacs/21.2-HEAD Installation prefix: /usr/local Operating system description file: `s/linux.h' Machine description file: `m/intel386.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow Relocating allocator for buffers: no GNU version of malloc: yes - Using Doug Lea's new malloc from the GNU C Library. Window System: Compiling in support for the X window system: - X Windows headers location: /usr/X11R6/include - X Windows libraries location: /usr/X11R6/lib - Handling WM_COMMAND properly. Compiling in support for the Athena widget set: - Athena headers location: X11/Xaw3d - Athena library to link: Xaw3d Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Using Athena native widgets. TTY: Compiling in support for ncurses. Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. Compiling in support for PNG images. Compiling in support for JPEG images. Compiling in support for TIFF images. Sound: Compiling in support for NAS (network audio system). Databases: Compiling in support for Berkeley database. Compiling in support for PostgreSQL. - Using PostgreSQL header file: postgresql/libpq-fe.h - Using PostgreSQL V7 bindings. Internationalization: Compiling in support for Mule (multi-lingual Emacs). Compiling in support for XIM (X11R5+ I18N input method). - Using raw Xlib to provide XIM support. - Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for the WNN input method on Mule. Mail: Compiling in support for "dot-locking" mail spool file locking method. Other Features: Compiling in support for dynamic shared object modules. Using the union type for Lisp_Objects. Using the new portable dumper. Compiling in support for extra debugging code. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: ---------------------------------------------------------

1 participants
0 comments

Re: More on find-file dialogue failure 23 years, 8 months

Didier Verna

Yoshiki Hayashi <yoshiki(a)xemacs.org> wrote: > Didier Verna <didier(a)xemacs.org> writes: > > > BTW, I'd like someone to clearly and slowly explain to me what > > means > > "running the packages in place" after all. I still don't > > understand what this > > means. What was not possible before, and > > is possible now ? > > I think it makes it possible to install package tree without > using --package-path or actually installing it to > $prefix/lib/xemacs. Huh, yes, but where do you put them then ? :-) I can understand that you want to put them outside $prefix/lib/. I've always considered the damn packages should be located under $prefix/share/xemacs. But what's the point in *not* using --package-path to do so ?? -- / / _ _ 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

More on find-file dialogue failure 23 years, 8 months

Peter B. West

This thread was originally 21.2.35 C-x C-f failure. linux 2.2.14-6.0.1 I previously used cvs update to maintain a copy of the xemacs source, but that is no longer accessible to me. I tried to find a function to feed in to debug-on-entry, and find-file looked promising, but debug-on-entry was not known to xemacs, so something seems to have gone wrong in the build. My environment is unchanged from previous incarnations, except that the .xemacs directory has been initialised, and .emacs has gone, following my startup of the new version. Any suggestions? -- Peter B. West pbwest(a)netscape.net +353 1 637 2455(W) "Lord, to whom shall we go?"

3 participants
4 comments

Re: [BUG] introduced in supercite ? 23 years, 8 months

Raymond Toy

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>> "drv" == Didier Verna <didier(a)xemacs.org> writes: drv> I don't use supercite myself, but I'm reporting a drv> problem encountered by a friend of mine whom I just convinced drv> to switch to XEmacs. drv> He has the following variable set, which is compliant with drv> what the doc says. drv> (setq sc-attrib-selection-list drv> '(("sc-from-address" drv> ((".*" . (bbdb/sc-consult-attr (sc-mail-field "sc-from-address"))) drv> )))) Stephen> Been there, done that, it doesn't work with the XEmacs version, and I Stephen> made the change below, which works for me. I had no idea that that Stephen> was the original code, or what was going on with the code either, Stephen> didn't report the bug, and forgot to go back to the problem. :-( Ok, I took a look at why I did this. I remember now that I switched to using customize to set up sc-attrib-selection-list. I have some code in there (pretty mangled): [INS] [DEL] Cons-cell: Regexp: $[^ ]+$ $[^ ]+$ ($EUS\|QCS\|ECS\|CRD\|EML\|LMC\|EED\|EIN\|EMN\|QML\|ERA$) Choice: [Value Menu] Repeat: [INS] [DEL] Repeat: [INS] [DEL] Lisp expression: let [INS] [DEL] Lisp expression: ((field (sc-mail-field "from"))) [INS] [DEL] Lisp expression: (string-match "\" ?\$[^ ]+\$ \$[^ ]+\$ (\$EUS\\|QCS\\|ECS\\|CRD\\|EML\\|LMC\\|EED\\|EIN\\|EMN\\|QML\\|ERA\$)" field) [INS] [DEL] Lisp expression: (match-string 1 field) [INS] [INS] I really just wanted: (let ((field (sc-mail-field "from"))) (string-match "\" ?\$[^ ]+\$ \$[^ ]+\$ (\$EUS\\|QCS\\|ECS\\|CRD\\|EML\\|LMC\\|EED\\|EIN\\|EMN\\|QML\\|ERA\$)" field) (match-string 1 field)) but couldn't get customize to insert it correctly. This was the only way I could get customize to put in the code at that time. It seems that an extra set of parens are inserted by customize so the change to supercite was supposed to remove it. I didn't understand customize but could fix supercite, so I did. :-( I'm pretty sure I reported my problems to this list bug got no replies on my customize problem so I hunted down the quick fix myself. Stephen> Unless either Raymond or Barry has something to say about Stephen> it, I would say submit a patch to xemacs-patches revert Stephen> that section to the upstream original. For discussion Stephen> purposes, here's my diff. The Of course if you do this, you'll hose me! Unless customize handles those lists better now.... Ray

2 participants
1 comments

Re: (interactive "_") 23 years, 8 months

Vin Shelton

Thanks to Gleb, Adrian and Hrvoje. Shouldn't the help say something about the transient nature of setting this variable: `zmacs-region-stays' is a built-in boolean variable. -- loaded from "filladapt" Value: nil Documentation: Whether the current command will deactivate the region. Commands which do not wish to affect whether the region is currently highlighted should set this to t. Normally, the region is turned off after executing each command that did not explicitly turn it on with the function zmacs-activate-region. Setting this to true lets a command be non-intrusive. See the variable `zmacs-regions'. The same effect can be achieved using the `_' interactive specification. I propose the following patch: --- src/editfns.c~ Sat Jul 29 16:31:59 2000 +++ src/editfns.c Thu Aug 3 21:56:11 2000 ＠＠ -2444,6 +2444,8 ＠＠ See the variable `zmacs-regions'. The same effect can be achieved using the `_' interactive specification. + +`zmacs-region-stays' is reset to nil before each command is executed. */ ); zmacs_region_stays = 0; >>>>> On Fri, 4 Aug 2000 01:05:39 +0200, Hrvoje Niksic <hniksic(a)fly.srk.fer.hr> said: Hrvoje> On Thu, Aug 03, 2000 at 06:18:37PM -0400, Vin Shelton wrote: >> 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? Hrvoje> I believe this should do it: Hrvoje> (setq zmacs-region-stays t) - vin

1 participants
0 comments

2000-08-04: Status of http://sourceforge.net/projects/xemacs/ 23 years, 8 months

Adrian Aichner

>>>>> "APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: APA> Hello All! Here's a real short update, focused on http://xemacs.sourceforge.net/ APA> This is intended to be a bootstrapper for anybody interested in APA> getting started on the sourceforge half of XEmacs development. APA> Q: Has XEmacs development moved to sourceforge? APA> A: No. Currently there is only one CVS module on sourceforge, namely APA> xemacsweb. This is the content of APA> xemacweb＠www.xemacs.org:~/genpage which prduces most of the static APA> content of xemacweb＠www.xemacs.org:~/docs. Mailing list and their APA> archives, for one, have not been moved to sourceforge. APA> Q: Which is the offical XEmacs Website? APA> A: For a transitional period of at least two weeks it is good old APA> http://www.xemacs.org. To visit the new site (and receive bonus points APA> for testing) go to http://xemacs.sourceforge.net/, either directly, APA> or via "Project Homepage" from APA> https://sourceforge.net/projects/xemacs/. Thereafter, if all goes APA> well, http://xemacs.sourceforge.net/ will answer for APA> http://www.xemacs.org if someone puts in the work to make it so APA> (http://sfdocs.sourceforge.net/sfdocs/display_topic.php?topicid=33). APA> Q: So what's so exciting about the new site? APA> A: It is fully CVS-controlled, all HTML documents are batch-validated APA> daily using XEmacs/PSGML by xemacsweb/Makefile according to their APA> individual DTD. Alltogether there are <10 HTML errors left between APA> all .html files on the XEmacs site there! APA> Q: When can I contribute to XEmacs website content again? APA> A: Now. Get yourself a sourceforge account via APA> https://sourceforge.net/account/register.php and contact one of APA> your friendly XEmacs admins to become a developer, using APA> https://sourceforge.net/project/memberlist.php?group_id=11. Meanwhile I have added Real Name: Andrew J Cosgriff Email Addr: ajc at users.sourceforge.net and Real Name: Kevin Oberman Email Addr: koberman at users.sourceforge.net to the list of xemacs developers on sourceforge on their request. APA> Q: How do I make changes to the XEmacs CVS repository on sourceforge? APA> A: Follow instructions in https://sourceforge.net/cvs/?group_id=11 to APA> checkout (20MB after running make) and commit the sources via CVS. APA> Q: How can I keep track of changes being made to the repository? APA> A: Subscribe yourself to xemacs-checkins(a)lists.sourceforge.net[1] at APA> http://lists.sourceforge.net/mailman/listinfo/xemacs-checkins. We APA> may even subscribe xemacs-cvs(a)xemacs.org to the list, if somebody I haven't got any feedback on this. Unless people say otherwise I will subscribe xemacs-cvs(a)xemacs.org to xemacs-checkins(a)lists.sourceforge.net This makes sense since xemacsweb patches are also sent to and reviewed on xemacs-patches(a)xemacs.org. APA> can send back a confirmation reply from there. The mailing list APA> archive at APA> http://www.geocrawler.com/lists/3/SourceForge/5231/0/4114662/ is APA> actually updated quite switfy (> 30 minutes?). APA> Q: How do I inspect the state of the actual files behind APA> http://xemacs.sourceforge.net/? APA> A: Read APA> http://sfdocs.sourceforge.net/sfdocs/display_topic.php?topicid=8 APA> for reference, although steps 1 .. 7 are already done. APA> Webpage contents are physically rooted at APA> shell.sourceforge.net:/home/groups/xemacs/htdocs where htdocs is APA> currently a symlink to xemacsweb. APA> Q: How do these pages get updated? This was my most active area recently. With help from Martin R. Buchholz I was able to implement updating of the XEmacs website at http://xemacs.sourceforge.net/ via cvs commit directly! All of this is done on behalf of user xemacs and the crontab entry for adriana has been disabled. The delay in commiting is not noticable for me (takes much longer for me until the passphrase prompt appears). Due to a substancial Makefile change we can even effort to HTML-validate always after a commit. CVS update and make are kicked off by cvs commit to cvs.sourceforge.net, but these processes are run in background on shell1.sourceforge.net to avoid locking up the CVS repository (as suggested in the CVS manual). The Makefile now only validates any HTML files younger than the validate-time-stamp touched after validation. Furthermore the genpage rule is now depending on CONTENT_FILES only. Since genpage output goes to the current directory, copying of files is not needed. genpage now only takes care of those HTML files generated from .content source files. genpage had to be patched to check file mtime to the second, not just to the day to avoid needless HTML file updates causing wasteful HTML validation via XEmacs. I will submit my genpage changes (I imported genpgage 1.0.7 on a vendor branch for ease of future updates) to the author. Please send me any feedback on the current commit/update process, especially actual problems you may experience. http://xemacs.sourceforge.net/cvs-update-make.err contains site update logs, for those who know it exists :-) This can come in handy and reduces the need to login to shell1.sourceforge.net even further. APA> A: They are currently being updated a personal crontab entry of mine APA> (temporarily, until Martin hand-holds me through direct updates APA> from cvs commits). Here's[2] that crontab entry (as others may not APA> have the privelege to look at it with "crontab -u adriana -l", APA> which doesn't work even for me). This gets mailed to APA> xemacs-checkins(a)lists.sourceforge.net for now. APA> xemacs-webmaint(a)xemacs.org may be a better destination when I have APA> fixed ALL validation errors (there are still FIVE!). Above paragraph is history! APA> Q: What editor can I use on shell.sourceforge.net? APA> A: ed, when you use ssh. :-) I have installed a pretty well-featured APA> XEmacs-21.1.11 under APA> shell.sourceforge.net:/home/groups/xemacs/tools/xemacs/bin for all APA> of us to use. See ~adriana/.profile for my setup. I also had to APA> get a decent tty for Windows NT for XEmacs to run, be it -nw even. APA> I installed APA> http://www.chiark.greenend.org.uk/~sgtatham/putty/latest/putty.exe APA> and am quite happy with it. APA> Q: Can I upload big files to some kind of /pub on sourceforge? APA> A: Yes, developers can copy files to APA> <user>＠shell1.sourceforge.net:/home/groups/ftp/pub/xeemacs using APA> scp1. Anyone can download from this URL: APA> ftp://xemacs.sourceforge.net/pub/xemacs/[3] APA> Q: How much did Adrian sleep lately? APA> A: Permission denied. APA> I hope this will be helpful to others. APA> We should probably start assigning jobs between us to further APA> development on sourceforge. Trey and John have been very quiet lately. Are you guys still around? APA> A big task would be conversion of mailing list interfaces and APA> archives, although I am not sure we want to move them away from APA> xemacs.org. What's the managerial plan for the mailing list interfaces and archives? Should these move to sourceforge too? APA> Making all URLs in xemacsweb relative is on our collective to-do list. APA> genpage should come to our aid here. More on that later. Hah, I have converted all links (except for xemacsweb/FAQ) to relative. This makes links in xemacsweb/Architecing-XEmacs/ work and I can use Netscape to navigate thru the documents in my local xemacsweb working directory. This is pretty cool! Most notably the image links included via template.html are broken in all subdir HTML files generated from subdir .content files. A fix for this will be devised shortly via a genpage recipe. APA> Any comments? APA> Adrian Best regards, Adrian -- Adrian Aichner <adrian(a)xemacs.org>

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