SY> Hey there everyone. SY> I have just added the following packages to the 'Pre-Releases' SY> directory: SY> New Packages in Pre-Release: SY> =========================== SY> speedbar-1.21-pkg.tar.gz SY> vm-6.95-pkg.tar.gz SY> zenirc-1.11-pkg.tar.gz Hi Steve, I have installed these three. Minor note: A quick look at *Message-Log* output suggests that quoting of package names should be unified: 15 lines matching package ["`] in buffer *Message-Log*. 948:Retrieving package `speedbar-1.21-pkg.tar.gz' ... 982:Removing old files for package "speedbar" ... 983:Removing old files for package "speedbar" ... done 984:Installing package `speedbar' ... 989:Added package `speedbar' 990:Retrieving package `vm-6.95-pkg.tar.gz' ... 1088:Removing old files for package "vm" ... 1089:Removing old files for package "vm" ... done 1090:Installing package `vm' ... 1095:Added package `vm' 1096:Retrieving package `zenirc-1.11-pkg.tar.gz' ... 1155:Removing old files for package "zenirc" ... 1156:Removing old files for package "zenirc" ... done 1157:Installing package `zenirc' ... 1162:Added package `zenirc' In fact, looking at other messages output to the message log, these message should probably not quote the package at all. We don't plan to allow whitespace in package names, do we? So, I'd propose this format (without quoting by " or ` instead): Retrieving package speedbar-1.21-pkg.tar.gz ... Removing old files for package speedbar ... Removing old files for package speedbar ... done Installing package speedbar ... Added package speedbar Retrieving package vm-6.95-pkg.tar.gz ... Removing old files for package vm ... Removing old files for package vm ... done Installing package vm ... Added package vm Retrieving package zenirc-1.11-pkg.tar.gz ... Removing old files for package zenirc ... Removing old files for package zenirc ... done Installing package zenirc ... Added package zenirc Best regards, Adrian SY> Previously Announced Packages Still in Pre-Release: SY> ================================================== SY> None SY> Detailed Changes: SY> ================ SY> speedbar-1.21-pkg.tar.gz SY> ------------------------ SY> 2001-07-26 Charles G Waldman <cgw(a)xemacs.org&gt; SY> * speedbar.texi: Correct spelling. SY> vm-6.95-pkg.tar.gz SY> ------------------ SY> 2001-07-26 Steve Youngs <youngs(a)xemacs.org&gt; SY> * Sync with VM-6.95. SY> zenirc-1.11-pkg.tar.gz SY> ---------------------- SY> 2001-07-23 Adrian Aichner <adrian(a)xemacs.org&gt; SY> * zenirc.el (zenirc-font-lock-keywords): Include last character SY> before > in fontification of font-lock-keyword-face. Use OVERRIDE SY> flag where appropriate to refine fontification. SY> Installing These: SY> ================ SY> Manually: SY> -------- SY> 1) Download the packages that you want to install from: SY> /ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/ SY> 2) Unpack them to: [1] SY> /usr/local/lib/xemacs/xemacs-packages/ SY> 3) Re-start XEmacs. SY> Using XEmacs Package Tools (XEmacs 21.[245].x): SY> ---------------------------------------------- SY> 1) Tools -> Packages -> Add Download Site -> Pre-Releases SY> 2) Tools -> Packages -> List and Install SY> 3) Select the packages you wish to install (there are brief SY> instructions at the bottom of the packages buffer). SY> 4) Packages -> Install/Remove Selected SY> 5) Re-start XEmacs. SY> Using XEmacs Package Tools (XEmacs 21.1.14): SY> ------------------------------------------- SY> 1) Options -> Manage Packages -> Add Download Site -> Pre-Releases SY> 2) Options -> Manage Packages -> List and Install SY> 3 - 5) As per XEmacs 21.[245].x. SY> Footnotes: SY> [1] Note: Mule packages should be installed into: SY> /usr/local/lib/xemacs/mule-packages/ SY> -- SY> |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| SY> | XEmacs - It's not just an editor. | SY> | It's a way of life. | SY> |------------------------------------&lt;youngs(a)xemacs.org&gt;---| -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

Steve Youngs writes: While I have to agree with you about whitespace in names of functions or variables, I have come to accept whitespace in filenames as a normal part of life. A few space characters in a filename should not present undue difficulties... on the other hand, *newlines* in filenames are really evil! (I've always been rather amazed by the existence of find(1)'s -print0 argument; I wonder who on Earth came up with that one?)

Charles> Steve Youngs writes: APA> We don't plan to allow whitespace in package names, do we? >> It's not something I've thought about, but I'd probably discourage >> it. I think whitespace in filenames/function & variable names is evil >> at the best of times. Charles> While I have to agree with you about whitespace in names Charles> of functions or variables, I have come to accept Charles> whitespace in filenames as a normal part of life. A few Like that :-) Loading c:\Program Files\XEmacs\XEmacs-21.5-b2\etc\sample.init.el...done My point is that above message goes to the message-log without quoting, so package messages should not have quotes around package names either. Perhaps we should instead decide that all file names written to messge-log SHOULD BE surrounded by double-quotes? I see it every that. If only MS succeeded to handle embedded WS in filenames everywhere. They don't! Sometimes you have to double-quote such names, sometimes not. Charles> space characters in a filename should not present undue Charles> difficulties... on the other hand, *newlines* in But the xemacs package system could disallow spaces in package names. Charles> filenames are really evil! (I've always been rather Charles> amazed by the existence of find(1)'s -print0 argument; I Charles> wonder who on Earth came up with that one?) -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

Charles G Waldman <cgw(a)alum.mit.edu&gt; writes: I've seen it attributed to DJ Bernstein. Even if you abhor newlines in file names, you must still allow for files that are created by accidentally (buggy software) or through malice. In such cases `-print0' is extremely useful because with it you *know* that your find/xargs combination will correctly handle all the file names, no matter the weirdness they contain.

|--==> "APA" == Adrian Aichner <adrian(a)xemacs.org&gt; writes: SY> Great. How is zenirc? The previous version gave me problems SY> but I haven't yet checked this one. Don't jump on me, this is SY> exactly what the Pre-Release section is for. APA> It works well, except when zenirc [info] contains single instances of APA> " embedded in escape sequences (for Japanese text). Ok. I discovered that my problem was self-inflicted anyway. APA> We don't plan to allow whitespace in package names, do we? SY> It's not something I've thought about, but I'd probably SY> discourage it. I think whitespace in filenames/function & SY> variable names is evil at the best of times. APA> We should make an official decision one way or the other on that an APA> enforce it by law :-) OFFICIAL DECISION: Anyone found putting whitespace characters in any of the XEmacs Packages' filenames, function names, variable names, macro names etc will be shot on sight! APA> So, I'd propose this format (without quoting by " or ` APA> instead): APA> Retrieving package speedbar-1.21-pkg.tar.gz ... APA> Removing old files for package speedbar ... APA> Removing old files for package speedbar ... done APA> Installing package speedbar ... APA> Added package speedbar SY> I'll support this. Have you got time to do the patch, Adrian? SY> Or should I add it to my own TODO list? APA> Perhaps we should take a step back an as ourselves what the right APA> thing to do is? APA> Take out the quotes here, or add quotes to messages printing path names? Thinking more about it, is it really all that important? It really doesn't bother me whether things in the message buffer are single-quoted, double-quoted, sans-quotes or whatever. And I think that trying to enforce conformity here would be a waste of time and effort. Most of us here would probably toe the line, but not many other people outside our XEmacs family would. Any reason that you can come up with for using a particular convention, somebody else will come up with an equally compelling reason to not conform. Perhaps this particular worm can should stay closed? -- |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|

Steve Youngs writes: these all installed fine on my FreeBSD 4.3 box running 21.4.4 #3 -- ------------------------------------------------------------------------- Peter Brown Web Programmer/Sys Admin/Apache Admin Education Development Web peter(a)edw.com.au www.edw.com.au rendhalver(a)users.sourceforge.net There are only two things that are infinite, the universe and human stupidity, and i am not certain about the former - Albert Einstein -------------------------------------------------------------------------