March 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Compile error 21.0.67 on X11R6.4 and SunOS4.1.3_U1 26 years, 1 month

Atsushi Kuroda

I had compilation errors on X11R6.4 and SunOS4.1.3_U1. Do I need any 'locale' package in my env.? Thank you very much for your information. Configuration is: export LANG=C ./configure --prefix=/export/scratch --with-mule --with-canna --with-xpm --with-gcc --with-xim The error message is: make[1]: Entering directory `/export/home1/scratch/kuroda/src/xemacs-21.0.67/src' EMACSBOOTSTRAPLOADPATH="/export/home1/scratch/kuroda/src/xemacs-21.0.67/src/../lisp/:/export/home1/scratch/kuroda/src/xemacs-21.0.67" ./temacs -batch -l /export/home1/scratch/kuroda/src/xemacs-21.0.67/src/../lisp/update-elc.el Loading /export/home1/scratch/kuroda/src/xemacs-21.0.67/src/../lisp/update-elc.el... Loading very-early-lisp... (1684) Loading find-paths.el... (10464) Loading packages.el... (18780) Loading setup-paths.el... (4096) Loading dump-paths.el... (0) Loading /export/home1/scratch/kuroda/src/xemacs-21.0.67/src/../lisp/dumped-lisp.el... (96) make[1]: Leaving directory `/export/home1/scratch/kuroda/src/xemacs-21.0.67/src' MAKE='make' EMACS='./src/xemacs' sh /export/home1/scratch/kuroda/src/xemacs-21.0.67/lib-src/update-elc.sh (using ./src/xemacs) Recompiling in /export/home1/scratch/kuroda/src/xemacs-21.0.67 with /export/home1/scratch/kuroda/src/xemacs-21.0.67/src/xemacs... X Windows does not support locale `C' Using C Locale instead X Windows does not even support locale `C'! Cleaning out of date .elcs in directory `lisp'... Cleaning out of date .elcs in directory `lisp'...done Deleting .elc files without .el files...done. Checking for Mule support...X Windows does not support locale `C' Using C Locale instead X Windows does not even support locale `C'! Yes Compiling files without .elc... Compiling files without .elc... Done ****************************************************************** It also has runtime error ****************************************************************** > ./xemacs X Windows does not support locale `C' Using C Locale instead X Windows does not even support locale `C'! Warning: Cannot allocate colormap entry for "Maroon" Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. 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 /export/home1/scratch/kuroda/src/xemacs-21.0.67/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: # bind (frame-being-created) make-frame(nil #<x-device on ":0.0" 0x8d9>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Segmentation fault (core dumped) ----------------------------------------------------------------- Atsushi Kuroda (kuroda＠tkitdsn1.eq.gs.com,atsushi.kuroda(a)gs.com) Client Service Technology (5563-7463) Goldman Sachs (Japan) Ltd. -----------------------------------------------------------------

1 participants
0 comments

Re: UW imap c-client 26 years, 1 month

Joshua R. Poulson

>The main bottleneck in nnimap/gnus right now is imho that it takes a >long time to check for new mail. No other imap clients I've tested >does this at all, so perhaps we can make that part optional. (It can >also be made faster by using a different strategy). OE4&5 check for mail in all subscribed folders. They do it radically faster than nnimap does. >The major bottleneck would then be that it takes a long time to enter >a folder, this is impossible to fix without heavy modifications of >Gnus, and for me this isn't a major problem anyway (entering a folder >with ~1200 articles takes ~25 seconds with 9s spent in nnimap for >me. I can live with that). OE4&5 gain speed advantages on this by caching the headers. >Do you agree with my observations of where the bottlenecks are? Which >things in nnimap are slow for you? The slowest/hardest thing for me is finding an old email. ;) --jrp

1 participants
0 comments

Re: converting files to installable package format? 26 years, 1 month

Adrian Aichner

>>>>> "jari" == jari aalto <jari.aalto(a)poboxes.com> writes: jari> I started experimenting with XEmacs packaging system and jari> before I convert my modules to this I'd like to know If jari> I'm on right tracks: See Info, XEmacs, Packages. jari> _pkg Seems pretty straightforward auto-generated jari> auto-autoloads.el Seesm to contain generate-file-autoloads auto-generated jari> cust-load.el Seems to be generated by ?? auto-generated (if sources contain (defcustom ...) BTW: it's called custom-load.el). To build a simple package you need at least these files: d:\el\xemacs-packages: total 128 drwxrwxrwx 2 AichnerAd 5 0 Mar 26 11:06 . drwxrwxrwx 2 AichnerAd 5 0 Mar 26 11:06 .. drwxrwxrwx 2 AichnerAd 5 0 Mar 25 23:59 comm -rw-rw-rw- 1 AichnerAd 5 2541 Mar 16 21:11 hack-package-index.el -rw-rw-rw- 1 AichnerAd 5 1620 Mar 16 21:05 Makefile -rw-rw-rw- 1 AichnerAd 5 5713 Mar 16 21:11 package-compile.el -rw-rw-rw- 1 AichnerAd 5 12424 Mar 26 00:07 XEmacs.rules d:\el\xemacs-packages\comm: total 24 drwxrwxrwx 2 AichnerAd 5 0 Mar 25 23:59 . drwxrwxrwx 2 AichnerAd 5 0 Mar 25 23:59 .. drwxrwxrwx 2 AichnerAd 5 0 Mar 26 12:06 bat-mode -rw-rw-rw- 1 AichnerAd 5 1754 Mar 25 23:59 Makefile d:\el\xemacs-packages\comm\bat-mode: total 16 drwxrwxrwx 2 AichnerAd 5 0 Mar 26 12:06 . drwxrwxrwx 2 AichnerAd 5 0 Mar 26 12:06 .. -rw-rw-rw- 1 AichnerAd 5 3950 Mar 26 11:03 bat-mode.el -rw-rw-rw- 1 AichnerAd 5 91 Mar 26 00:11 ChangeLog -rw-rw-rw- 1 AichnerAd 5 1167 Mar 26 11:05 Makefile -rw-rw-rw- 1 AichnerAd 5 402 Mar 25 21:59 package-info.in jari> Are these the only files that are needed to put in jari> PACKAGE-VER.tar.gz? When PACKAGE-VER.tar.gz is ready jari> where should it be put available? See staging in XEmacs.rules file. jari> Q. How do I classify the the "type" (I'm using the jari> footnote-el as an example) Read info docs on XEmacs, Packages jari> ;;;###autoload jari> (package-provide 'footnote jari> :version 1.09 jari> :type 'regular) jari> Q. Where do I send the package-get-base entry, like the one jari> in footnote.el It goes into the staging directory as well. jari> (footnote jari> (standards-version 1.0 jari> version "1.06" jari> author-version "0.18x" jari> date "1998-08-27" jari> build-date "1998-09-19" jari> maintainer "SL Baur <steve(a)xemacs.org>" jari> distribution stable jari> priority low jari> category "comm" jari> dump nil jari> description "Footnoting in mail message editing modes." jari> filename "footnote-1.06-pkg.tar.gz" jari> md5sum "796323a84d97bade70a5d78fd9076a2e" jari> size 13551 jari> provides (footnote) jari> requires (mail-lib xemacs-base) jari> type regular jari> )) jari> What's priority? How to choose Category value? Don't know. jari> Q. What if a MODULE consists of several files, say jari> xxx-file1.el xxx-file2.el? If they're all necessary to provide MODULE, then it's a regular package. jari> jari Make sure you also get hack-package-index.el from xemacs-packages CVS sources. I had trouble checking it out. I am building all my packages from within a native Windows NT MULE Xemacs using M-x compile RET make --unix bindist RET I have Cygnus Development Tools installed to get GNU make, bash, etc. I had to change quoting in XEmacs.rules and Makefile, e.g. from $(AUTOLOAD_PATH)/auto-autoloads.el : $(ELCS:.elc=.el) $(AUTOLOAD_PATH)/_pkg.el $(XEMACS) $(VANILLA) -batch \ -eval "(setq autoload-package-name \"$(PACKAGE)\")" \ -l autoload -f batch-update-directory $(AUTOLOAD_PATH) ＠rm -f $(AUTOLOAD_PATH)/auto-autoloads.el~ to $(AUTOLOAD_PATH)/auto-autoloads.el : $(ELCS:.elc=.el) $(AUTOLOAD_PATH)/_pkg.el $(XEMACS) $(VANILLA) -batch \ -eval "(setq autoload-package-name \\\"$(PACKAGE)\\\")" \ -l autoload -f batch-update-directory $(AUTOLOAD_PATH) ＠rm -f $(AUTOLOAD_PATH)/auto-autoloads.el~ HTH, Adrian -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: pop3.el - treating "From " at the beginning of lines 26 years, 1 month

Dmitry Yaitskov

Dmitry Yaitskov <dimas(a)home.com> wrote: <snip-snip> Oops. Sorry about the followup to my own post. Here is a somewhat better variant: ----------------------------cut here------------------------------- --- e:\bin\XEmacs\xemacs-packages\lisp\mail-lib\pop3.el Mon Mar 08 22:36:12 1999 +++ pop3.el Mon Mar 29 15:22:04 1999 ＠＠ -310,12 +310,18 ＠＠ (defun pop3-clean-region (start end) "Convert MS-DOG style line endings to normal line endings. -Also remove '.' from the beginning of lines." +Also remove '.' from the beginning of lines. +Also escape 'From ' at the beginning of lines with '>'." (setq end (set-marker (make-marker) end)) (save-excursion (goto-char start) (while (and (< (point) end) (search-forward "\r\n" end t)) (replace-match "\n" t t)) + ;; Escape "\n\nFrom " (for mbox). + (goto-char start) + (while (re-search-forward "\n\n\$From \$" end t) + (replace-match "\n\n>\\1" t nil)) + ;; (goto-char start) (while (and (< (point) end) (re-search-forward "^\\." end t)) (replace-match "" t t) ----------------------------cut here------------------------------- -- Cheers, -Dima.

1 participants
0 comments

converting files to installable package format? 26 years, 1 month

Jari Aalto

I started experimenting with XEmacs packaging system and before I convert my modules to this I'd like to know If I'm on right tracks: _pkg Seems pretty straightforward auto-autoloads.el Seesm to contain generate-file-autoloads cust-load.el Seems to be generated by ?? Are these the only files that are needed to put in PACKAGE-VER.tar.gz? When PACKAGE-VER.tar.gz is ready where should it be put available? Q. How do I classify the the "type" (I'm using the footnote-el as an example) ;;;###autoload (package-provide 'footnote :version 1.09 :type 'regular) Q. Where do I send the package-get-base entry, like the one in footnote.el (footnote (standards-version 1.0 version "1.06" author-version "0.18x" date "1998-08-27" build-date "1998-09-19" maintainer "SL Baur <steve(a)xemacs.org>" distribution stable priority low category "comm" dump nil description "Footnoting in mail message editing modes." filename "footnote-1.06-pkg.tar.gz" md5sum "796323a84d97bade70a5d78fd9076a2e" size 13551 provides (footnote) requires (mail-lib xemacs-base) type regular )) What's priority? How to choose Category value? Q. What if a MODULE consists of several files, say xxx-file1.el xxx-file2.el? jari

1 participants
0 comments

Re: UW imap c-client 26 years, 1 month

Simon Josefsson

Mark Moll <mmoll(a)cs.cmu.edu> writes: > I have used both nnimap 0.95 and Pine 4.10. Although nnimap is quite usable, > the speed difference between nnimap and Pine is *huge*. I agree with John, this wouldn't win us that much speed. The speed difference between pine/gnus is because of the very different design decisions. > I was wondering if anybody has looked at using Pine's imap back-end, > c-client. I'm not a real xemacs wizard, but I can imagine that this > c-client library can be plugged into xemacs 21.2 as a module. Would > this be a good idea? Probably not, the imap parser isn't the bottleneck so replacing that wouldn't improve much. The main bottleneck in nnimap/gnus right now is imho that it takes a long time to check for new mail. No other imap clients I've tested does this at all, so perhaps we can make that part optional. (It can also be made faster by using a different strategy). The major bottleneck would then be that it takes a long time to enter a folder, this is impossible to fix without heavy modifications of Gnus, and for me this isn't a major problem anyway (entering a folder with ~1200 articles takes ~25 seconds with 9s spent in nnimap for me. I can live with that). Do you agree with my observations of where the bottlenecks are? Which things in nnimap are slow for you?

1 participants
0 comments

pop3.el - treating "From " at the beginning of lines 26 years, 1 month

Dmitry Yaitskov

Hi, With XEmacs 21.2 \"Demeter\" [Lucid] (i586-pc-win32), pop3.el Version: 2.03 from the latest(?) mail-lib package, I had the following problem. In my setup, pgnus .80 reads mail from pop3, using pop3-movemail from mail-lib package's pop3.el. A message came in containing the following lines in its body: ---start qote--- |might want to try it and see how it fares. It's an 80KB download. | |From that webpage: |"Features: ---end qote--- The line starting with 'From' was interpreted by gnus as the start of a new message (which is AFAIK indeed that in mbox format) resulting in mail screwup (and loss). Below is my fix for pop3.el. I am *not* sure I put it in the right place, although it seems to work. People more knowledgeable about this code are welcome to fix the fix. The problem is real though. ----------------------------cut here------------------------------- --- e:\bin\XEmacs\xemacs-packages\lisp\mail-lib\pop3.el Mon Mar 08 22:36:12 1999 +++ pop3.el Mon Mar 29 12:39:59 1999 ＠＠ -310,9 +310,17 ＠＠ (defun pop3-clean-region (start end) "Convert MS-DOG style line endings to normal line endings. -Also remove '.' from the beginning of lines." +Also remove '.' from the beginning of lines. +Also escape 'From ' at the beginning of lines with '>'." (setq end (set-marker (make-marker) end)) (save-excursion + ;; unix mbox format treats "^From " as message start. Escape it. + (goto-char start) + (while (re-search-forward "^From " end t) + (progn + (goto-char (match-beginning 0)) + (insert ">"))) + ;; (goto-char start) (while (and (< (point) end) (search-forward "\r\n" end t)) (replace-match "\n" t t)) ----------------------------cut here------------------------------- -- Cheers, -Dima.

1 participants
0 comments

Re: UW imap c-client 26 years, 1 month

William M. Perry

Mark Moll <mmoll(a)cs.cmu.edu> writes: > I have used both nnimap 0.95 and Pine 4.10. Although nnimap is quite > usable, the speed difference between nnimap and Pine is *huge*. I was > wondering if anybody has looked at using Pine's imap back-end, > c-client. I'm not a real xemacs wizard, but I can imagine that this > c-client library can be plugged into xemacs 21.2 as a module. Would this > be a good idea? A first pass of this could be to try and use a c-client based stub program in a subprocess. The nice thing about having all the nnimap stuff done in lisp is that things like my socks.el library or ssl.el can be used as well to modify how the connection is made. -Bill P.

1 participants
0 comments

Re: UW imap c-client 26 years, 1 month

John Prevost

Mark Moll <mmoll(a)cs.cmu.edu> writes: > I have used both nnimap 0.95 and Pine 4.10. Although nnimap is quite usable, > the speed difference between nnimap and Pine is *huge*. I was wondering if > anybody has looked at using Pine's imap back-end, c-client. I'm not a real > xemacs wizard, but I can imagine that this c-client library can be plugged > into xemacs 21.2 as a module. Would this be a good idea? I'm very dubious as to the effectiveness of this. The only win would be on message parsing speed. I expect c-client would be able to do a bit better of a job than emacs at this, but in my experience, it's not that great. Where pine really wins is not in using c-client per se, but in using "virtual scrollbars". It only fetches the headers for the page you're looking at now rather than all of the pages of header info. Take a look at mutt for an example of a curses-based imap reader that doesn't do this. Take a look at various c-client based X clients to see how not to use c-client successfully for this purpose. Finally, it's been my experience that c-client is more than a bit on the ugly side. If this imap-parsing-speaking tool were to be written, it'd probably be better to write something from scratch that talks IMAP on one end and elisp on the other, rather than basing on c-client. John.

1 participants
0 comments

Re: image-mode and format-alist 26 years, 1 month

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > I think image-mode is hacking into the file reading code at too low > a level. The image-mode mode stuff ought to be removed from > format-alist. You have my blessing. I fought for the same thing. Not to mention that the image mode is broken in other ways (such as not allowing me to normally edit an XPM -- I had to use vi for that!)

2 participants
1 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 March 1999