July 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: return value of gettext() needs to be MULE-converted? 24 years, 5 months

Gunnar Evermann

Ben Wing <ben(a)666.com> writes: > Hrvoje Niksic wrote: > > Obviously noone thought about strerror() returning non-ASCII stuff. > > The correct way to write the above would be something like: > > > > Bufbyte *internal_strerror; > > TO_INTERNAL_FORMAT (C_STRING, strerror (saverrno), > > C_STRING_ALLOCA, internal_strerror, > > Qnative); > > > > error ("IO error reading %s: %s", > > XSTRING_DATA (filename), internal_strerror); > > > > Even better, the code should be modified to use report_file_error() or > > one of its relatives (if possible.) > ok, i fixed this bug in my mule workspace. I didn't see this fix in your last mega-patch. Do you still have it in your workspace? Just trying to make sure we don't lose any patches... Gunnar

2 participants
1 comments

Object printing broken 24 years, 5 months

Andy Piper

After the latest round of patches gdb now SEGV's on me if I try and print out lisp objects - e.g. doing ldp when I have loaded .gdbinit. I have no idea what the cause might be, but it worked fairly recently and its pretty annoying when you are trying to debug stuff. Hmm, ok this fixes it: 2000-07-29 Andy Piper <andy(a)xemacs.org> * print.c (debug_print_no_newline): only write to debugger if in WIN32_NATIVE. andy -------------------------------------------------------------- Dr Andy Piper Principal Consultant, BEA Systems Ltd

1 participants
0 comments

Re: Reproducible core dump in 21.1.10 24 years, 5 months

Gunnar Evermann

Ben Wing <ben(a)666.com> writes: > ok, try this: [for 21.1]: > > 2000-07-04 Ben Wing <ben(a)xemacs.org> > > * symbols.c (Fmapatoms): gcpro obarray, may be new (debug-continue). > (Fapropos_internal): consing + call1 = must gcpro. yes, this fixes it (of course). thanks for applying the patch. Gunnar

1 participants
0 comments

Re: 21.2.35, file name completion and ccase 24 years, 5 months

Raymond Toy

>>>>> "Raymond" == Raymond Toy <toy(a)rtp.ericsson.se> writes: Raymond> I've been using ccase.el with 21.2.34 without any real problems for a Raymond> couple of weeks. (Very nice!) Raymond> However, it doesn't work so well with 21.2.35 now. Raymond> The major problem thus far is that file name completion doesn't work Raymond> very well at all. Raymond> With 21.2.34 I could do filename completion with view tags just fine. Raymond> Now 21.2.35 does weird things. C-x C-f /view/<viewtag>/ <TAB> is ok Raymond> (where <viewtag> is some view tag). If I continue with Raymond> /view/<viewtag>/v and press TAB, I get a beep and the cursor moves Raymond> back to just after /view. In 21.2.34, this would complete correctly Raymond> to /view/<viewtag>/vobs. Raymond> Since the only difference is that I've upgraded to 21.2.35, I assume Raymond> the problem is due to some change in filename completion in 21.2.35? Well, recompiling ccase.el with 21.2.35 seems to have fixed this problem. Ray

2 participants
1 comments

Re: The need for a new XEmacs NT binary 24 years, 5 months

Kirill 'Big K' Katsnelson

Some time ago, Sandra Wambold wrote... > From what I understand, we have a new version that solves the "won't >start on some machines" problem, but we don't have a binary for it. >(Please correct me if I'm wrong). If I am not mistaken, the non-starting problem has to do with driver DLLs smuggled by the system into the address space of the process, so that the heap cannot be recreated at the same address as it was dumped from. This problem has no cure, except for the portable dumper, which, IMO, works more or less (please correct me if I am wrong again; I spent more time outside xemacs lately). Question for which I am crossposting this to xemacs-beta: what's up with the portable dumper? Last time I tried it, there was no definitive algorithm for locating the xemacs.dmp file; when I grepped through my beta mailbox starting from March, I found nothing relevant (unventive regexp?). -kkm

1 participants
0 comments

21.2.35, file name completion and ccase 24 years, 5 months

Raymond Toy

I've been using ccase.el with 21.2.34 without any real problems for a couple of weeks. (Very nice!) However, it doesn't work so well with 21.2.35 now. The major problem thus far is that file name completion doesn't work very well at all. With 21.2.34 I could do filename completion with view tags just fine. Now 21.2.35 does weird things. C-x C-f /view/<viewtag>/ <TAB> is ok (where <viewtag> is some view tag). If I continue with /view/<viewtag>/v and press TAB, I get a beep and the cursor moves back to just after /view. In 21.2.34, this would complete correctly to /view/<viewtag>/vobs. Since the only difference is that I've upgraded to 21.2.35, I assume the problem is due to some change in filename completion in 21.2.35? Ray

1 participants
0 comments

Re: widget-url-link-action 24 years, 5 months

Per Abrahamsen

A similar change is already in Emacs, apparently without problems, so I cannot see any reason not to apply Kenichi Okada's patch.

1 participants
0 comments

RE: 21.1.11: XEmacs cannot start ... 24 years, 5 months

Alastair Houghton

