Re: Coding system sniffing.
17 years, 6 months
Joachim Schrod
Joachim Schrod
Stephen J. Turnbull wrote:
> Aidan Kehoe writes:
>
> > Reliably differentiating those [bit-for-bit identical] pairs
> > without metadata is not possible.
>
> And unnecessary, precisely because it's not possible. It's only when
> you add disambiguating text that it matters, and then the Sufficiently
> Smart Program argument applies.
I hate to disturb your conversation -- but I want to add the voice
of one European (German) user: Aidan expresses the problem, and you
seem to reject work on it to get a Really Good Design. But it ain't
so easy, from this user's perspective -- sometimes Worse Is Better,
as we all have learned from Dick Gabriel.
It is highly annoying that I need to explicitly, manually, specify
the buffer-coding-system for a file when I want to insert an EUR
sign and when I want it to end up encoded in ISO-8859-15. And
that's the current state of affairs, AFAICS.
Since many of us use templates for new files anyhow, it's a small
matter to add an appropriate cookie to demand a specific encoding
for a file. That this approach is effectively rejected by you, is
really disturbing for us European users. Maybe one doesn't need it
for Japanese scripts and for UTF-8, but for us poor souls who still
want to use ISO-8859-* for other reasons, it would be a real advantage.
Well, speaking of UTF-8: Since XEmacs is very happy to destroy lots
of my files with its supposedly smart encoding detection -- and
does so WITHOUT any warning -- your demand for more thought about
error recovery is right on spot. But there seems to be other areas
that are in more severe need of that error handling than recovery
from wrong coding cookies (namely, automatic encoding sniffing). I
have had literally dozens of UTF-8 files with one single Latin1
char in them, that got reencoded by XEmacs when I opened and saved
them. (I.e., when I didn't pay enough attention to the modeline in
the process of quickly modifying one or two words.) In all these
cases, reliance on a user-supplied coding cookie would have saved
me untold hours and hours of work to redo the result of XEmacs
automatic encoding detection which Really Really Really Sucks.
Throwing an error if the coding system is not sufficient is much
preferred to the current state of affairs (arbitrarily choosing a
coding system that XEmacs thinks is right).
Sorry about sounding frustrated -- but I am, and your insistence on
Sufficiently Smart Programs(tm) being the Right Way(tm) does not
match my experience with XEmacs, or with programs at all. Please
let us have our way to specify "yes, I want the buffer of this file
in THIS coding system and be DAMNED if you try to switch on another
one beneath my back. I know what I'm doing because I'M THE USER and
I'M ALWAYS RIGHT BY DEFINITION because I know more about MY OWN
FILES than you bloody stupid detection algorithm."
Please.
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: jschrod(a)acm.org
Roedermark, Germany
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 3 participants
- 3 comments
[Bug: 21.4.13] emacs crashed when closing with unsaved file
17 years, 6 months
Itamar Glatzer
Itamar Glatzer
================================================================
Dear Bug Team!
I tryed to close my emacs when there was unsaved file. A GUI massage
appeared asking me if I want to save the file (as always in this
case). I pressed on the 'x' bottom in the top of the GUI and then the
emaxs has crashed.
The core file is attached
================================================================
System Info to help track down your bug:
---------------------------------------
uname -a: Linux E180 2.6.0-test3 #1 Fri Jul 11 20:16:51 UTC 2003 i686 athlon i386 GNU/Linux
./configure 'i386-suse-linux' '--with-gcc' '--dynamic' '--rel-alloc' '--debug=no' '--error-checking=none' '--cflags=-O2 -march=i586 -mcpu=i686 -fmessage-length=0 -Wall -Wno-switch -pipe -O2 -march=i586 -mcpu=i686 -fmessage-length=0' '--ldflags=-s -znocombreloc' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/X11R6/bin' '--datadir=/usr/share' '--archlibdir=/usr/lib/xemacs/21.4.13/i386-suse-linux' '--docdir=/usr/lib/xemacs/21.4.13/i386-suse-linux' '--lispdir=/usr/share/xemacs/21.4.13/lisp' '--pkgdir=/usr/share/xemacs/21.4.13/lisp' '--etcdir=/usr/share/xemacs/21.4.13/etc' '--statedir=/var/lib/xemacs' '--moduledir=/usr/lib/xemacs/21.4.13/i386-suse-linux/modules' '--infodir=/usr/share/xemacs/info' '--mandir=/usr/share/man/man1' '--with-sound=native' '--with-database=gnudbm,berkdb' '--with-ncurses' '--with-tty=yes' '--with-gpm' '--with-site-lisp' '--pdump' '--with-xpm' '--with-gif' '--with-tiff' '--with-jpeg' '--with-png' '--with-x' '--with-athena=3d' '--with-menubars=lucid' '
--with-scrollbars=lucid' '--with-dialogs=athena' '--with-widgets=athena' '--x-includes=/usr/X11R6/include' '--x-libraries=/usr/X11R6/lib' '--with-mule' '--with-xim=xlib' '--with-xfs' '--with-clash-detection' '--with-ldap' '--with-pop'
XEmacs 21.4.13 "Rational FORTRAN" configured for `i386-suse-linux'.
Compilation / Installation:
Source code location: /usr/src/packages/BUILD/xemacs-21.4.13
Installation prefix: /usr
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -Wall -Wno-switch -pipe -O2 -march=i586 -mcpu=i686 -fmessage-length=0
Relocating allocator for buffers: yes
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.
Compiling in support for GPM (General Purpose Mouse).
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.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
Compiling in support for GNU DBM.
Compiling in support for LDAP.
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 POP mail retrieval.
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new portable dumper.
Load-Path Lisp Shadows:
----------------------
(/usr/share/xemacs/site-packages/lisp/flim/std11
/usr/share/xemacs/xemacs-packages/lisp/apel/std11
~/my-lisp/ecb/tree-buffer
/usr/share/xemacs/xemacs-packages/lisp/ecb/tree-buffer
~/my-lisp/ecb/silentcomp
/usr/share/xemacs/xemacs-packages/lisp/ecb/silentcomp
~/my-lisp/ecb/ecb /usr/share/xemacs/xemacs-packages/lisp/ecb/ecb
~/my-lisp/ecb/ecb-util
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-util
~/my-lisp/ecb/ecb-upgrade
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-upgrade
~/my-lisp/ecb/ecb-tod
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-tod
~/my-lisp/ecb/ecb-speedbar
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-speedbar
~/my-lisp/ecb/ecb-navigate
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-navigate
~/my-lisp/ecb/ecb-layout
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-layout
~/my-lisp/ecb/ecb-mode-line
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-mode-line
~/my-lisp/ecb/ecb-jde
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-jde
~/my-lisp/ecb/ecb-help
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-help
~/my-lisp/ecb/ecb-face
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-face
~/my-lisp/ecb/ecb-examples
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-examples
~/my-lisp/ecb/ecb-eshell
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-eshell
~/my-lisp/ecb/ecb-cycle
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-cycle
~/my-lisp/ecb/ecb-layout-defs
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-layout-defs
~/my-lisp/ecb/ecb-compilation
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-compilation
~/my-lisp/ecb/ecb-autogen
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-autogen
~/my-lisp/ecb/ecb-create-layout
/usr/share/xemacs/xemacs-packages/lisp/ecb/ecb-create-layout
/usr/share/xemacs/site-packages/lisp/flim/sha1
/usr/share/xemacs/xemacs-packages/lisp/ecrypto/sha1
/usr/share/xemacs/site-packages/lisp/flim/sha1-el
/usr/share/xemacs/xemacs-packages/lisp/ecrypto/sha1-el
/usr/share/xemacs/site-packages/lisp/flim/md5
/usr/share/xemacs/xemacs-packages/lisp/ecrypto/md5
/usr/share/xemacs/site-packages/lisp/flim/md4
/usr/share/xemacs/xemacs-packages/lisp/ecrypto/md4
/usr/share/xemacs/site-packages/lisp/flim/hex-util
/usr/share/xemacs/xemacs-packages/lisp/ecrypto/hex-util
~/my-lisp/eieio/tree /usr/share/xemacs/xemacs-packages/lisp/eieio/tree
~/my-lisp/eieio/linemark
/usr/share/xemacs/xemacs-packages/lisp/eieio/linemark
~/my-lisp/eieio/eieio
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio
~/my-lisp/eieio/eieio-tests
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio-tests
~/my-lisp/eieio/eieio-opt
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio-opt
~/my-lisp/eieio/eieio-doc
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio-doc
~/my-lisp/eieio/eieio-custom
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio-custom
~/my-lisp/eieio/eieio-comp
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio-comp
~/my-lisp/eieio/eieio-base
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio-base
~/my-lisp/eieio/chart
/usr/share/xemacs/xemacs-packages/lisp/eieio/chart
~/my-lisp/eieio/call-tree
/usr/share/xemacs/xemacs-packages/lisp/eieio/call-tree
~/my-lisp/eieio/eieio-speedbar
/usr/share/xemacs/xemacs-packages/lisp/eieio/eieio-speedbar
/usr/share/xemacs/site-packages/lisp/semi/smime
/usr/share/xemacs/xemacs-packages/lisp/gnus/smime
/usr/share/xemacs/site-packages/lisp/flim/smtpmail
/usr/share/xemacs/xemacs-packages/lisp/mail-lib/smtpmail
/usr/share/xemacs/site-packages/lisp/semi/pgg
/usr/share/xemacs/xemacs-packages/lisp/pgg/pgg
/usr/share/xemacs/site-packages/lisp/semi/pgg-pgp5
/usr/share/xemacs/xemacs-packages/lisp/pgg/pgg-pgp5
/usr/share/xemacs/site-packages/lisp/semi/pgg-pgp
/usr/share/xemacs/xemacs-packages/lisp/pgg/pgg-pgp
/usr/share/xemacs/site-packages/lisp/semi/pgg-parse
/usr/share/xemacs/xemacs-packages/lisp/pgg/pgg-parse
/usr/share/xemacs/site-packages/lisp/semi/pgg-gpg
/usr/share/xemacs/xemacs-packages/lisp/pgg/pgg-gpg
/usr/share/xemacs/site-packages/lisp/semi/pgg-def
/usr/share/xemacs/xemacs-packages/lisp/pgg/pgg-def
/usr/share/xemacs/site-packages/lisp/flim/sasl
/usr/share/xemacs/xemacs-packages/lisp/sasl/sasl
/usr/share/xemacs/site-packages/lisp/flim/sasl-scram
/usr/share/xemacs/xemacs-packages/lisp/sasl/sasl-scram
/usr/share/xemacs/site-packages/lisp/flim/sasl-ntlm
/usr/share/xemacs/xemacs-packages/lisp/sasl/sasl-ntlm
/usr/share/xemacs/site-packages/lisp/flim/sasl-digest
/usr/share/xemacs/xemacs-packages/lisp/sasl/sasl-digest
/usr/share/xemacs/site-packages/lisp/flim/sasl-cram
/usr/share/xemacs/xemacs-packages/lisp/sasl/sasl-cram
/usr/share/xemacs/site-packages/lisp/flim/ntlm
/usr/share/xemacs/xemacs-packages/lisp/sasl/ntlm
/usr/share/xemacs/site-packages/lisp/flim/hmac-sha1
/usr/share/xemacs/xemacs-packages/lisp/sasl/hmac-sha1
/usr/share/xemacs/site-packages/lisp/flim/hmac-md5
/usr/share/xemacs/xemacs-packages/lisp/sasl/hmac-md5
/usr/share/xemacs/site-packages/lisp/flim/hmac-def
/usr/share/xemacs/xemacs-packages/lisp/sasl/hmac-def
~/my-lisp/semantic/working
/usr/share/xemacs/xemacs-packages/lisp/semantic/working
~/my-lisp/semantic/sformat
/usr/share/xemacs/xemacs-packages/lisp/semantic/sformat
~/my-lisp/semantic/senator
/usr/share/xemacs/xemacs-packages/lisp/semantic/senator
~/my-lisp/semantic/semanticdb
/usr/share/xemacs/xemacs-packages/lisp/semantic/semanticdb
~/my-lisp/semantic/semantic
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic
~/my-lisp/semantic/semantic-util
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-util
~/my-lisp/semantic/semantic-texi
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-texi
~/my-lisp/semantic/semantic-skel
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-skel
~/my-lisp/semantic/semantic-scm
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-scm
~/my-lisp/semantic/semantic-sb
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-sb
~/my-lisp/semantic/semantic-make
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-make
~/my-lisp/semantic/semantic-load
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-load
~/my-lisp/semantic/semantic-java
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-java
~/my-lisp/semantic/semantic-imenu
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-imenu
~/my-lisp/semantic/semantic-ia
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-ia
~/my-lisp/semantic/semantic-ia-sb
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-ia-sb
~/my-lisp/semantic/semantic-example
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-example
~/my-lisp/semantic/semantic-el
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-el
~/my-lisp/semantic/semantic-ctxt
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-ctxt
~/my-lisp/semantic/semantic-chart
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-chart
~/my-lisp/semantic/semantic-cb
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-cb
~/my-lisp/semantic/semantic-c
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-c
~/my-lisp/semantic/semantic-bnf
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-bnf
~/my-lisp/semantic/semantic-analyze
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-analyze
~/my-lisp/semantic/document-vars
/usr/share/xemacs/xemacs-packages/lisp/semantic/document-vars
~/my-lisp/semantic/semantic-util-modes
/usr/share/xemacs/xemacs-packages/lisp/semantic/semantic-util-modes
~/my-lisp/semantic/document
/usr/share/xemacs/xemacs-packages/lisp/semantic/document
~/my-lisp/speedbar/speedbar
/usr/share/xemacs/xemacs-packages/lisp/speedbar/speedbar
~/my-lisp/speedbar/sb-w3
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-w3
~/my-lisp/speedbar/sb-texinfo
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-texinfo
~/my-lisp/speedbar/sb-rmail
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-rmail
~/my-lisp/speedbar/sb-info
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-info
~/my-lisp/speedbar/sb-image
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-image
~/my-lisp/speedbar/sb-html
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-html
~/my-lisp/speedbar/sb-gud
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-gud
~/my-lisp/speedbar/sb-ant
/usr/share/xemacs/xemacs-packages/lisp/speedbar/sb-ant
~/my-lisp/speedbar/rpm
/usr/share/xemacs/xemacs-packages/lisp/speedbar/rpm
~/my-lisp/speedbar/dframe
/usr/share/xemacs/xemacs-packages/lisp/speedbar/dframe
~/my-lisp/speedbar/bigclock
/usr/share/xemacs/xemacs-packages/lisp/speedbar/bigclock
/usr/share/xemacs/site-packages/lisp/semi/signature
/usr/share/xemacs/xemacs-packages/lisp/tm/signature
/usr/share/xemacs/site-packages/lisp/semi/mime-setup
/usr/share/xemacs/xemacs-packages/lisp/tm/mime-setup
/usr/share/xemacs/site-packages/lisp/flim/mel-u
/usr/share/xemacs/xemacs-packages/lisp/tm/mel-u
/usr/share/xemacs/site-packages/lisp/flim/mel-q
/usr/share/xemacs/xemacs-packages/lisp/tm/mel-q
/usr/share/xemacs/site-packages/lisp/flim/mel-g
/usr/share/xemacs/xemacs-packages/lisp/tm/mel-g
/usr/share/xemacs/site-packages/lisp/flim/mel
/usr/share/xemacs/xemacs-packages/lisp/tm/mel
/usr/share/xemacs/xemacs-packages/lisp/build/build-report
/usr/share/xemacs/21.4.13/lisp/build-report)
Installed XEmacs Packages:
-------------------------
((zenirc:version 1.13 :type regular)
(xslt-process :version 1.11 :type regular)
(xslide :version 1.07 :type regular)
(xemacs-devel :version 1.55 :type single-file)
(xemacs-base :version 1.78 :type regular)
(x-symbol :version 1.05 :type regular)
(w3 :version 1.28 :type regular)
(vm :version 7.14 :type regular)
(viper :version 1.36 :type regular)
(view-process :version 1.12 :type regular)
(vhdl :version 1.17 :type regular)
(vc-cc :version 1.21 :type regular)
(vc :version 1.37 :type regular)
(tramp :version 1.15 :type regular)
(tpu :version 1.12 :type regular)
(tooltalk :version 1.13 :type regular)
(tm :version 1.36 :type regular)
(time :version 1.13 :type regular)
(textools :version 1.14 :type regular)
(text-modes :version 1.61 :type single-file)
(texinfo :version 1.24 :type regular)
(supercite :version 1.19 :type regular)
(strokes :version 1.08 :type regular)
(speedbar :version 1.26 :type regular)
(sounds-wav :version 1.1 :type regular)
(sounds-au :version 1.1 :type regular)
(sml-mode :version 0.09 :type regular)
(slider :version 1.13 :type regular)
(sieve :version 1.13 :type regular)
(sh-script :version 1.17 :type regular)
(sgml :version 1.08 :type regular)
(semantic :version 1.17 :type regular)
(scheme :version 1.13 :type regular)
(sasl :version 1.13 :type regular)
(ruby-modes :version 1.01 :type regular)
(rmail :version 1.13 :type regular)
(reftex :version 1.28 :type regular)
(python-modes :version 1.02 :type single-file)
(psgml-dtds :version 1.02 :type regular)
(psgml :version 1.4 :type regular)
(ps-print :version 1.08 :type regular)
(prog-modes
:version
1
.79
:type
single-file)
(pgg :version 1.03 :type regular)
(perl-modes :version 1.04 :type single-file)
(pcomplete :version 1.02 :type regular)
(pcl-cvs :version 1.64 :type regular)
(pc :version 1.25 :type single-file)
(os-utils :version 1.31 :type single-file)
(ocaml :version 0.04 :type regular)
(net-utils :version 1.32 :type single-file)
(mmm-mode :version 1.0 :type regular)
(misc-games :version 1.16 :type single-file)
(mine :version 1.14 :type regular)
(mh-e :version 1.23 :type regular)
(mew :version 1.17 :type regular)
(mailcrypt :version 2.12 :type regular)
(mail-lib :version 1.59 :type regular)
(liece :version 1.12 :type regular)
(jde :version 1.45 :type regular)
(ispell :version 1.24 :type regular)
(ilisp :version 1.32 :type regular)
(igrep :version 1.1 :type regular)
(idlwave :version 1.28 :type regular)
(ibuffer :version 1.08 :type regular)
(hm--html-menus :version 1.21 :type regular)
(haskell-mode :version 1.05 :type regular)
(gnus :version 1.71 :type regular)
(gnats :version 1.15 :type regular)
(general-docs :version 1.0 :type regular)
(games :version 1.14 :type regular)
(fsf-compat :version 1.12 :type single-file)
(frame-icon :version 1.09 :type regular)
(fortran-modes :version 1.02 :type single-file)
(forms :version 1.14 :type regular)
(footnote :version 1.15 :type regular)
(eudc :version 1.38 :type regular)
(eterm :version 1.13 :type regular)
(ess :version 1.04 :type regular)
(eshell :version 1.05 :type regular)
(emerge :version 1.09 :type regular)
(elib :version 1.1 :type single-file)
(eieio :version 1.04 :type regular)
(efs :version 1.29 :type regular)
(edt :version 1.12 :type regular)
(edit-utils :version 2.02 :type single-file)
(ediff :version 1.47 :type regular)
(edebug :version 1.18 :type regular)
(ecrypto :version 0.13 :type regular)
(ecb :version 1.08 :type regular)
(docbookide :version 0.06 :type regular)
(dired :version 1.13 :type regular)
(dictionary :version 1.12 :type regular)
(debug :version 1.16 :type regular)
(crisp :version 1.12 :type regular)
(cookie :version 1.14 :type regular)
(clearcase :version 1.06 :type regular)
(cc-mode :version 1.33 :type regular)
(calendar :version 1.19 :type regular)
(calc :version 1.23 :type regular)
(c-support :version 1.16 :type single-file)
(build :version 1.1 :type regular)
(bbdb :version 1.23 :type regular)
(auctex :version 1.35 :type regular)
(apel :version 1.26 :type regular)
(ada :version 1.13 :type regular)
(Sun :version 1.13 :type regular)
(skk :version 1.23 :type regular)
(mule-ucs :version 1.04 :type regular)
(mule-base :version 1.43 :type regular)
(lookup :version 1.13 :type regular)
(locale :version 1.2 :type regular)
(leim :version 1.2 :type regular)
(latin-unity :version 1.07 :type regular)
(egg-its :version 1.26 :type regular)
(edict :version 1.13 :type regular))
Installed Modules:
-----------------
Features:
--------
(mail-abbrevs xemacsbug shadow sendmail rfc822 font paren blink-paren
ecb-layout-defs autorevert bk view-less view x-migrant vc vc-hooks man
diff-mode swbuff recentf ecb ecb-autogen autoload ecb-tod ecb-cycle
ecb-eshell ecb-navigate ecb-help ecb-jde efc ecb-layout
ecb-create-layout ecb-mode-line ecb-compilation ecb-speedbar ecb-face
tree-buffer semantic-load semantic-ia-sb semantic-analyze
semantic-ctxt semantic-cb eieio-base eieio-speedbar eieio-custom
wid-edit speedbar sb-image dframe eieio semantic-util-modes timer
semantic-util semantic assoc working ecb-upgrade ecb-util advice
advice-preload rsz-minibuf crypt crypt++ func-menu dired-faces
dired-xemacs dired python-mode info-look info ansi-color compile
comint ring adb-mode highlight sh-script skeleton font-lock cus-face
executable toggle-source profile-mode valgrind-mode list-mode edmacro
ispell un-define mule-uni latin-euro-input quail overlay
latin-unity-tables latin-unity-latin10 latin-unity-latin9
latin-unity-latin8 latin-unity-latin7 latin-unity-vars latin-unity
x-compose zenirc-autoloads xslt-process-autoloads xslide-autoloads
xemacs-devel-autoloads xemacs-base-autoloads x-symbol-autoloads
w3-autoloads vm-autoloads viper-autoloads view-process-autoloads
vhdl-autoloads vc-cc-autoloads vc-autoloads tramp-autoloads
tpu-autoloads tooltalk-autoloads tm-autoloads time-autoloads
textools-autoloads text-modes-autoloads texinfo-autoloads
supercite-autoloads strokes-autoloads speedbar-autoloads
sounds-wav-autoloads sounds-au-autoloads sml-mode-autoloads
slider-autoloads sieve-autoloads sh-script-autoloads sgml-autoloads
semantic-autoloads scheme-autoloads sasl-autoloads
ruby-modes-autoloads rmail-autoloads reftex-autoloads
python-modes-autoloads psgml-dtds-autoloads psgml-autoloads
ps-print-autoloads prog-modes-autoloads pgg-autoloads
perl-modes-autoloads pcomplete-autoloads pcl-cvs-autoloads
pc-autoloads os-utils-autoloads ocaml-autoloads net-utils-autoloads
mmm-mode-autoloads misc-games-autoloads mine-autoloads mh-e-autoloads
mew-autoloads mailcrypt-autoloads mail-lib-autoloads liece-autoloads
jde-autoloads ispell-autoloads ilisp-autoloads igrep-autoloads
idlwave-autoloads ibuffer-autoloads hm--html-menus-autoloads
haskell-mode-autoloads gnus-autoloads gnats-autoloads
general-docs-autoloads games-autoloads fsf-compat-autoloads
frame-icon-autoloads fortran-modes-autoloads forms-autoloads
footnote-autoloads eudc-autoloads eterm-autoloads ess-autoloads
eshell-autoloads emerge-autoloads elib-autoloads eieio-autoloads
efs-autoloads edt-autoloads edit-utils-autoloads ediff-autoloads
ediff-hook edebug-autoloads ecrypto-autoloads ecb-autoloads
docbookide-autoloads dired-autoloads dictionary-autoloads
debug-autoloads crisp-autoloads cookie-autoloads clearcase-autoloads
cc-mode-autoloads calendar-autoloads calc-autoloads
c-support-autoloads build-autoloads bbdb-autoloads auctex-autoloads
apel-autoloads ada-autoloads Sun-autoloads skk-autoloads
mule-ucs-autoloads mule-base-autoloads lookup-autoloads
locale-autoloads leim-autoloads latin-unity-autoloads
egg-its-autoloads edict-autoloads semi-autoloads flim-autoloads
lisp-autoloads disp-table loadhist auto-show fontl-hooks x-iso8859-1
canna-leim slovenian czech romanian ccl mule-help code-cmds
gutter-items menubar-items x-menubar mode-motion mouse itimer
auto-save lisp-mode easymenu iso8859-1 page buff-menu lib-complete
cus-file derived frame text-props obsolete cus-start custom widget
cl-extra mini-cl cl cl-19 packages backquote very-early-lisp CANNA
file-coding wnn mule lucid-scrollbars cut-buffer lucid-menubars
athena-dialogs x c-balloon-help tty-frames tty toolbar native-sound
scrollbar unix-processes multicast network-streams subprocesses
modules menu-accelerator-support menubar berkeley-db dbm md5 xemacs
xim i18n2 gutter tiff png gif jpeg xface xpm xbm lisp-float-type linux
dialog devices window-system base64)
Recent keystrokes:
-----------------
misc-user
Recent messages (most recent first):
-----------------------------------
Loading xemacsbug...done
Loading xemacsbug...
Loading font...done
Loading font...
Paren mode is paren
Loading paren...done
Loading paren...
Loading ~/my-lisp/autorevert...done
Loading ~/my-lisp/autorevert...
No file removed from the list
Loading /homes/itamarg/.recentf...done
Loading /homes/itamarg/.recentf...
ECB 1.95.1 uses semantic 1.4.4, eieio 0.17 and speedbar 0.14beta4.
Loading advice...done
Loading advice...
Loading rsz-minibuf...done
Loading rsz-minibuf...
Loading /homes/itamarg/.emacsCC...done
Loading /homes/itamarg/.emacsCC...
Loading dired-mule...done
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 5 participants
- 7 comments
Re: Coding system sniffing.
17 years, 6 months
Aidan Kehoe
Aidan Kehoe
Ar an seachtú lá déag de mí Bealtaine, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > Reliably differentiating those [bit-for-bit identical] pairs
> > without metadata is not possible.
>
> And unnecessary, precisely because it's not possible.
With metadata, it is. Which is why I want useful metadata.
> It's only when you add disambiguating text that it matters, and then the
> Sufficiently Smart Program argument applies.
If you assume that no other program is processing the file, then yes. Which
is not a very useful starting point to people who do other things than hack
XEmacs.
If you’re working on a website, and you’ve configured Apache to send
ISO-8859-15 headers for every file served, and you’re editing a PHP file
with character literals, it is not appropriate for XEmacs to encode the Euro
sign as a tilde because it thinks the file is in ISO-8859-1.
> > Gzip and bzip2 legitimately don’t try to undo damage to files that
> > have been corrupted by FTP, and no-one expects them to.
> > Encouraging data corruption is not a particularly worthy goal,
>
> *sigh* Translating a file from ISO-8859-5 to KOI8-R is not data
> corruption any more than compressing a file with gzip is.
ISO-8859-5 and KOI8-R have differing repertoires. Unconditionally
translating from the former to the latter loses data. Unconditionally
translating from the latter to the former loses data. That is corruption.
> Unless there's a protocol that labels the file with its encoding, and
> some programs respect it while others ignore it. The latter may
> "corrupt" the file by translating, or by adding new data to a file that
> originally conformed to both encodings.
>
> Which is precisely the possibility that you propose to introduce. It
> is therefore your responsibility to at least think about ways to deal
> with the inevitable corruption, ie, incorrect cookies.
Warnings, warnings, warnings. GNU has them.
> I know why you want cookies; I don't deny that they are a useful
> private protocol. I just don't want you imposing the *known* problems
> with them on others without thinking about how to alleviate those
> problems.
Imposing? You’re aware they’re already there, right?
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: Coding system sniffing.
17 years, 6 months
Aidan Kehoe
Aidan Kehoe
Ar an cúigiú lá déag de mí Bealtaine, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > I want to enforce something I already know on XEmacs,
>
> I know what you want. I'm not telling you you can't have your
> Ferrari, I'm telling you that if you want to put it in the mainline,
> it needs to have a child seat.
>
> > > No, from the point of view of our workflow, it's not the same.
> > > Autodetection failures are in principle our responsibility, and in
> > > theory can be reduced to near zero by Sufficiently Smart Programming.
> >
> > Spoken like an East Asian. No they can’t. Trivial examples;
>
> Aidan, if I bet you €100 you couldn't do it, I'm sure I'd get an
> algorithm by return mail. No?
No. German in iso-8859-1, iso-8859-2, iso-8859-15 and iso-8859-16 without
using the Euro sign is bit-for-bit identical. Russian using KOI8-U (which
Ukrainians have occasion to do, the entire country is bilingual) is
bit-for-bit identical to the same Russian using KOI8-R. Reliably
differentiating those pairs without metadata is not possible.
> So let's calm down and put together a design that works for pretty
> much everybody, including folks with colleagues using bogus local
> versions of dos2unix.
Note that every solution will have some user behaviour where the correct
reaction for us is the frequent one of the MD confronted with a patient
whose complaint is ‘Doctor, it hurts when I do this’; ‘Then don’t do that.’
Gzip and bzip2 legitimately don’t try to undo damage to files that have been
corrupted by FTP, and no-one expects them to. Encouraging data corruption is
not a particularly worthy goal, especially in this day and age when Unix
programs can read Shift JIS.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
hyperbole 5.0 planned to replace 4.18
17 years, 6 months
The XEmacs Package Smoketest
The XEmacs Package Smoketest
Hi,
I've just released GNU Hyperbole 5.0. It is available for download at
"ftp://ftp.gnu.org/gnu/hyperbole"
Consequently I would want to make the switch and replace the current
version in the package tree, 4.18, with version 5.0, in order to
maintain one version of the package.
Why would you object? Well since 5.0 is based on version 4.01 there
are possibly a few things that will be broken or missing after the
change. The export function in kotl-mode is one example but there
might be others.
Still I think 5.0 is the way to go. Bug reports about missing
functions will of course get high priority to ease transition. The
reason why not everything is synced is due to my ignorance to only
support things I use and the thought that now, ten years later, things
might be solved differently.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: Coding system sniffing.
17 years, 6 months
Aidan Kehoe
Aidan Kehoe
Ar an cúigiú lá déag de mí Bealtaine, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
> >
> > Ar an cúigiú lá déag de mí Bealtaine, scríobh Stephen J. Turnbull:
> >
> > > In XML, it's strictly enforced by validating parsers;
> >
> > Right, but there's no guarantee a validating parser has been run on a given
> > XML file that XEmacs sees.
>
> Sure. My point is that an XML charset declaration that is wrong is an
> error, and by definition other software can treat that case as
> deprecated. Users who don't know the rules, well, too bad. But when
> there is no rule outside of XEmacs, it's not reasonable to expect the
> users to enforce it on their environment.
I want to enforce something I already know on XEmacs, in a way that will
work on other machines that don’t have my value of file-coding-system-alist.
In a way that won’t interfere with command line parsing, as happens on
Cygwin currently:
/usr/bin/env: perl # -*- coding: windows-1251 -*-: No such file or directory
Having it work on GNU Emacs too would be gravy.
> > > We don't *need* to do anything; the user can always go back and
> > > re-read the file with C-u C-x C-f.
> >
> > Oh, don't be obtuse. On that reasoning, we can abandon development
> > right now since anyone who would like a feature we don't have can
> > implement it themselves.
>
> I'm not being obtuse. Lack of cookie support is not a security or
> data loss issue (by itself), nor is it a bug at all; as you point out,
> it's a missing feature. We don't *need* to do anything.
Only in the sense I gave above.
> So let's take the time to not introduce new ways to fail.
Everything we do introduces new ways to fail. The interesting thing is the
tradeoff between those and the positive aspects of what we do.
> If the work to prevent cookie lossage helps deal with our existing
> sterile equine behavior, so much the better.
>
> > > No, that is an error mode of sniffing from cookies that we *create*
> > > for our users by parsing cookies that are not enforced by the
> > > protocol we're editing,
> >
> > The same error mode arises when the automatic coding detection
> > (independent of coding cookies) gets something wrong. It's distinct
> > from sniffing cookies.
>
> No, from the point of view of our workflow, it's not the same.
> Autodetection failures are in principle our responsibility, and in
> theory can be reduced to near zero by Sufficiently Smart Programming.
Spoken like an East Asian. No they can’t. Trivial examples; deciding between
iso-8859-1 vs. iso-8859-15. Between KOI8-U used for Russian vs. KOI8-R.
iso-8859-2 used for German, vs iso-8859-1 used for German (bit-for-bit
identical, until someone types the word Škoda, which Germans have occasion
to do now and then).
> OTOH, the rate of broken cookies was quite high in the early days of
> Nihongo Emacs; I didn't stop seeing them until cookies themselves
> disappeared (in modern MULE, distinguishing among the 4 common
> Japanese encodings is essentially perfect). The problem was that
> people would do things like modify dos2unix to also recode Shit JIS as
> EUC-JP, but not to recognize Emacs coding cookies (a reasonable
> behavior for vi users, you will admit, I hope). So you'd get whole
> trees full of EUC-JP marked as Shit JIS.
Japan; the land of transcoding HTTP proxies. The land where backslash is
written as Y with two lines through it. The land of government standards for
character sets that left encodings underspecified.
Okay, so we don’t need coding cookies in Japan today. That doesn’t help
Europe a whole lot.
> > If you can find it without too much searching, I'd appreciate a
> > link to what Ilya posted. Otherwise I suppose I can ask him.
>
> Will do.
Thanks.
> I gather you're not in a "by 10pm tonight" kind of hurry?
Nope.
> (Thing is, I suspect this is in archives that aren't online, may as
> well take the time to put them online.)
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
packageGuide.html omission
17 years, 6 months
Peter Wiersig
Peter Wiersig
I built xemacs 21.5 beta27 20070502 without trouble.
I followed http://www.xemacs.org/Documentation/packageGuide.html#Installing_automati...
and was stumped because mailcrypt has additionally mail-lib as
dependancy. The error message was
Cannot open load file: "rfc822"
when trying to load mailcrypt directly and had an %s thrown in when
the menubar was used to call the package "List and install" or "Update
package list" funcitons.
After I installed that the further package management worked like a
charm. (for the first time after building a xemacs release. I blamed
the ftp command line client for the former problems with the package
management)
The additional dependency should be documented.
Peter
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: Coding system sniffing.
17 years, 6 months
David Kastrup
David Kastrup
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
> Aidan Kehoe writes:
>
> > GNU Emacs’ coding sniffing is better than ours; for example, it responds
> > sensibly to this at the start of a file:
> >
> > #!/usr/bin/env perl
> > # -*- coding: windows-1251 -*-
>
> Please, no. IMHO, if this must be done, do a design from scratch, and
> think about how to recover from an incorrect cookie (eg, because
> somebody copied boilerplate from one mostly-ASCII file to another,
> perhaps in an editor that doesn't respect cookies). *Then* look at
> GNU's implementation and see if it makes sense in the light of a
> sensible design.
Whether or not it makes sense in the light of a sensible design: if it
is reasonably reliable, there is a chance that people will adapt the
few cases where it misses to Emacs' heuristics, and if XEmacs had
different heuristics, this would be sort of a pain in the neck.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Re: Coding system sniffing.
17 years, 6 months
Aidan Kehoe
Aidan Kehoe
Ar an cúigiú lá déag de mí Bealtaine, scríobh Stephen J. Turnbull:
> In XML, it's strictly enforced by validating parsers;
Right, but there’s no guarantee a validating parser has been run on a given
XML file that XEmacs sees.
> > We need to respond sensibly to that at the start of a file. We
> > don’t currently.
>
> We don't *need* to do anything; the user can always go back and
> re-read the file with C-u C-x C-f.
Oh, don’t be obtuse. On that reasoning, we can abandon development right now
since anyone who would like a feature we don’t have can implement it
themselves.
> The question is "how can we help the judicious coder introduce a
> convenient automatic protocol without exposing naive users to abuse from
> the kind of guy who would smoke in a maternity ward?"
Warnings, I think.
> > > IMHO, if this must be done, do a design from scratch, and think about how
> > > to recover from an incorrect cookie (eg, because somebody copied
> > > boilerplate from one mostly-ASCII file to another, perhaps in an editor
> > > that doesn't respect cookies).
> >
> > That’s distinct from sniffing using coding cookies,
>
> No, that is an error mode of sniffing from cookies that we *create*
> for our users by parsing cookies that are not enforced by the protocol
> we're editing,
The same error mode arises when the automatic coding detection (independent
of coding cookies) gets something wrong. It’s distinct from sniffing
cookies.
> > > Anyway, IIRC, you already committed a half-baked patch from Ivan
> > > Golubev to do this.
> >
> > No, that wasn’t me.
>
> Well, if you decide to do this yourself, Ivan did exactly what you
> propose (port the GNU code, from 21.3 IIRC). I thought somebody
> committed it as a package, but you're right, I don't see it anywhere.
If you can find it without too much searching, I’d appreciate a link to what
Ilya posted. Otherwise I suppose I can ask him.
> I'll help with documenting existing workarounds.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: Coding system sniffing.
17 years, 6 months
Aidan Kehoe
Aidan Kehoe
Ar an cúigiú lá déag de mí Bealtaine, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > GNU Emacs’ coding sniffing is better than ours; for example, it
> > responds sensibly to this at the start of a file:
> >
> > #!/usr/bin/env perl
> > # -*- coding: windows-1251 -*-
>
> Please, no.
Hmm? That’s how Python does it, and AIUI you had some part in their choice
of that deisgn. We need to respond sensibly to that at the start of a
file. We don’t currently.
> IMHO, if this must be done, do a design from scratch, and think about how
> to recover from an incorrect cookie (eg, because somebody copied
> boilerplate from one mostly-ASCII file to another, perhaps in an editor
> that doesn't respect cookies).
That’s distinct from sniffing using coding cookies, and there’s no general
solution to it; windows-1251 cannot be reliably distinguished from
ISO-8859-1, or even from UTF-8. (The opposite direction _is_ possible for
UTF-8, though.)
> *Then* look at GNU's implementation and see if it makes sense in the
> light of a sensible design.
>
> Anyway, IIRC, you already committed a half-baked patch from Ivan
> Golubev to do this.
No, that wasn’t me.
> > and if I understand things correctly it also sniffs XML coding
> > correctly.
>
> This is very useful, and I too would like to see it; it's been on my
> list for a while.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments