January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: customize versus supercite 25 years, 3 months

Raymond Toy

>>>>> "Raymond" == Raymond Toy <toy(a)rtp.ericsson.se> writes: Raymond> I don't know what to do about customize in this case. Oops. I've found that if I do this in customize, I get what I want: Sc Attrib Selection List: * [INS] [DEL] List: String: from Repeat: [INS] [DEL] Cons-cell: Regexp: "$[^ ]+$ $[^ ]+$ (EUS) 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)" field) [INS] [DEL] Lisp expression: (match-string 1 field) [INS] [INS] Hardly intuitive. Is this the way it's supposed to work? It would seem much more intuitive if I could have just entered [INS] [DEL] Lisp expression: (let ((field (sc-mail-field "from"))) (string-match "\"\$[^ ]+\$ \$[^ ]+\$ (EUS)" field) (match-string 1 field)) Ray

1 participants
0 comments

customize versus supercite 25 years, 3 months

Raymond Toy

I've been trying to get supercite to understand addresses produced by our *wonderful* exchange server. Addresses look like "Raymond Toy (EUS)" <EUSRTOY(a)am1.ericsson.se> The solution I came up with is to use sc-attrib-selection-list with sc-consult to get what I want. What I did was to use this for sc-attrib-selection-list: (("from" (("\"\$[^ ]+\$ \$[^ ]+\$ (EUS)" (let ((field (sc-mail-field "from"))) (string-match "\"\$[^ ]+\$ \$[^ ]+\$ (EUS)" field) (match-string 1 field)))))) If I set this directly, this almost works. The problem is in sc-select-attribution when it tries to eval the list. sc-scan-info-alist returns that as '((let ((field ...)))) which can't be eval'ed. I had to use (eval (first attrib)) instead of just (eval attrib). I guess I could have made sc-scan-info-alist return the right thing too. Now, when I tried to use customize to set this, customize puts an extra set of parens around the list, so sc-select-attribution now sees '(((let ((field ...))))), which is even worse. I can supply a patch for supercite, if someone can tell me if sc-select-attribution or sc-scan-info-alist should be changed. I don't know what to do about customize in this case. Ray

1 participants
0 comments

Packages and Building XEmacs from CVS 25 years, 3 months

Alastair Burt

Dear beta mailing listers, I am still having trouble trying to build XEmacs 20.1 from CVS. I would prefer to build from CVS, because eventually I would like to add x-symbol to CVS tree. I configure like this: ./configure --prefix=/home/burt/lib/xemacs --with-mule--package-path="~/.xemacs::/home/burt/lib/xemacs/lib/xemacs/mule-packages:/home/burt/lib/xemacs/lib/xemacs/xemacs-packages" I have obtained mule-base from CVS and put it somewhere in this package path. Thus /home/burt/lib/xemacs/lib/mule-packages/mule-base/_pkg.el . . . /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-category.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-ccl.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-charset.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-cmds.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-cne.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-coding.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-debug.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-diag.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-files.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-help.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-init.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-keyboard.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-misc.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-trex.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-tty-init.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-util.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/mule-x-init.el /home/burt/lib/xemacs/lib/mule-packages/mule-base/package-info.in When I build, I get the following message: Loading /home/burt/Desktop/XEmacs-CVS/xemacs-21.0/src/../lisp/dumped-lisp.el... (108) Error: dumped file mule-charset.elc does not exist Error: dumped file mule-coding.elc does not exist Error: dumped file mule-files.elc does not exist So the question is: how do I build the mule package (without a working XEmacs 21) and how do I get the XEmacs build process to see it? --- Alastair

1 participants
0 comments

Re: rssh.el interactions with ange-ftp/efs 25 years, 3 months

David Maslen

Sandy Rutherford <sandy(a)math.ubc.ca> writes: > Yuck! This is horrible syntax. I frequently use EFS to edit files as > root on the local host. In fact, since the null string for the > hostname defaults to the local host, then a quick edit of /etc/hosts > can be accomplished by editing /root＠:/etc/hosts. The RFC 1738 syntax > that you describe above would turn this into a mess. I would find this convenient too, except by default my linux distribution, denies root ftp (and telnet) access. Now obviously I could change this, but my usual attitude toward these security issues is that wiser heads than mine have made it this way for a reason. I can log in as root with ssh, if I could do the eqivalent of the above using ssh I'd be happier. -- Binary Bar - Australia's first free access internet bar/cafe/gallery. 243 Brunswick Street, Fitzroy, Melbourne, Australia. 3pm - 1am http://www.binary.net.au/ Running on Debian/GNU Linux

3 participants
5 comments

enhanced pop naming 25 years, 3 months

Andy Piper

Due to various problems it looks like I will not be able to fold my changes to pop back into the original source. So do I: a) leave the name the same and mark it as an XEmacs specific version b) change the name (and symbols) to avoid collision with the "real" version c) if c what name should I choose. I'm inclined to just use pop- instead of pop3-. Other possibilities are xpop3, or pop3client or something andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

Re: What to do with modules now ... 25 years, 3 months

Soren Dayton