> I looked through the make file and didn't see any additional options. I > know the 21.2 tree has the portable dumper code in it, could that be what > you were thinking of? Yep. That's it exactly. I think the portable dumper's supposed to fix this problem - but I've never actually tried using it (or needed to use it) so I don't know for certain. [from the other e-mail] > I guess the bottom line for everyone waiting for a 21.1.11 binary build to > fix their "It wont start" problem is you aren't really any closer > to having > a working installation, but now it will tell you you're hosed instead of > silently dying. :( Yep. But silently dying is much much worse, because it leaves people with the impression that the program doesn't work at all, whereas in reality, it just doesn't work when built on someone else's machine. > Yes, it is NT 4 SP 5. I saw an experimental patch of yours to try and tell > what the offending dll is, I'll try to compile it in this evening and test > it tomorrow on the broken machine. Don't hold your breath. It looked to me like your memory region wasn't part of a module (i.e. DLL or EXE) - but it could still work I suppose. I'm not entirely certain that what I did in that patch is safe, which is why it's "experimental"; I think it probably is, but it's certainly undocumented... Kind regards, Alastair. ____________________________________________________________ Alastair Houghton ajhoughton(a)lineone.net

1 participants
0 comments

Re: [jgd@lanl.gov] I think the xemacs FTP package directory is fouled up... 24 years, 5 months

Dan Holmsand

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Hi Jan, Dan, Michael! > > I have tested as suggested by Michael and am delighted to report success. > > I intend to commit this against release-21-2 CVS shortly: I also gave it a quick try. Works great here too! /dan -- Dan Holmsand dan(a)innehall.com

1 participants
0 comments

Re: [jgd@lanl.gov] I think the xemacs FTP package directory is fouled up... 24 years, 5 months

Adrian Aichner

>>>>> "Jan" == Jan Vroonhof <jan.vroonhof(a)insignia.com> writes: Jan> Dan Holmsand <dan(a)innehallsbolaget.com> writes: >> > http://www.xemacs.org/list-archives/xemacs-patches/199906/msg00050.html >> >> OK, I see. Btw there seems to be a typo in the patch: it says >> coding-system-for-read twice in the let clause. Fsfmacs has >> coding-system-for-write the second time. Jan> Thank you. It should be changed. It shouldn't matter though Jan> as this we are supposed to be doing only reading. Hi Jan, Dan, Michael! I have tested as suggested by Michael and am delighted to report success. I intend to commit this against release-21-2 CVS shortly: Gotta shatter that perception of being a shy guy ;-> I intend to apply and test this against 21.1.11 as well since this is a showstopper AFAIAC. Best regards, Adrian lisp/ChangeLog: 2000-07-28 Adrian Aichner <aichner(a)ecf.teradyne.com> * files.el (insert-file-contents-literally): Fix second let binding for `coding-system-for-read' to `coding-system-for-write' as suggested by Dan Holmsand <dan(a)innehallsbolaget.com>. 1999-06-15 Jan Vroonhof <vroonhof(a)math.ethz.ch> * files.el (insert-file-contents-literally): Use binary coding system (from Morioka san). (insert-file-contents-literally): Make file-name-handler method. top-level patch: cd d:\tmp\21.2\xemacs\ cvs diff lisp/files.el Compilation started at Fri Jul 28 15:22:11 2000 +0200 (W. Europe Daylight Time) Index: lisp/files.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/files.el,v retrieving revision 1.27.2.23 diff -u -r1.27.2.23 files.el --- files.el 2000/06/30 08:44:10 1.27.2.23 +++ files.el 2000/07/28 13:27:07 ＠＠ -873,23 +873,31 ＠＠ (defun insert-file-contents-literally (filename &optional visit beg end replace) "Like `insert-file-contents', q.v., but only reads in the file. A buffer may be modified in several ways after reading into the buffer due -to advanced Emacs features, such as file-name-handlers, format decoding, -find-file-hooks, etc. +to advanced Emacs features, such as format decoding, character code +conversion,find-file-hooks, automatic uncompression, etc. + This function ensures that none of these modifications will take place." - (let ((file-name-handler-alist nil) - (format-alist nil) - (after-insert-file-functions nil) - (find-buffer-file-type-function - (if (fboundp 'find-buffer-file-type) - (symbol-function 'find-buffer-file-type) - nil))) - (unwind-protect - (progn - (fset 'find-buffer-file-type (lambda (filename) t)) - (insert-file-contents filename visit beg end replace)) - (if find-buffer-file-type-function - (fset 'find-buffer-file-type find-buffer-file-type-function) - (fmakunbound 'find-buffer-file-type))))) + (let ((wrap-func (find-file-name-handler filename + 'insert-file-contents-literally))) + (if wrap-func + (funcall wrap-func 'insert-file-contents-literally filename + visit beg end replace) + (let ((file-name-handler-alist nil) + (format-alist nil) + (after-insert-file-functions nil) + (coding-system-for-read 'binary) + (coding-system-for-write 'binary) + (find-buffer-file-type-function + (if (fboundp 'find-buffer-file-type) + (symbol-function 'find-buffer-file-type) + nil))) + (unwind-protect + (progn + (fset 'find-buffer-file-type (lambda (filename) t)) + (insert-file-contents filename visit beg end replace)) + (if find-buffer-file-type-function + (fset 'find-buffer-file-type find-buffer-file-type-function) + (fmakunbound 'find-buffer-file-type))))))) (defun find-file-noselect (filename &optional nowarn rawfile) "Read file FILENAME into a buffer and return the buffer. Compilation exited abnormally with code 1 at Fri Jul 28 15:22:22 Jan> Jan -- Adrian Aichner <adrian(a)xemacs.org>

1 participants
0 comments

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 July 2000