June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs 21.0-b44/pre1 "Swedish Landrace" is released 27 years

SL Baur

Greg Klanderman <greg(a)alphatech.com> writes: > Hi Barry, > I grabbed libpng 1.0.1 off ftp.uu.net in /graphics/png saturday and > it's working fine... > Steve I've put libpng-1.0.1.tar.gz on altair for you. Why? Is there an advantage of this version over the most recent (1.0.2)?

1 participants
0 comments

Re: TM help playing Ben's attachments 27 years

Hrvoje Niksic

greg(a)alphatech.com (Greg Klanderman) writes: > I got rvplayer and it works, but how do I convince TM to do something > more useful than dump the attachment into a random file in /tmp? > > I'm trying something like > > (push '((type . "audio/x-pn-realaudio") > (method "rvplayer" nil 'file)) > mime/content-decoding-condition) > > but it does not seem to be working. Rvplayer comes up but isn't > playing anything. Is this Rvplayer's fault, perhaps? The last time I tried it, rvplayer didn't support specifying the file to play from the command-line. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- I luv the smell of nature in the morning. Smells like manure!

1 participants
0 comments

Re: toolbar picks up -bg 27 years

Didier Verna

Andy Piper <andyp(a)parallax.co.uk> writes: > Now I understand Kyle's intent a little more clearly. Yes but Kyle's intent is still wrong. > here is a patch to reinstate -bg behaviour. Oh please ! Can't we really agree on something once for all and stop patching this kinda stuff back and forth from realease to release !? How can I make people understand that using -bg and -fg for the widgets as well as for the text is wrong WRONG *WRONG* _WRONG_ _*WRONG*_ !! As soon as you use a 3d layout, widgets *must* have a different appearance by default. How many times did I say so ?! :-( -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

3 participants
2 comments

TM help playing Ben's attachments 27 years

Greg Klanderman

I got rvplayer and it works, but how do I convince TM to do something more useful than dump the attachment into a random file in /tmp? I'm trying something like (push '((type . "audio/x-pn-realaudio") (method "rvplayer" nil 'file)) mime/content-decoding-condition) but it does not seem to be working. Rvplayer comes up but isn't playing anything. greg

1 participants
0 comments

Re: XEmacs 21.0-b44/pre1 "Swedish Landrace" is released 27 years

Greg Klanderman

Hi Barry, I grabbed libpng 1.0.1 off ftp.uu.net in /graphics/png saturday and it's working fine... Steve I've put libpng-1.0.1.tar.gz on altair for you. greg

2 participants
1 comments

Re: XEmacs 21.0-beta43 "Spanish" is released 27 years

Adrian Aichner

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Note to Adrian: Your changes to texinfo.texi bombed. Since the texinfo sb> manuals are out of date (they're based on GNU texinfo-3.11) I went sb> ahead and synched them with the latest versions from texinfo-3.12. Hello Steven, I haven't oticed any major differences between texinfo.texi of b42 and b44. Here is another patch attempt which will hopefully apply to b44. Best, Adrian man/ChangeLog remains the same: 1998-06-10 Adrian Aichner <aichner(a)ecf.teradyne.com> * texinfo.texi: added ../info/ to ＠setfilename, broke line after ＠noindent. Changed ＠var{arg-not-used-by-＠TeX{}} to ＠var{arg-not-used-by-＠＠TeX{}} to make `texinfo-format-buffer' happy. Fixed refs broken by a previous patch of mine. Index: texinfo.texi =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/man/texinfo.texi,v retrieving revision 1.6 diff -u -r1.6 texinfo.texi --- texinfo.texi 1998/06/13 04:28:16 1.6 +++ texinfo.texi 1998/06/16 06:39:41 ＠＠ -3,7 +3,7 ＠＠＠c %**start of header ＠c All text is ignored before the setfilename. -＠setfilename texinfo +＠setfilename ../info/texinfo ＠settitle Texinfo ＠value{edition} ＠c Edition number is now the same as the Texinfo distribution version number. ＠＠ -924,7 +924,7 ＠＠＠TeX{} is freely distributable. It is written in a superset of Pascal called WEB and can be compiled either in Pascal or (by using a conversion program that comes with the ＠TeX{} distribution) in C. -(＠xref{TeX Mode, ,＠TeX{} Mode, emacs, The GNU Emacs Manual}, for information +(＠xref{TeX Mode, ,＠TeX{} Mode, xemacs, XEmacs User's Manual}, for information about ＠TeX{}.)＠refill ＠TeX{} is very powerful and has a great many features. Because a ＠＠ -1561,8 +1561,8 ＠＠ delimiter, you can jump from chapter title to chapter title with the ＠kbd{C-x ]} (＠code{forward-page}) and ＠kbd{C-x [} (＠code{backward-page}) commands and narrow to a chapter with the -＠kbd{C-x p} (＠code{narrow-to-page}) command. (＠xref{Pages, , ,emacs, -The GNU Emacs Manual}, for details about the page commands.)＠refill +＠kbd{C-x p} (＠code{narrow-to-page}) command. (＠xref{Pages, , , xemacs, +XEmacs User's Manual}, for details about the page commands.)＠refill You may name a Texinfo file however you wish, but the convention is to end a Texinfo file name with one of the three extensions ＠＠ -1777,7 +1777,7 ＠＠＠kbd{C-x n n} (＠code{narrow-to-region}) command and ＠code{texinfo-show-structure} will work on only that region. To see the whole buffer again, use ＠w{＠kbd{C-x n w}} (＠code{widen}). -(＠xref{Narrowing, , , emacs, The GNU Emacs Manual}, for more +(＠xref{Narrowing, , , xemacs, XEmacs User's Manual}, for more information about the narrowing commands.)＠refill ＠vindex page-delimiter ＠＠ -1788,7 +1788,7 ＠＠ ]} (＠code{forward-page}) and ＠kbd{C-x [} (＠code{backward-page}) commands to move forward and backward by chapter, and to use the ＠kbd{C-x p} (＠code{narrow-to-page}) command to narrow to a chapter. -＠xref{Pages, , , emacs, The GNU Emacs Manual}, for more information +＠xref{Pages, , , xemacs, XEmacs User's Manual}, for more information about the page commands.＠refill ＠node Updating Nodes and Menus, Info Formatting, Showing the Structure, Texinfo Mode ＠＠ -1975,10 +1975,9 ＠＠ column to which menu descriptions are indented. By default, the value is 32 although it is often useful to reduce it to as low as 24. You can set the variable with the ＠kbd{M-x edit-options} command -(＠pxref{Edit Options, , Editing Variable Values, emacs, The GNU Emacs -Manual}) or with the ＠kbd{M-x set-variable} command (＠pxref{Examining, -, Examining and Setting Variables, emacs, The GNU Emacs -Manual}).＠refill +(＠pxref{Edit Options, , Editing Variable Values, xemacs, XEmacs User's +Manual}) or with the ＠kbd{M-x set-variable} command (＠pxref{Examining, , +Examining and Setting Variables, xemacs, XEmacs User's Manual}).＠refill Also, the ＠code{texinfo-indent-menu-description} command may be used to indent existing menu descriptions to a specified column. Finally, if ＠＠ -6146,26 +6145,30 ＠＠＠＠uref＠{ftp://ftp.gnu.ai.mit.edu/pub/gnu＠} ＠end example -＠noindent produces (in text): +＠noindent +produces (in text): ＠display The official GNU ftp site is ＠uref{ftp://ftp.gnu.ai.mit.edu/pub/gnu} ＠end display -＠noindent whereas +＠noindent +whereas ＠example The official ＠＠uref＠{ftp://ftp.gnu.ai.mit.edu/pub/gnu, GNU ftp site＠} holds programs and texts. ＠end example -＠noindent produces (in text): +＠noindent +produces (in text): ＠display The official ＠uref{ftp://ftp.gnu.ai.mit.edu/pub/gnu, GNU ftp site} holds programs and texts. ＠end display -＠noindent and (in HTML): +＠noindent +and (in HTML): ＠example The official <A HREF="ftp://ftp.gnu.ai.mit.edu/pub/gnu">GNU ftp site</A> holds programs and texts. ＠＠ -6806,7 +6809,8 ＠＠ Send bug reports to ＠＠email＠{bug-texinfo＠＠＠＠gnu.org(a)}. Send suggestions to the ＠＠email＠{bug-texinfo＠＠＠(a)gnu.org, same place＠}. ＠end example -＠noindent produces +＠noindent +produces ＠example Send bug reports to ＠email{bug-texinfo＠(a)gnu.org}. Send suggestions to the ＠email{bug-texinfo＠(a)gnu.org, same place}. ＠＠ -8188,7 +8192,8 ＠＠＠＠multitable ＠＠columnfractions .33 .33 .33 ＠end example -＠noindent The fractions need not add up exactly to 1.0, as these do +＠noindent +The fractions need not add up exactly to 1.0, as these do not. This allows you to produce tables that do not need the full line length. ＠＠ -8229,7 +8234,7 ＠＠ Here is a complete example of a multi-column table (the text is from ＠cite{The GNU Emacs Manual}, ＠pxref{Split Window,, Splitting Windows, -emacs, The GNU Emacs Manual}): +xemacs, XEmacs User's Manual}): ＠example ＠＠multitable ＠＠columnfractions .15 .45 .4 ＠＠ -8249,7 +8254,8 ＠＠＠＠end multitable ＠end example -＠noindent produces: +＠noindent +produces: ＠multitable ＠columnfractions .15 .45 .4 ＠item Key ＠tab Command ＠tab Description ＠＠ -8865,7 +8871,7 ＠＠ The meanings of ＠code{＠＠:} and ＠code{＠(a).}＠: in Texinfo are designed to work well with the Emacs sentence motion commands (＠pxref{Sentences,,, -emacs, The GNU Emacs Manual}). This made it necessary for them to be +xemacs, XEmacs User's Manual}). This made it necessary for them to be incompatible with some other formatting systems that use ＠＠-commands. Do not put braces after any of these commands. ＠＠ -8903,7 +8909,8 ＠＠ example. ＠end example -＠noindent produces +＠noindent +produces ＠example Spacey＠＠＠＠＠＠ -9833,7 +9840,8 ＠＠＠example ＠＠hyphenation＠{man-u-script man-u-scripts＠} ＠end example -＠noindent ＠TeX{} only uses the specified hyphenation points when the +＠noindent +＠TeX{} only uses the specified hyphenation points when the words match exactly, so give all necessary variants. ＠end table ＠＠ -10415,7 +10423,7 ＠＠＠item ＠＠defspec ＠var{name} ＠var{arguments}＠dots{} The ＠code{＠＠defspec} command is the definition command for special forms. (In Lisp, a special form is an entity much like a function, -＠pxref{Special Forms,,, elisp, GNU Emacs Lisp Reference Manual}.) +＠pxref{Special Forms,,, lispref, XEmacs Lisp Reference Manual}.) ＠code{＠＠defspec} is equivalent to ＠samp{＠＠deffn ＠{Special Form＠} ＠dots{}} and works like ＠code{＠＠defun}.(a)refill ＠end table ＠＠ -10502,7 +10510,7 ＠＠＠cindex User options, marking The ＠code{＠＠defopt} command is the definition command for ＠dfn{user options}, i.e., variables intended for users to change according to -taste; Emacs has many such (＠pxref{Variables,,, emacs, The GNU Emacs +taste; Emacs has many such (＠pxref{Variables,,, xemacs, XEmacs User's Manual}). ＠code{＠＠defopt} is equivalent to ＠samp{＠＠defvr ＠{User Option＠} ＠dots{}} and works like ＠code{＠＠defvar}.(a)refill ＠end table ＠＠ -11036,8 +11044,8 ＠＠＠code{＠＠defun} command and it is followed, on the same line, by the parameter list.＠refill -Here is a definition from ＠ref{Calling Functions,,, elisp, The GNU Emacs -Lisp Reference Manual}. +Here is a definition from ＠ref{Calling Functions,,, lispref, XEmacs Lisp +Reference Manual}. ＠quotation ＠defun apply function &rest arguments ＠＠ -11297,9 +11305,9 ＠＠ It can be either ＠samp{"separate"} for the separate node style or ＠samp{"end"} for the end of node style. (You can change the value of this variable with the ＠kbd{M-x edit-options} command (＠pxref{Edit -Options, , Editing Variable Values, emacs, The GNU Emacs Manual}), or +Options, , Editing Variable Values, xemacs, XEmacs User's Manual}), or with the ＠kbd{M-x set-variable} command (＠pxref{Examining, , Examining -and Setting Variables, emacs, The GNU Emacs Manual}).＠refill +and Setting Variables, xemacs, XEmacs User's Manual}).＠refill The ＠code{texinfo-footnote-style} variable also controls the style if you use the ＠kbd{M-x makeinfo-region} or ＠kbd{M-x makeinfo-buffer} ＠＠ -11852,7 +11860,8 ＠＠＠＠＠var{macro-name} ＠{＠var{arg1}, ＠var{arg2}, ＠dots{}＠} ＠end example -＠noindent and the result will be just as if you typed the body of +＠noindent +and the result will be just as if you typed the body of ＠var{macro-name} at that spot. For example: ＠example ＠＠ -11862,7 +11871,8 ＠＠＠＠foo＠{a, b＠} ＠end example -＠noindent produces: +＠noindent +produces: ＠display Together: a & b. ＠＠ -11893,7 +11903,8 ＠＠＠＠bar aah ＠end example -＠noindent produces: +＠noindent +produces: ＠display Twice: aah, aah. ＠＠ -11970,7 +11981,8 ＠＠ tex foo.texi ＠end example -＠noindent ＠TeX{} will produce a ＠dfn{DVI file} as well as several auxiliary +＠noindent +＠TeX{} will produce a ＠dfn{DVI file} as well as several auxiliary files containing information for indices, cross references, etc. The DVI file (for ＠dfn{DeVice Independent} file) can be printed on virtually any printe (see the following sections). ＠＠ -12252,10 +12264,10 ＠＠ You can change the values of these variables with the ＠kbd{M-x edit-options} command (＠pxref{Edit Options, , Editing Variable Values, -emacs, The GNU Emacs Manual}), with the ＠kbd{M-x set-variable} command -(＠pxref{Examining, , Examining and Setting Variables, emacs, The GNU -Emacs Manual}), or with your ＠file{.emacs} initialization file -(＠pxref{Init File, , , emacs, The GNU Emacs Manual}).＠refill +xemacs, XEmacs User's Manual}), with the ＠kbd{M-x set-variable} command +(＠pxref{Examining, , Examining and Setting Variables, xemacs, XEmacs +User's Manual}), or with your ＠file{.emacs} initialization file +(＠pxref{Init File, , , xemacs, XEmacs User's Manual}).＠refill ＠node Compile-Command, Requirements Summary, Texinfo Mode Printing, Format/Print Hardcopy ＠comment node-name, next, previous, up ＠＠ -12283,7 +12295,7 ＠＠＠noindent This technique is most often used by programmers who also compile programs -this way; see ＠ref{Compilation, , , emacs, The GNU Emacs Manual}.＠refill +this way; see ＠ref{Compilation, , , xemacs, XEmacs User's Manual}.＠refill ＠node Requirements Summary, Preparing for TeX, Compile-Command, Format/Print Hardcopy ＠＠ -12298,7 +12310,7 ＠＠＠example \input texinfo -＠＠setfilename ＠var{arg-not-used-by-＠TeX{}} +＠＠setfilename ＠var{arg-not-used-by-＠＠TeX{}} ＠end example ＠noindent ＠＠ -12948,7 +12960,7 ＠＠ (＠code{next-error}). This causes Emacs to go to and position the cursor on the line in the Texinfo source that ＠code{makeinfo} thinks caused the error. ＠xref{Compilation, , Running ＠code{make} or -Compilers Generally, emacs, The GNU Emacs Manual}, for more +Compilers Generally, xemacs, XEmacs User's Manual}, for more information about using the ＠code{next-error} command.＠refill In addition, you can kill the shell in which the ＠code{makeinfo} ＠＠ -13000,9 +13012,9 ＠＠＠noindent ＠ifinfo For more information, see＠* -＠ref{Edit Options, , Editing Variable Values, emacs, The GNU Emacs Manual},＠* -＠ref{Examining, , Examining and Setting Variables, emacs, The GNU Emacs Manual},＠* -＠ref{Init File, , , emacs, The GNU Emacs Manual}, and＠* +＠ref{Edit Options, , Editing Variable Values, xemacs, XEmacs User's Manual},＠* +＠ref{Examining, , Examining and Setting Variables, xemacs, XEmacs User's Manual},＠* +＠ref{Init File, , , xemacs, XEmacs User's Manual}, and＠* ＠ref{makeinfo options, , Options for ＠code{makeinfo}}. ＠end ifinfo ＠＠ -13052,7 +13064,7 ＠＠ You can format Texinfo files for Info using ＠code{batch-texinfo-format} and Emacs Batch mode. You can run Emacs in Batch mode from any shell, including a shell inside of Emacs. (＠xref{Command Switches, , Command -Line Switches and Arguments, emacs, The GNU Emacs Manual}.)＠refill +Line Switches and Arguments, xemacs, XEmacs User's Manual}.)＠refill Here is a shell command to format all the files that end in ＠file{.texinfo} in the current directory: ＠＠ -13099,7 +13111,7 ＠＠ files were always kept short and ＠dfn{include files} were designed as a way to create a single, large printed manual out of the smaller Info files. ＠xref{Include Files}, for more information. Include files are -still used for very large documents, such as ＠cite{The Emacs Lisp +still used for very large documents, such as ＠cite{The XEmacs Lisp Reference Manual}, in which each chapter is a separate file.)＠refill When a file is split, Info itself makes use of a shortened version of ＠＠ -15135,7 +15147,7 ＠＠ Also, if you are writing a manual about software, you should explain that the software is free and either include the GNU General Public License (GPL) or provide a reference to it. ＠xref{Distrib, , -Distribution, emacs, The GNU Emacs Manual}, for an example of the text +Distribution, xemacs, XEmacs User's Manual}, for an example of the text that could be used in the software ``Distribution'', ``General Public License'', and ``NO WARRANTY'' sections of a document. ＠xref{Copying, , Texinfo Copying Conditions}, for an example of a brief explanation ＠＠ -15511,7 +15523,7 ＠＠＠end group ＠end example -The outer Texinfo source file for ＠cite{The GNU Emacs Lisp Reference +The outer Texinfo source file for ＠cite{The XEmacs Lisp Reference Manual} is named ＠file{elisp.texi}. This outer file contains a master menu with 417 entries and a list of 41 ＠code{＠＠include} files.＠refill ＠＠ -15546,7 +15558,7 ＠＠ no longer necessary to keep them small.＠refill Nowadays, multiple Texinfo files are used mostly for large documents, -such as ＠cite{The GNU Emacs Lisp Reference Manual}, and for projects +such as ＠cite{The XEmacs Lisp Reference Manual}, and for projects in which several different people write different sections of a document simultaneously.＠refill ＠＠ -16106,8 +16118,8 ＠＠＠code{re-search-forward} was called; it was this function that could not find the missing right-hand brace.＠refill -＠xref{Lisp Debug, , Debugging Emacs Lisp, emacs, The GNU Emacs -Manual}, for more information.＠refill +＠xref{Lisp Debug, , Debugging Emacs Lisp, xemacs, XEmacs User's Manual}, +for more information.＠refill ＠end ignore ＠node Debugging with TeX, Using texinfo-show-structure, Debugging with Info, Catching Mistakes ＠＠ -16286,20 +16298,20 ＠＠ window, you can position the cursor over one of the lines and use the ＠kbd{C-c C-c} command (＠code{occur-mode-goto-occurrence}), to jump to the corresponding spot in the Texinfo file. ＠xref{Other Repeating -Search, , Using Occur, emacs, The GNU Emacs Manual}, for more +Search, , Using Occur, xemacs, XEmacs User's Manual}, for more information about ＠code{occur-mode-goto-occurrence}.＠refill The first line in the ＠samp{*Occur*} window describes the ＠dfn{regular expression} specified by ＠var{texinfo-heading-pattern}. This regular expression is the pattern that ＠code{texinfo-show-structure} looks for. -＠xref{Regexps, , Using Regular Expressions, emacs, The GNU Emacs Manual}, +＠xref{Regexps, , Using Regular Expressions, xemacs, XEmacs User's Manual}, for more information.＠refill When you invoke the ＠code{texinfo-show-structure} command, Emacs will display the structure of the whole buffer. If you want to see the structure of just a part of the buffer, of one chapter, for example, use the ＠kbd{C-x n n} (＠code{narrow-to-region}) command to mark the -region. (＠xref{Narrowing, , , emacs, The GNU Emacs Manual}.) This is +region. (＠xref{Narrowing, , , xemacs, XEmacs User's Manual}.) This is how the example used above was generated. (To see the whole buffer again, use ＠kbd{C-x n w} (＠code{widen}).)＠refill ＠＠ -16331,10 +16343,10 ＠＠＠noindent and then, when prompted, type a ＠dfn{regexp}, a regular expression for the pattern you want to match. (＠xref{Regexps, , Regular Expressions, -emacs, The GNU Emacs Manual}.) The ＠code{occur} command works from -the current location of the cursor in the buffer to the end of the -buffer. If you want to run ＠code{occur} on the whole buffer, place -the cursor at the beginning of the buffer.＠refill +xemacs, XEmacs User's Manual}.) The ＠code{occur} command works from the +current location of the cursor in the buffer to the end of the buffer. +If you want to run ＠code{occur} on the whole buffer, place the cursor at +the beginning of the buffer.＠refill For example, to see all the lines that contain the word ＠samp{＠＠chapter} in them, just type ＠samp{＠＠chapter}. This will ＠＠ -16349,7 +16361,7 ＠＠ all the nodes that are part of the same chapter or section and therefore have the same `Up' pointer.＠refill -＠xref{Other Repeating Search, , Using Occur, emacs , The GNU Emacs Manual}, +＠xref{Other Repeating Search, , Using Occur, xemacs, XEmacs User's Manual}, for more information.＠refill ＠node Running Info-Validate, , Using occur, Catching Mistakes ＠＠ -16758,7 +16770,8 ＠＠＠end group ＠end display -＠noindent Please make checks payable to the University of Washington. +＠noindent +Please make checks payable to the University of Washington. Checks must be in U.S.＠: dollars, drawn on a U.S.＠: bank. Overseas sites: please add to the base cost, if desired, $20.00 for shipment via air parcel post, or $30.00 for shipment via courier. -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Re: -batch loads site-start.el 27 years

SL Baur

Glynn Clements <glynn(a)sensei.co.uk> writes: > Is `xemacs -batch' supposed to load site-start.el? Yes. It's a deliberate feature. > This caused a (minor) problem when building, due to an error in my > site-start.el file (expecting emacs-beta-version to be an integer). > It would seem (to me) more logical for -batch to imply -vanilla. -batch implies -q. Stuff loaded and actions performed by site-start.el are equal in effect to things dumped with the XEmacs binary. The strongest argument against making this change is that it could cause a great deal of breakage to people with scripts using XEmacs -batch.

1 participants
0 comments

Re: dark background, unreadable modeline 27 years

Hrvoje Niksic

This is the result of Kyle's controversial color policy. Not only will jwz bitch, but so will our other users (basically anyone who uses a dark background, which I suspect is quite a lot), *including* people on xemacs-beta, including myself. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Then... his face does a complete change of expression. It goes from a "Vengeance is mine" expression, to a "What the fuck" blank look.

2 participants
1 comments

[OK] 21.0 "Swedish Landrace" XEmacs Lucid on sparc-sun-solaris2.5.1 27 years

Raymond Toy

Looks good so far. No surprises, except I had to rearrange my .emacs to load stuff from my .xemacs directory, as expected. Ray > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /apps/public/XEmacs/Beta/src/xemacs-21.0-b44/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: [PATCH] TM usability enhancements 27 years

Hrvoje Niksic

Darryl Okahata <darrylo(a)sr.hp.com> writes: > However, your idea of dynamically determining the type based upon > file contents in an excellent suggestion (and would also solve the > current .diff/.patch dichotomy). I think it is the wrong thing to do. Encoding should be based upon the file contents in the sense of the presence of 8bit chars, etc. Type should be based on the semantics of the file. For example, postscript files (the output of automatic converters) would not make much sense as text/plain, because they are not human-readable, in spite of being 7bit. Patch files *should* be text/plain, because they *are* meant to be read by humans (especially in the context of xemacs-patches), even if they contain 8bit chars. In both of these cases, the issues of type and encoding are orthogonal, except for the charset matter, as pointed out by Kyle. The file extension may provide a good estimate of the file type, while examining its contents allows us to choose the optimal encoding. Please let's not "fix" what is not broken by confusing the two. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Reporter: Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.

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 June 1998