"J. Kean Johnston" <jkj(a)sco.com> writes: > All, > > Once the module loading technology is in place and people are happier > with it, I would like to start work on ripping out major parts of XEmacs > and putting them in modules. I havem in my prototype tree, a mechanism > in place where a given source file can either be compiled in as part > of the dumped Emacs, or as a module. If module loading is availible, > the makefile is constructed in such a way that it compiles things as > modules rather than part of the dumped Emacs. This is a good thing. > > It is not only possible, but preferable (I believe) to make large parts of > XEmacs modules. It will also make distribution a lot easier. I am working > on making the TTY and X11 code loadable, so that you only ever load in > those parts that you care about. Doesn't this (demand paging?) happen on virtually every operating system out there? (given some sort of assumption about locality in some way) I guess that you could argue "no" because some sort of initialization that has to occur. (could this be done lazily to get some of the same effect?) > This gives users choices they didnt have before (eg, I think I'll try > loading the Lucid widgets instead of the mOtif ones) This, I buy. This would be very nice to have. > and it reduces the > size of the in-memory footprint of Emacs considerably. See above. Does this _really_ matter so much? The fact is that it _is_ all shared, and it _is_ demand paged, so this is sort of a possibly shaky win. Would it _really_ be worth the work? Soren

5 participants
7 comments

Re: Beware of modules. 25 years, 3 months

William M. Perry

Martin Buchholz <martin(a)xemacs.org> writes: > >>>>> "Kyle" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: > > Kyle> Hrvoje Niksic writes: > >> wmperry(a)aventail.com (William M. Perry) writes: > >> > >> > Having everything in src/ bugs me. (...) > >> > >> I think I hear Kyle's chainsaw buzzing. I think I'll get out of the > >> way now. > > Kyle> :) I'm OK with this. It was the Lisp directories that I wanted > Kyle> consolidated, for speed. But that looks completely out of the > Kyle> question now, so forget it. > > Well, I'm more guilty of random pointless improvements to the code base > than most, but switching src to use multiple subdirectories strikes me as > really going over the top. Remember that there'll be a Makefile (for me > (!?)) to maintain in each subdirectory. So I veto this initiative. If we could find volunteers to maintain a specific chunk of functionality, then they would of course be responsible for maintaining the Makefile in their subdirectory, unless you were making some very sweeping changes, that would impact every makefile. This happens to me at work once every 6-8 months, and I can usually do it with perl. :) -bp

2 participants
1 comments

[FIX] 21.2 w3 display image -> SIGSEGV 25 years, 3 months

Gunnar Evermann

Norbert Koch <n.koch(a)delta-ii.de> writes: > I've tried to display images on <URL:http://www.debis.de/>. Always > within the third frame (out of four), no matter what order, I get a > SIGSEGV. I've finally tracked this down (after starting to make a local mirror of the debis site with wget :-) The Problem is the following tiny image: NB: I've labeled this as application/octet-stream do avoid pgnus inlining it. If it got inlined for somebody I offer my sincere apologies for the resulting crash :-) If you save it and load it in a vanilla XEmacs you'll probably get a crash. For the experts (Jareth) here are some details: (gdb) p *unwind.giffile $31 = {SWidth = 2, SHeight = 2, SColorResolution = 1, SBackGroundColor = 255, SColorMap = 0x84f0268, ImageCount = 1, Image = {Left = 0, Top = 0, Width = 2, Height = 2, Interlace = 64, ColorMap = 0x0}, SavedImages = 0x853ac48, Private = 0x853e498, GifIO = 0x83b02c8} The problem is the small height and the interlacing (don't ask me why you'd want to interlace a 2 line picture, or what exactly that would mean). The crash is caused by the following code (glyphs-eimage.c:689): ------------- if (interlace) if (row >= height) { row = InterlacedOffset[++pass]; while (row > height) row = InterlacedOffset[++pass]; } eip = unwind.eimage + (row * width * 3); ------------ here 'row' *must* be smaller than 'height' otherwise we overwrite something outside the allocated space (unwind.eimage) later on. Actually the above code looks pretty obviously broken. (no offence, Jareth) :-) But then again this particular gif is probably broken as well (I don't know the specs at all). Somebody who *does* know the specs should check this patch. 1999-01-17 Gunnar Evermann <ge204(a)eng.cam.ac.uk> * glyphs-eimage.c (gif_instantiate): Correct handling of interlaced gifs to avoid writing past the end of the eimage buffer. Index: src/glyphs-eimage.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/glyphs-eimage.c,v retrieving revision 1.3.2.4 diff -u -r1.3.2.4 glyphs-eimage.c --- glyphs-eimage.c 1998/12/05 16:55:52 1.3.2.4 +++ glyphs-eimage.c 1999/01/18 05:58:40 ＠＠ -689,7 +689,7 ＠＠ if (interlace) if (row >= height) { row = InterlacedOffset[++pass]; - while (row > height) + while (row >= height) row = InterlacedOffset[++pass]; } eip = unwind.eimage + (row * width * 3); -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

Deleting broken in Python, or why delete-key-deletes-forward sucks 25 years, 3 months

Hrvoje Niksic

The Python electric deleting feature is totally broken wrt `delete-key-deletes-forward'. I have `delete-key-deletes-forward', but my backspace key generates delete, and I have no backspace key on my keyboard. The standard XEmacs way of recognizing this can look like this: (defsubst delete-forward-p () (and delete-key-deletes-forward (or (not (eq (device-type) 'x)) (x-keysym-on-keyboard-sans-modifiers-p 'backspace)))) This is hard to explain and harder to understand, but that's what compliant code has to do in order to respect the current `delete-key-deletes-forward' mess.

4 participants
4 comments

question about something in the faq. 25 years, 3 months

Alejandro Forero Cuervo

XEmacs FAQ says: > There are currently irreconcilable differences in the views about > technical, programming, design and organizational matters between RMS > the XEmacs development team which provide little hope for a merge to > take place in the short-term future. I am just curious. What are those differences you speak about? I've always seen RMS as a very wise person and I'm just curious. Were can I find info about it? About those differences? :) Thanks. Alejo, --- The goal of Computer Science is to build something that will last at least until we've finished building it.

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 January 1999