Fatal error (11).
22 years, 11 months
Magnusson Thomas
Magnusson Thomas
Hi, I'm running xemacs 20.4 and the following happended to me
when I tried to do C-H f with the cursor over the string
`strokes-define-stroke'.
/tm
---
I'm running Solaris 7 on a Ultra Sparc
Fatal error (11).
Lisp backtrace follows:
skip-syntax-backward("_w")
# (unwind-protect ...)
# (unwind-protect ...)
# bind (stab)
byte-code("À ÂÃ
!ÅÆÇ!!«`fzÈa¬`fzÉa¬ÊË!ÌÍwÎp!9Ð!," [syntax-table stab
((set-syntax-table stab)) set-syntax-table emacs-lisp-mode-syntax-table
zerop skip-syntax-backward "_w" ?w ?\_ forward-sexp -1 "`'" nil read obj
fboundp] 4)
# (condition-case ... . ((error)))
function-at-point()
(let* ((fn ...) (val ...)) (list (if ... fn ...)))
)
call-interactively(describe-function)
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault (core dumped)
$
$
$ gdb $(whence xemacs) core
(gdb) where
#0 0xfec9a480 in _libc_kill ()
#1 0x858cc in fatal_error_signal ()
#2 <signal handler called>
#3 0xebb70 in bufpos_to_bytind_func ()
#4 0x1260a4 in find_before_next_newline ()
#5 0x1266e8 in Fskip_syntax_backward ()
#6 0x8bf1c in funcall_recording_as ()
#7 0x8c4dc in Ffuncall ()
#8 0x69580 in Fbyte_code ()
#9 0x8b944 in Feval ()
#10 0x89954 in condition_case_1 ()
#11 0x89adc in Fcondition_case_3 ()
#12 0x69a44 in Fbyte_code ()
#13 0x8d260 in Fapply ()
#14 0x8cf9c in Fapply ()
#15 0x8bb9c in Feval ()
#16 0x88a98 in FletX ()
#17 0x8b914 in Feval ()
#18 0x6ae14 in Fcall_interactively ()
#19 0x8ac44 in Fcommand_execute ()
#20 0xbd624 in extract_vector_nth_mouse_event ()
#21 0xbdc04 in Fdispatch_event ()
#22 0x72b34 in Fcommand_loop_1 ()
#23 0x7295c in Frecursive_edit ()
#24 0x89954 in condition_case_1 ()
#25 0x72388 in Freally_early_error_handler ()
#26 0x723b0 in Freally_early_error_handler ()
#27 0x895e4 in internal_catch ()
#28 0x725bc in initial_command_loop ()
#29 0x86b1c in Finvocation_directory ()
#30 0x87248 in main ()
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "sparc-sun-solaris2.6"...
(no debugging symbols found)...
core: No such file or directory.
(gdb) where
No stack.
Sorry!
/tm
- 2 participants
- 1 comments
bug : edebug-read-sexp [upstream?]
22 years, 11 months
Sean Champ
Sean Champ
the big question:
what in eieio.el is having the side-effect of 'read' being aliased to
'edebug-read', but only when eieio.el is byte-compiled?
i've been grepping around for it, but can't seem to find it; there's no
'edebug-read' in eieio, though there are some places in eieio.el, where edebug
forms are used.
edebug-read is giving my xemacs some indigestion problems.
anyway, here's the bug description:
there's something in a file that is loaded as a result of:
(byte-compile-and-load eieio-main-lib)
...which is redefining 'read', and making it an alias to 'edebug-read'; later,
when i run a certain function, then 'edebug-read-sexp' is causing an
error. Namely, i'm getting a strange 'exceeds max-lisp-eval-depth' error --
edebug-read-sexp starts looping.
The bug doesn't happen after a clean
(load-file eieio-main-lib)
...when 'read' is just its straight built-in 'read', and not an alias to
'ededbug-read'.
Fixing it?:
what in eieio.el is having the side-effect of 'read' being aliased to
'edebug-read', but only when folding.el is byte-compiled? i've been grepping
around for it, but can't seem to find it.
--
environment:
Emacs version: 21.4.5 , with gtk widgets, on debian linux 3.0 (woody)
As for what this xemacs 21.4.5 was compiled with,
(maphash #'(lambda (key value)
(insert (format "%s : %s" key value))
(newline))
(config-value-hash-table))
...just makes a long list of things. my concern is with finding what's
mangling the definition of 'read', and stopping it from doing that.
{{{ steps to reproduce
(require 'eieio)
;; define the function where the error seems to occur
(defun foo-serialize (project)
"return a serialized form of PROJECT, suitable for saving and restoring the
project and its slots. "
(with-temp-buffer
(let ((outv) (standard-output (current-buffer)))
;; backquote it, to keep read from evaluating it.
(insert "`")
;; the default object-write prints the data to 'standard-output'
(object-write project))
(goto-char (point-min))
; DEBUG:
(switch-to-buffer (current-buffer))
(read-string "continue...")
(condition-case err
;; this is where the read starts:
(while (setq outv (cons 'make-instance (cadr (read (current-buffer))))))
(end-of-file outv))))
;; byte-compile and load the local eieio library
(byte-compile-and-load-file
(car (member* "eieio.el" (library-all-completions "eieio" load-path t)
:test #'string-match
:key #'file-name-nondirectory )))
;; or use the straight 0.16
;(byte-compile-and-load-file"~/project/xemacs/package/eieio/eieio-0.16/eieio.el")
;;or the un-modified 0.17beta3
;(byte-compile-and-load-file "~/project/xemacs/package/eieio/eieio-0.17beta3/eieio.el")
; then
(defclass foo () nil)
(setq x (make-instance 'foo))
(foo-serialize x)
;; RESULT:
;; when doing that foo-serialize, i get a massive backtrace, about
;; '... exceeds 'max-lisp-eval-depth' , on 'edebug-read-sexp'.
;; Now, i _don't_ get that error, when i do one of the following:
; (require 'eieio)
;; or
; (load-file "~/project/xemacs/package/eieio/eieio-0.16/eieio.el")
;; or
; (load-file "~/project/xemacs/package/eieio/eieio-0.17beta3/eieio.el")
;...instead of any of the (byte-compile-and-load-file ...) forms, as above.
; so, 'read' is apparently only being aliased to 'ededbug-read-sexp', during
; (byte-compile "eieio.el")
}}}
{{{ backtrace
Signaling: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
edebug-next-token-class()
<snipped: a bunch of calls to edebug-read-sexp>
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-sexp()
edebug-read-and-maybe-wrap-form1()
byte-code("..." [result edebug-read-and-maybe-wrap-form1 nil] 1)
edebug-read-and-maybe-wrap-form()
read(#<buffer " *temp*">)
(cadr (read (current-buffer)))
(cons (quote make-instance) (cadr (read ...)))
(setq outv (cons (quote make-instance) (cadr ...)))
(while (setq outv (cons ... ...)))
(condition-case err (while (setq outv ...)) (end-of-file outv))
(save-current-buffer (set-buffer temp-buffer) (let (... ...) (insert "`") (object-write project)) (goto-char (point-min)) (switch-to-buffer (current-buffer)) (read-string "continue...") (condition-case err (while ...) (end-of-file outv)))
(with-current-buffer temp-buffer (let (... ...) (insert "`") (object-write project)) (goto-char (point-min)) (switch-to-buffer (current-buffer)) (read-string "continue...") (condition-case err (while ...) (end-of-file outv)))
(unwind-protect (with-current-buffer temp-buffer (let ... ... ...) (goto-char ...) (switch-to-buffer ...) (read-string "continue...") (condition-case err ... ...)) (and (buffer-name temp-buffer) (kill-buffer temp-buffer)))
(let ((temp-buffer ...)) (unwind-protect (with-current-buffer temp-buffer ... ... ... ... ...) (and ... ...)))
(with-temp-buffer (let (... ...) (insert "`") (object-write project)) (goto-char (point-min)) (switch-to-buffer (current-buffer)) (read-string "continue...") (condition-case err (while ...) (end-of-file outv)))
foo-serialize([object foo foo])
eval((foo-serialize x))
eval-interactive((foo-serialize x))
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
}}}
- 1 participants
- 0 comments
[QUERY 21.4] Re: [PATCH] etags sync
22 years, 11 months
Stephen J. Turnbull
Stephen J. Turnbull
QUERY 21.4
>>>>> "Yoshiki" == Yoshiki Hayashi <yoshiki(a)xemacs.org> writes:
Yoshiki> Makefile.in.in portion is recommended for 21.4.
(NB this is to add -DEMACS_NAME=XEmacs to CFLAGS for etags.)
Is the same change appropriate for ootags?
We probably ought to think about making emacs_name a configure
variable (eg for use of Infodock, UTF-2000 XEmacs, etc). Comment?
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
- 3 participants
- 3 comments
find-paths.el and run-in-place
22 years, 11 months
Harnois, Michael D.
Harnois, Michael D.
(moving this discussion, about how the recent change to find-paths.el has
broken run-in-place with XEmacs defaults, to the list)
I'll try that, thanks. But then it seems it will also be necessary to change
all the package installation code, that worked until last week, to work with
your new setting, or that all users who run in place will have to specify
directory paths in their init file. Also, it will be necessary to change the
directory each time the version changes. All of this is terribly unfriendly
to users. It seems like it would be easier and more straightforward for you
to change your code so that it finds the directory that the package
installation routine uses by default.
----- Original Message -----
From: "Michael Sperber [Mr. Preprocessor]"
<sperber(a)informatik.uni-tuebingen.de>
To: "Michael Harnois" <mharnois(a)cpinternet.com>
Sent: Tuesday, December 18, 2001 8:09 AM
Subject: Re: [PATCH] generalizing face settings..., GTK face fixes
> >>>>> "Michael" == Michael Harnois <mharnois(a)cpinternet.com> writes:
>
> Michael> On Tue, 2001-12-18 at 07:28, Michael Sperber [Mr. Preprocessor]
wrote:
> >> >>>>> "Michael" == Michael Harnois <mharnois(a)cpinternet.com> writes:
> >>
> >> If you run XEmacs in-place, it expects the packages to be in-place as
> >> well. I'm surprised XEmacs worked at all previously---this certainly
> >> wasn't by any design.
>
> Michael> I'm not certain what you mean by "by design." Ever since the
> Michael> package system was instituted -- it's been several years now,
> Michael> hasn't it? -- that's where XEmacs has installed the packages
> Michael> by default, run-in-place or not. That certainly seems like
> Michael> "design" to me, and when it suddenly stops working, that
> Michael> seems like breakage.
>
> This has nothing to do with the package system, but rather how XEmacs
> determines where to find its files at startup. The code for this was
> entirely written by me before the first XEmacs with an advertised
> package system came out. It tries to be smart about it, and works in
> many environments and ways I never envisioned. It certainly was part
> of my intention that, if you run in-place, you run *everything*
> in-place, and I feel qualified to say that your being able to run in
> this split setup is mere accident.
>
> You'll probably notice that, when you create an xemacs-<version>
> directory alongside the vanilla xemacs one, your setup starts working
> again. I would recommend simple symlinks, however.
>
> --
> Cheers =8-} Mike
> Friede, Völkerverständigung und überhaupt blabla
- 5 participants
- 9 comments
Glyph example documentation
22 years, 11 months
Darryl Okahata
Darryl Okahata
FYI,
I'm adding some examples to the lispref documentation, on how to
display graphics in a buffer. Here is my current draft. Before I
submit patches, I'd like to get some comments.
[ Although the following is a formatted info node, I am doing all of the
changes in texinfo. ]
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
===============================================================================
File: lispref.info, Node: Glyph Examples, Prev: Subwindows, Up: Glyphs
Glyph Examples
==============
For many applications, displaying graphics is a simple process: you
create a glyph, and then you insert it into the buffer.
The easiest way to create a glyph is to use a file that contains a
graphical image, such as a JPEG, TIFF, or PNG file:
;; Create a glyph from a JPEG file:
(setq foo (make-glyph [jpeg :file "/tmp/file1.jpg"]))
;; Create a glyph from a XPM file:
(setq foo (make-glyph [xpm :file "/tmp/file2.xpm"]))
;; Create a glyph from a PNG file:
(setq foo (make-glyph [png :file "/tmp/file3.png"]))
;; Create a glyph from a TIFF file:
(setq foo (make-glyph [tiff :file "/tmp/file4.tiff"]))
The parameters passed to `make-glyph' are called "Image Specifiers",
and can handle more image types than those shown above. You can also
put the raw image data into a string (e.g., if you put the contents of
a JPEG file into a string), and use that to create a glyph. *Note
Image Specifiers::, for more information.
*Caution*: In order for XEmacs to read a particular graphics file
format, support for that format must have been compiled into
XEmacs. It's possible, although somewhat unlikely, for XEmacs to
have been compiled without support for any of the various graphics
file formats. To see what graphics formats your particular
version of XEmacs supports, use `M-x describe-installation'.
Once you have a glyph, you can then insert it into a buffer.
Example:
;; Use this function to insert a glyph at the left edge of point in the
;; current buffer. Any existing glyph at this location is replaced.
(defun insert-glyph (gl)
"Insert a glyph at the left edge of point."
(let ( (prop 'myimage) ;; myimage is an arbitrary name, chosen
;; to (hopefully) not conflict with any
;; other properties. Change it if
;; necessary.
extent )
;; First, check to see if one of OUR extents already exists at point.
;; For ease-of-programming, we are creating and using our own extents
;; (multiple extents are allowed to exist/overlap at the same point).
;; Basically, if an extent, with the property stored in "prop",
;; exists at point, we assume that it is one of ours, and we re-use
;; it (this is why it is important for the property stored in "prop"
;; to be unique, and only used by us).
(if (not (setq extent (extent-at (point) (current-buffer) prop)))
(progn
;; If an extent does not already exist, create a zero-length
;; extent, and give it our special property.
(setq extent (make-extent (point) (point) (current-buffer)))
(set-extent-property extent prop t)
))
;; Display the glyph by storing it as the extent's "begin-glyph".
(set-extent-property extent 'begin-glyph gl)
))
;; You can then use this function like:
(insert-glyph (make-glyph [jpeg :file "/tmp/file1.jpg"]))
;; This will insert the glyph at point.
;; Here's an example of how to insert two glyphs side-by-side, at point
;; (using the above code):
(progn
(insert-glyph (make-glyph [jpeg :file "/tmp/file1.jpg"]))
;; Create a new extent at point. We can't simply call "insert-glyph",
;; as "insert-glyph" will simply replace the first glyph with the
;; second.
(setq extent (make-extent (point) (point) (current-buffer)))
;; Here, we're only setting the 'myimage property in case we need
;; to later identify/locate/reuse this particular extent.
(set-extent-property extent 'myimage t)
(set-extent-property extent 'begin-glyph
(make-glyph [jpeg :file "/tmp/file2.jpg"]))
)
Here are the gory details:
* Glyphs are displayed by attaching them to extents (see *Note
Extents::), either to the beginning or the end of extents.
* Glyphs are often displayed inside the text area (alongside text).
This is the default.
Although glyphs can also be displayed in the margins, how to do
this will not be described here. For more information on this, see
*Note Annotation Basics:: (look for information on "layout types")
and *Note Extent Properties:: (look for `begin-glyph-layout' and
`end-glyph-layout').
* The easiest way to insert a glyph into text is to create a
zero-length extent at the point where you want the glyph to appear.
* It's often a good idea to assign a unique property to the
newly-created extent, in case you later want to locate it, and
replace any existing glyph with a different one (or just delete
the existing one). In the above example, we are using "myimage"
as our unique property name.
* Glyphs are displayed by assigning then to the `begin-glyph' or
`end-glyph' property of the extent. For zero-length extents, it
doesn't really matter if you assign the glyph to the `begin-glyph'
or `end-glyph' property, as they are both at the same location;
however, for non-zero-length extents (extents that cover one or
more characters of text), it does matter which one you use.
Assigning `nil' to the `begin-glyph' or `end-glyph' property will
delete any existing glyph (in this case, you may also want to
delete the extent).
* If you happen to insert two glyphs, side-by-side, note that the
example `insert-glyph' function will have trouble, if it's again
used at the same point (it can only locate one of the two
extents). To locate all of the extents, you'll have to use
functions like `extent-list' or `next-extent', or provide
additional parameters to the `extent-at' function. *Note Mapping
Over Extents::, for more information.
* Among other things, glyphs provide a way of displaying graphics
alongside text. Note, however, that glyphs only provide a way of
displaying graphics; glyphs are not actually part of the text, and
are only displayed alongside the text. The low-level glyph code
does not provide a way of saving graphics with the text. If you
need to save graphics and text, you have to write your own code to
do this, and this topic is outside the scope of this discussion.
- 5 participants
- 9 comments
Re: abbrev case sensitive
22 years, 11 months
Yoshiki Hayashi
Yoshiki Hayashi
[Ccing back to xemacs-beta]
Uwe Brauer <oub(a)maraton.sim.ucm.es> writes:
> Yoshiki Hayashi writes:
> > Uwe Brauer <oub(a)maraton.sim.ucm.es> writes:
> >
> > > Are there any plans for future xemacs releases to make abbrev case
> > > sensitive? I use flyspell a lot, which automatically adds corrected
> > > words to an abbrev list, but since abbrev is not case sensitive the
> > > result can sometimes be annoying.
> >
> > Is dabbrev-case-fold-search what you want?
> >
>
> I am not sure, in xemacs-21.1.14 no such function or variable
> exists. Let me clarify again my point
>
> Suppose I have an entry like this in my .abbrev_defs
>
> (global-abbrev-table)
> "Anwer" 0 "Answer"
>
> Then also anwer is expanded to Answer which is wrong. It should be of
> course answer.
Ah, you are using abbrev-mode. I only use dabbrev-mode so I
don't know much about that mode. If you want to change
expand-abbrev to do that, it's in src/abbrev.c. There're
some calls to Fupcase_initials_region and Fupcase_region.
Probably changing some of those code will achieve what you
want.
--
Yoshiki Hayashi
- 1 participants
- 0 comments
xemacs segfaulting under X
22 years, 11 months
Florian Simnacher
Florian Simnacher
Hello,
at first thanks for maintaining xemacs.
Unfortunately the following problems occurs on my system:
'xemacs -nw' starts up on the console or xterm. But 'xemacs'
under X crashes with a segmentation fault.
Appended to this mail you will find the output before core dumping,
the ouput of M-x describe-installation and a backtrace from the
core.
Please contact in case of questions via florian.simnacher(a)eikon.tum.de.
Regards and best wishes,
Florian
BTW Speicherzugriffsfehler is german and means segmentation fault
########## Output before dumping core
florian＠hera:/usr/local/src/xemacs-21.4.5> xemacs
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, 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 /usr/local/bin/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" 0x1ba4>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Speicherzugriffsfehler
florian＠hera:/usr/local/src/xemacs-21.4.5>
########## Output of M-x describe-installation
uname -a: Linux hera 2.4.10-4GB #1 Tue Sep 25 12:33:54 GMT 2001 i686 unknown
./configure '--prefix=/usr/local/'
XEmacs 21.4.5 "Civil Service" configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /usr/local/src/xemacs-21.4.5
Installation prefix: /usr/local/
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O3 -Wall -Wno-switch -Winline
-Wmissing-prototypes -Wsign-compare -Wshadow
Relocating allocator for buffers: no
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/X11/include
- X Windows libraries location: /usr/X11/lib
- Handling WM_COMMAND properly.
Using Lucid menubars.
Using Lucid scrollbars.
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.
Sound:
Compiling in support for sound (native).
Databases:
Internationalization:
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Compiling in support for dynamic shared object modules.
########## Backtrace of core
#0 0x402f3861 in kill () from /lib/libc.so.6
#1 0x080a7e33 in fatal_error_signal (sig=11) at emacs.c:539
#2 <signal handler called>
#3 0x400fd888 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
#4 0x400fdbdf in xtWidgetAlloc () from /usr/X11R6/lib/libXt.so.6
#5 0x400fddc0 in xtCreate () from /usr/X11R6/lib/libXt.so.6
#6 0x400fe71b in _XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#7 0x400fe7bd in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#8 0x081775a5 in x_create_widgets (f=0x8460818, lisp_window_id=136313156,
parent=136313156) at frame-x.c:1957
#9 0x08177b4d in x_init_frame_1 (f=0x8460818, props=136313156)
at frame-x.c:2184
#10 0x080fb66c in Fmake_frame (props=136313156, device=138279680)
at frame.c:395
#11 0x080af08c in Ffuncall (nargs=3, args=0xbfffefa8) at eval.c:3528
#12 0x0808a109 in execute_optimized_program (
program=0x8460700 "Æ \210Ç ?&È\fÉ \"¬\027Ê\r\013\"\022Ë\rÈ\tÌ
\"＠\"\211\020\026\020Í\r!\025Î\016\021!\210Ï\211\024\207", stack_depth=5,
constants_data=0x8295378) at bytecode.c:746
#13 0x08089de9 in funcall_compiled_function (fun=137182552, nargs=0,
args=0xbffff0ec) at bytecode.c:515
#14 0x080af22f in Ffuncall (nargs=1, args=0xbffff0e8) at eval.c:3563
#15 0x0808a109 in execute_optimized_program (
program=0x83df3d8 "\013A\035ÆÇ\032\031È\r!\025\bÉa«\004Ê \210ËÌ!«\004Í
\210\f«\017\016\035¬\013ÎÏÐ\f!ÑQ! \210Ò \210*Ó \210Ô \210rÕÖ!q\210×
\210ØÙ!\210\016!Úa«\005\016\" \210)Û Üa«\bÝ ¬\004Þ \210ß \210Ù\026#Ý
\004àÇ!)\207moA\001",
stack_depth=4, constants_data=0x83270c8) at bytecode.c:746
#16 0x08089de9 in funcall_compiled_function (fun=137504036, nargs=0,
args=0xbffff22c) at bytecode.c:515
#17 0x080af22f in Ffuncall (nargs=1, args=0xbffff228) at eval.c:3563
#18 0x0808a109 in execute_optimized_program (
program=0x8248da8 "\t«\005ÆÇ!\207È\021É
\211\034«\025\fG\rGW«\016Ê\r!Ê\f!k«\005Ë\f!\025)Ì\r!\025Í \210Î
\210\013®\aÏÐ!\002È\eÑ\016#\016$\"\022\013«\tÒÓÔ\n\"Õ\"\210\n¬\004Ö
\210×\n\016%\b\016&\013%\210Ø
\210)\016!¬\022\016\"«\016ÙÚÛ\016'!\016\"\"ÜÈ#\210\016!¬\023\b¬\006Ý\016(!\210Ý\016)!\210Ý\016*!\210Þ\216ß
\210)\016+\003à \207gging ¡", stack_depth=7, constants_data=0x8326f08)
at bytecode.c:746
#19 0x08089de9 in funcall_compiled_function (fun=137503980, nargs=0,
args=0xbffff2d4) at bytecode.c:515
#20 0x080ae9a2 in Feval (form=137450780) at eval.c:3388
#21 0x080b4c76 in condition_case_1 (handlers=136313252,
bfun=0x80ae070 <Feval>, barg=137450780, hfun=0x8092890 <cmd_error>,
harg=136313156) at eval.c:1651
---Type <return> to continue, or q <return> to quit---
#22 0x0809291f in top_level_1 (dummy=136313156) at cmdloop.c:206
#23 0x080b4b3c in internal_catch (tag=136389252,
func=0x80928f0 <top_level_1>, arg=136313156, threw=0x0) at eval.c:1317
#24 0x080921e2 in initial_command_loop (load_me=136313156) at cmdloop.c:285
#25 0x080a8c3c in xemacs_21_4_5_i686_pc_linux () at emacs.c:2353
#26 0x080aa969 in main () at emacs.c:2782
#27 0x402e27ee in __libc_start_main () from /lib/libc.so.6
(gdb)
- 2 participants
- 1 comments
[ANNOUNCE] New & Updated packages in Pre-Release - Dec 18
22 years, 11 months
Steve Youngs
Steve Youngs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
mule-ucs-1.00-pkg.tar.gz (Mule) *** New Package ***
prog-modes-1.45-pkg.tar.gz
vc-1.30-pkg.tar.gz
Previously Announced Packages Still in Pre-Release:
==================================================
None
Detailed Changes:
================
mule-ucs-1.00-pkg.tar.gz
- ------------------------
This is a new package!
- From the TeXinfo:
Mule-UCS is a character code translator. It provides functions to
translate from any character set to any other, and construct new
coding systems easily.
prog-modes-1.45-pkg.tar.gz
- --------------------------
2001-12-18 Steve Youngs <youngs(a)xemacs.org>
* old-c-mode.el: New file.
* p4.el: Ditto.
* php-mode.el: Ditto.
* pydoc.el: Ditto.
* verilog-mode.el: Sync to author version 3.57
* Makefile (REQUIRES): Add vc, speedbar for p4 and php-mode.
(ELCS): Add old-c-mode.elc, p4.elc, php-mode.elc, pydoc.elc
(EXTRA_SOURCES): Add pydoc-el-README, pydoc_lisp.py
* package-info.in (provides): Update for new files.
vc-1.30-pkg.tar.gz
- ------------------
2001-12-17 Sean Champ <schamp(a)users.sourceforge.net>
* vc.el (vc-version-diff): Modified the `interactive' spec of
#'vc-version-diff so it will run the diff on the file in the
current buffer, unless a prefix argument is given, in which case
it'll do the old behavior of querying the user for the name of a
file to run the diff on.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
- --
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: The XEmacs Development Team.
iD8DBQE8HjDgjNKQaxDVycURAgJRAJ9NDvupDI+HZvyFJ0SoEvn4vGme0wCfdsac
yrXhLYZVhivQuHdIWYjzT3I=
=RIhp
-----END PGP SIGNATURE-----
- 6 participants
- 16 comments
RE: XEmacs dumps core upon exiting (sometimes)
22 years, 11 months
Miller, David M.
Miller, David M.
Ah! Solaris 2.7!
But we're running on Solaris 2.6 ... lemme do a search on Sun's website.
> -----Original Message-----
> From: Andy Piper [SMTP:andy＠xemacs.org]
> Sent: Tuesday, December 18, 2001 2:11 PM
> To: Miller, David M.; 'Andy Piper'
> Cc: Miller, David M.; xemacs-beta(a)xemacs.org
> Subject: RE: XEmacs dumps core upon exiting (sometimes)
>
> ** SunOS/Solaris
> *** Crashes when using Motif libraries, especially with multiple frames.
>
> Crashes that produce C-backtraces like this:
>
> #0 0xfec9a118 in _libc_kill () from /usr/lib/libc.so.1
> #1 0x77f48 in fatal_error_signal (sig=11)
> at /codes/rpluim/xemacs-21.4/src/emacs.c:539
> #2 <signal handler called>
> #3 0xfee929f4 in XFindContext () from /usr/openwin/lib/libX11.so.4
> #4 0xfee92930 in XFindContext () from /usr/openwin/lib/libX11.so.4
> #5 0xff297e54 in DisplayDestroy () from /usr/dt/lib/libXm.so.4
> #6 0xfefbece0 in XtCallCallbackList () from /usr/openwin/lib/libXt.so.4
> #7 0xfefc486c in XtPhase2Destroy () from /usr/openwin/lib/libXt.so.4
> #8 0xfefc45d0 in _XtDoPhase2Destroy () from /usr/openwin/lib/libXt.so.4
> #9 0xfefc43b4 in XtDestroyWidget () from /usr/openwin/lib/libXt.so.4
> #10 0x15cf9c in x_delete_device (d=0x523f00)
>
> are caused by buggy Motif libraries. Installing the following patches
> has been reported to solve the problem on Solaris 2.7:
>
> 107081-40 107656-07
>
> For information (although they have not been confirmed to work), the
> equivalent patches for Solaris 2.8 are:
>
> 108940-33 108652-25
>
> At 02:08 PM 12/18/2001 -0500, Miller, David M. wrote:
> >Thanks for responding so quickly.
> >
> >I initially didn't notice any patches in PROBLEMS that seemed to apply to
> my
> >environment, but after receiving your reply I tried searching PROBLEMS
> for
> >both 'motif' and for 'patch'. Walking through PROBLEMS with 'isearch',
> >nothing came up which appears to apply.
> >
> >Can you clip the relevant parts of whatever you're referring to and email
> >them to me?
> >
> > > -----Original Message-----
> > > From: Andy Piper [SMTP:andyp＠bea.com]
> > > Sent: Tuesday, December 18, 2001 1:39 PM
> > > To: David M. Miller; xemacs-beta(a)xemacs.org
> > > Subject: Re: XEmacs dumps core upon exiting (sometimes)
> > >
> > > Did you try applying the Motif patches documented in PROBLEMS?
> > >
> > > andy
> > >
> > > At 01:19 PM 12/18/01 -0500, David M. Miller wrote:
> > > >This bug report will be sent to the XEmacs Development Team,
> > > > not to your local site managers!!
> > > >Please write in English, because the XEmacs maintainers do not have
> > > >translators to read other languages for them.
> > > >
> > > >
> > > >Please describe as succinctly as possible:
> > > > - What happened.
> > > > - What you thought should have happened.
> > > > - Precisely what you were doing at the time.
> > > >
> > > >Please also include any C or lisp back-traces that you may have.
> > > >================================================================
> > > >Dear Bug Team!
> > > >
> > > >XEmacs dumps core upon exiting about once every three or more times
> or
> > > >so. My gut tells me this is because of a build error (like say,
> > > >'configure' failed to detect something, or it detected something
> > > >erroneously), but I have nothing tangible on which to base that
> > > >opinion.
> > > >
> > > >A search of the PROBLEMS file produced this (which quickened my pulse
> > > >briefly -- until I read further):
> > > >
> > > > *** On Solaris 2.6, XEmacs dumps core when exiting.
> > > >
> > > > This happens if you're XEmacs is running on the same machine as
> the
> > > X
> > > > server, and the optimized memory transport has been turned on by
> > > > setting the environment variable XSUNTRANSPORT. The crash
> occurs
> > > > during the call to XCloseDisplay.
> > > >
> > > > If this describes your situation, you need to undefine the
> > > > XSUNTRANSPORT environment variable.
> > > >
> > > >which appears NOT to apply in my situation, since I am using
> > > >Hummingbird Exceed on a Windows NT 4.0 SP6 box as my X server. I do
> > > >not have the XSUNTRANSPORT environment variable defined in any case.
> > > >
> > > >Here is a stack dump from gdb:
> > > >
> > > > (gdb) where
> > > > #0 0xef18800c in _libc_kill () from /usr/lib/libc.so.1
> > > > #1 0xa5ae0 in fatal_error_signal ()
> > > > #2 <signal handler called>
> > > > #3 0xef6cd498 in RemoveMatchingEntries () from
> > > /usr/dt/lib/libXm.so.3
> > > > #4 0xef680294 in _XmEnumerateHashTable () from
> > > /usr/dt/lib/libXm.so.3
> > > > #5 0xef6cd5d4 in CleanupOnDisplayClose () from
> > > /usr/dt/lib/libXm.so.3
> > > > #6 0xef41f9a4 in XtCallCallbackList () from
> > > /usr/openwin/lib/libXt.so.4
> > > > #7 0xef428208 in XtPhase2Destroy () from
> > > /usr/openwin/lib/libXt.so.4
> > > > #8 0xef428420 in _XtDoPhase2Destroy () from
> > > /usr/openwin/lib/libXt.so.4
> > > > #9 0xef428630 in XtDestroyWidget () from
> > > /usr/openwin/lib/libXt.so.4
> > > > #10 0x22d8e8 in x_delete_device ()
> > > > #11 0x934f8 in delete_device_internal ()
> > > > #12 0x88a8c in delete_console_internal ()
> > > > #13 0xa7de0 in Fkill_emacs ()
> > > > #14 0xe30cc in Ffuncall ()
> > > > #15 0x7df48 in Fcall_interactively ()
> > > > #16 0xde594 in Fcommand_execute ()
> > > > #17 0xe3100 in Ffuncall ()
> > > > #18 0x785b8 in execute_optimized_program ()
> > > > #19 0x77ee0 in funcall_compiled_function ()
> > > > #20 0xe2fcc in Ffuncall ()
> > > > #21 0x7df48 in Fcall_interactively ()
> > > > #22 0xde594 in Fcommand_execute ()
> > > > #23 0x123054 in execute_command_event ()
> > > > #24 0x123bfc in Fdispatch_event ()
> > > > #25 0x85998 in Fcommand_loop_1 ()
> > > > #26 0xb4788 in condition_case_1 ()
> > > > #27 0x852f8 in command_loop_2 ()
> > > > #28 0xb2c0c in internal_catch ()
> > > > #29 0x854c0 in initial_command_loop ()
> > > > #30 0xa7288 in xemacs_21_4_5_sparc_sun_solaris2_6 ()
> > > > #31 0xa7cc0 in main ()
> > > >
> > > >
> > > >
> > > >================================================================
> > > >
> > > >System Info to help track down your bug:
> > > >---------------------------------------
> > > >
> > > >uname -a: SunOS njefpdap1 5.6 Generic_105181-12 sun4u sparc
> SUNW,Ultra-4
> > > >
> > > >./configure '--without-gcc'
> > > >'--site-prefixes=/home/eqdev/tools:/home/cepstein'
> > > >'--prefix=/home/eqdev/tools/xemacs-21.4.5'
> > > >
> > > >
> > > >XEmacs 21.4.5 "Civil Service" configured for `sparc-sun-solaris2.6'.
> > > >
> > > >
> > > >Compilation / Installation:
> > > > Source code location:
> /home/dmmiller/src/xemacs-21.4.5
> > > > Installation prefix: /home/eqdev/tools/xemacs-21.4.5
> > > > Additional prefixes: /home/eqdev/tools
> /home/cepstein
> > > > Runtime library search
> > > > path:
> > > >
> > >
> /home/eqdev/tools/lib:/home/cepstein/lib:/usr/dt/lib:/usr/openwin/lib:/opt
> > > /SUNWdt/lib
> > > > Operating system description file: `s/sol2.h'
> > > > Machine description file: `m/sparc.h'
> > > > Compiler: cc -v -xO4
> > > > Relocating allocator for buffers: yes
> > > > GNU version of malloc: yes
> > > >
> > > >Window System:
> > > > Compiling in support for the X window system:
> > > > - X Windows headers location: /usr/dt/include
> > > > /usr/openwin/include
> > > > - X Windows libraries location: /usr/dt/lib
> > > > /usr/openwin/lib
> > > > - Handling WM_COMMAND properly.
> > > > Using Lucid menubars.
> > > > Using Lucid scrollbars.
> > > > Using Motif dialog boxes.
> > > > Using Motif native widgets.
> > > >
> > > >TTY:
> > > > Compiling in support for ncurses.
> > > >
> > > >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.
> > > >
> > > >Sound:
> > > > Compiling in support for sound (native).
> > > >
> > > >Databases:
> > > > Compiling in support for DBM.
> > > >
> > > >Internationalization:
> > > >
> > > >Mail:
> > > > Compiling in support for "dot-locking" mail spool file locking
> method.
> > > >
> > > >Other Features:
> > > > Compiling in support for ToolTalk.
> > > > Compiling in support for dynamic shared object modules.
> > > >
> > > >
> > > >
> > > >Load-Path Lisp Shadows:
> > > >----------------------
> > > >(/home/dmmiller/.xemacs/tempo
> > >
> >/home/eqdev/tools/xemacs-21.4.5/lib/xemacs/xemacs-packages/lisp/edit-util
> > > s/tempo
> > > >/home/dmmiller/.xemacs/background
> > >
> >/home/eqdev/tools/xemacs-21.4.5/lib/xemacs/xemacs-packages/lisp/os-utils/
> > > background
> > > >/home/dmmiller/.xemacs/sql
> > >
> >/home/eqdev/tools/xemacs-21.4.5/lib/xemacs/xemacs-packages/lisp/prog-mode
> > > s/sql
> > > >/home/dmmiller/.xemacs/custom
> > > >/home/eqdev/tools/xemacs-21.4.5/lib/xemacs-21.4.5/lisp/custom)
> > > >
> > > >
> > > >Installed XEmacs Packages:
> > > >-------------------------
> > > >
> > > >((zenirc:version 1.11 :type regular)
> > > > (xslt-process :version 1.05 :type regular)
> > > > (xemacs-devel :version 1.38 :type single-file)
> > > > (xemacs-base :version 1.55 :type regular)
> > > > (w3 :version 1.2 :type regular)
> > > > (vm :version 6.96 :type regular)
> > > > (viper :version 1.28 :type regular)
> > > > (view-process :version 1.11 :type regular)
> > > > (vhdl :version 1.13 :type regular)
> > > > (vc-cc :version 1.16 :type regular)
> > > > (vc :version 1.28 :type regular)
> > > > (tpu :version 1.12 :type regular)
> > > > (tooltalk :version 1.13 :type regular)
> > > > (tm :version 1.29 :type regular)
> > > > (time :version 1.11 :type regular)
> > > > (textools :version 1.12 :type regular)
> > > > (text-modes :version 1.32 :type single-file)
> > > > (texinfo :version 1.2 :type regular)
> > > > (supercite :version 1.18 :type regular)
> > > > (strokes :version 1.08 :type regular)
> > > > (speedbar :version 1.21 :type regular)
> > > > (sounds-wav :version 1.1 :type regular)
> > > > (sounds-au :version 1.1 :type regular)
> > > > (slider :version 1.13 :type regular)
> > > > (sh-script :version 1.13 :type regular)
> > > > (sgml :version 1.08 :type regular)
> > > > (semantic :version 1.1 :type regular)
> > > > (scheme :version 1.11 :type regular)
> > > > (rmail :version 1.12 :type regular)
> > > > (reftex :version 1.23 :type regular)
> > > > (psgml :version 1.23 :type regular)
> > > > (ps-print-nomule :version 1.05 :type regular)
> > > > (prog-modes
> > > > :version
> > > > 1
> > > > .42
> > > > :type
> > > > single-file)
> > > > (pcomplete :version 1.01 :type regular)
> > > > (pcl-cvs :version 1.55 :type regular)
> > > > (pc :version 1.2 :type single-file)
> > > > (os-utils :version 1.25 :type single-file)
> > > > (net-utils :version 1.23 :type single-file)
> > > > (misc-games :version 1.15 :type single-file)
> > > > (mine :version 1.14 :type regular)
> > > > (mh-e :version 1.13 :type regular)
> > > > (mew :version 1.14 :type regular)
> > > > (mailcrypt :version 2.09 :type regular)
> > > > (mail-lib :version 1.39 :type regular)
> > > > (ispell :version 1.23 :type regular)
> > > > (ilisp :version 1.19 :type regular)
> > > > (igrep :version 1.08 :type regular)
> > > > (idlwave :version 1.23 :type regular)
> > > > (hm--html-menus :version 1.16 :type regular)
> > > > (gnus :version 1.57 :type regular)
> > > > (gnats :version 1.12 :type regular)
> > > > (games :version 1.13 :type regular)
> > > > (fsf-compat :version 1.09 :type single-file)
> > > > (frame-icon :version 1.09 :type regular)
> > > > (forms :version 1.13 :type regular)
> > > > (footnote :version 1.13 :type regular)
> > > > (eudc :version 1.34 :type regular)
> > > > (eterm :version 1.13 :type regular)
> > > > (eshell :version 1.01 :type regular)
> > > > (emerge :version 1.09 :type regular)
> > > > (elib :version 1.08 :type single-file)
> > > > (eieio :version 1.01 :type regular)
> > > > (efs :version 1.26 :type regular)
> > > > (edt :version 1.12 :type regular)
> > > > (edit-utils :version 1.7 :type single-file)
> > > > (ediff :version 1.33 :type regular)
> > > > (edebug :version 1.14 :type regular)
> > > > (dired :version 1.11 :type regular)
> > > > (debug :version 1.14 :type regular)
> > > > (crisp :version 1.12 :type regular)
> > > > (cookie :version 1.13 :type regular)
> > > > (cc-mode :version 1.26 :type regular)
> > > > (calendar :version 1.16 :type regular)
> > > > (calc :version 1.17 :type regular)
> > > > (c-support :version 1.16 :type single-file)
> > > > (build :version 1.02 :type regular)
> > > > (bbdb :version 1.16 :type regular)
> > > > (auctex :version 1.25 :type regular)
> > > > (apel :version 1.2 :type regular)
> > > > (ada :version 1.1 :type regular))
> > > >
> > > >
> > > >Features:
> > > >--------
> > > >
> > > >(mail-abbrevs xemacsbug shadow sendmail efs-netrc view-less view font
> > > >disp-table popper advice advice-preload icomplete balloon-help paren
> > > >blink-paren savehist outline cperl-mode fast-lock desktop sql-test
> > > >sql-mode scroll-in-place comint ring recent-files time rsz-minibuf
> > > >func-menu font-lock filladapt crypt crypt++ completer efs-cu
> > > >efs-x19.15 efs-fnh efs-ovwrt efs-auto cus-face dired-faces
> > > >dired-xemacs dired pending-del edmacro zenirc-autoloads
> > > >xslt-process-autoloads xemacs-devel-autoloads xemacs-base-autoloads
> > > >w3-autoloads vm-autoloads viper-autoloads view-process-autoloads
> > > >vhdl-autoloads vc-cc-autoloads vc-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 slider-autoloads sh-script-autoloads
> > > >sgml-autoloads semantic-autoloads scheme-autoloads rmail-autoloads
> > > >reftex-autoloads psgml-autoloads ps-print-nomule-autoloads
> > > >prog-modes-autoloads pcomplete-autoloads pcl-cvs-autoloads
> > > >pc-autoloads os-utils-autoloads net-utils-autoloads
> > > >misc-games-autoloads mine-autoloads mh-e-autoloads mew-autoloads
> > > >mailcrypt-autoloads mail-lib-autoloads ispell-autoloads
> > > >ilisp-autoloads igrep-autoloads idlwave-autoloads
> > > >hm--html-menus-autoloads gnus-autoloads gnats-autoloads
> > > >games-autoloads fsf-compat-autoloads frame-icon-autoloads
> > > >forms-autoloads footnote-autoloads eudc-autoloads eterm-autoloads
> > > >eshell-autoloads emerge-autoloads elib-autoloads eieio-autoloads
> > > >efs-autoloads edt-autoloads edit-utils-autoloads ediff-autoloads
> > > >edebug-autoloads dired-autoloads debug-autoloads crisp-autoloads
> > > >cookie-autoloads cc-mode-autoloads calendar-autoloads calc-autoloads
> > > >c-support-autoloads build-autoloads bbdb-autoloads auctex-autoloads
> > > >apel-autoloads ada-autoloads lisp-autoloads loadhist auto-show
> > > >fontl-hooks x-iso8859-1 gutter-items menubar-items x-menubar
> > > >mode-motion mouse itimer auto-save lisp-mode easymenu iso8859-1 page
> > > >buff-menu lib-complete help-nomule cus-file derived frame text-props
> > > >obsolete cus-start custom widget cl-extra mini-cl cl cl-19 packages
> > > >backquote very-early-lisp tooltalk lucid-scrollbars cut-buffer
> > > >lucid-menubars motif-dialogs x c-balloon-help tty-frames tty toolbar
> > > >native-sound scrollbar unix-processes multicast network-streams
> > > >subprocesses modules menu-accelerator-support menubar dbm md5 xemacs
> > > >gutter png gif jpeg xpm xbm lisp-float-type usg-unix-v dialog devices
> > > >window-system base64)
>
>
>
_____________________________________________________________________
IMPORTANT NOTICES:
This message is intended only for the addressee. Please notify the
sender by e-mail if you are not the intended recipient. If you are not the
intended recipient, you may not copy, disclose, or distribute this message
or its contents to any other person and any such actions may be unlawful.
Banc of America Securities LLC("BAS") does not accept time
sensitive, action-oriented messages or transaction orders, including orders
to purchase or sell securities, via e-mail.
BAS reserves the right to monitor and review the content of all
messages sent to or from this e-mail address. Messages sent to or from this
e-mail address may be stored on the BAS e-mail system.
- 2 participants
- 1 comments
RE: [Proposed Patch] button2 on ISO8:T in modeline toggles eol ty pe
22 years, 11 months
Wedler, Christoph
Wedler, Christoph
Yoshiki Hayashi [yoshiki(a)xemacs.org]:
> "Wedler, Christoph" <christoph.wedler(a)sap.com> writes:
>> >> 1. Use the above appended list
>> >> 2. Open a new file foo.txt with two line of "ab".
>> >> 3. You see the modeline is still "ISO8" (and
>> >> `buffer-file-coding-system' is iso-2208-8), but this would be
>> >> acceptable, although not nice (since I also see ISO8 for Unix
>> >> endings and ISO8:T for dos)
>> >> 4. Save the buffer, the length is 6 bytes (i.e., Unix endings)
>> >> 5. Kill the buffer, re-read it.
>> >> 6. Modeline ISO8:T, and `buffer-file-coding-system' is
#<coding_system
>> >> iso-2022-8-dos> -- huh?
>> >> 7. delete your entry from file-coding-system-alist
>> >> 8. Kill the buffer, re-read it.
>> >> 9. Modeline ISO8, and `buffer-file-coding-system' is #<coding_system
iso-2022-8-unix>
>>
>> > Did you try this?
>> > (setq-default default-buffer-file-coding-system 'iso-8859-1-dos)
>>
>> Yes, it's better that it really write files with dos endings (i.e, 4
>> above is OK now), but when reading files with unix eol type, the buffer
>> has a coding system with dos eol type (i.e., 6 is still strange).
> Then you found a bug in file-coding XEmacs.
Well, it doesn't contradict the docstring of
default-buffer-file-coding-system:
Default value of `buffer-file-coding-system' for buffers that do not
override it. This is the same as (default-value
'buffer-file-coding-system). This value is used both for buffers
without associated files and for buffers whose files do not have any
apparent coding system.
If you set `default-buffer-file-coding-system' to `iso-2022-8-dos' and
visit a Unix file with ASCII-only characters, this file doesn't probably
have a "apparent coding system", that's why the corresponding is
`#<coding_system iso-2022-8-dos>'.
The eol type of the file is apparent, but not the whole coding system.
If the two properties "base" and "eol type" should be considered
independently, this should be mentioned in the docstring, and the
current behaviour of XEmacs should be considered wrong as you've said.
> It does work with MULE XEmacs.
Maybe XEmacs-21.5.X, but not on the following:
./configure '--with-png=no' '--site-includes=/sapmnt/hw1020/a/include'
'--site-libraries=/sapmnt/hw1020/a/lib' '--with-mule'
XEmacs 21.4.5 "Civil Service" configured for `hppa1.1-hp-hpux11.00'.
>> [...] eol type nil means:
>> (1) when reading: XEmacs tries to guess the correct eol type
>> (2) when writing: XEmacs uses its internal eol type which is unix' one.
>>
>> I definitely want to have (1), that is, no, I don't want to set a
>> variable which uses a specific eol type to read a file.
>>
>> But there is no auto-guess functionality when saving the buffer. That
>> is I want to say that eol type nil can also mean dos or mac when writing
>> the file.
> XEmacs should not attempt to auto-guess EOL when saving buffer and
> should never be. It uses whatever the value of
> buffer-file-coding-system. EOL type nil is not auto-guess in this
> case but means LF for new file.
Err, yes... The wording in my previous message wasn't good: I just
wanted to say (in the section starting with "But there is no..." and in
earlier messages) that it would be useful to be able to customize that
eol type nil when saving can mean CRLF (or CR) instead of LF.
> If it is not a new file, you can't have EOL type nil in that buffer.
Exactly. That's why I always talked about new files when arguing why
toggling from eol type nil is useful...
> I thought we are talking about your proposal of future enhancement.
Except for the above mentioned variable ("able to customize"), I didn't
mention any others.
> I'm not specifically talking about your patch.
Well, this is exactly my problem. Toggling from eol type nil in a
buffer is specific to that patch, people vetoed that feature and when I
asked "why?", people start talking about something else (if there was an
answer at all).
That's why I got annoyed. Sorry that it sounded like I was specific
annoyed with your answer.
> I think no one has commented on your patch so far.
Err, some people vetoed the feature "toggling from eol type nil in a
buffer"[1] and some agreed with the veto. Before sending a patch, it
would be useful to get a reason for that or that they take the veto back
(otherwise I put work in a patch which will be vetoed).
[1] To which one should be customizable (I already agreed on that)
- Christoph
- 3 participants
- 2 comments