June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [bug] grep/compile process exits immediately 26 years, 6 months

Hrvoje Niksic

greg(a)alphatech.com (Greg Klanderman) writes: > I've been seeing this for quite some time and recall Hrvoje > submitting a patch once that sounded like it was supposed to fix > this. My patch only reversed a change done by Kirill which introduced the bug. If it is in fact a "deeper" bug, then my patch did nothing to fix it. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Try to use "ad nauseam" at least once per flame. It doesn't mean anything; but it gives that polished feel to your postings.

2 participants
1 comments

Re: Patches & MIME 26 years, 6 months

Oliver Graf

Darryl Okahata <darrylo(a)sr.hp.com> writes: > I took a look at my mailer (mh-e), and my patches are being sent > out as application/octet-stream instead of text/plain due to bugs in TM. > I'll fix this in a day or two and submit patches (which I realize > probably won't make it into 21.0). Perhaps mh-e, tm, or whatever module of XEmacs is reponsible should do a bit file-magic and guess the type of the file to use the correct MIME type. This part is also of interest for me, cause Drag'n'Drop *will* use MIME types for transfer. Perhaps we can cooperate (who is responsible for the encoding-guess of the mail sender?) and create something that is a bit smarter in with the MIME-guess? Regards, Oliver.

2 participants
1 comments

Re: Patches & MIME 26 years, 6 months

Jan Vroonhof

Darryl Okahata <darrylo(a)sr.hp.com> writes: > (e.g., base64 -- as I and others mistakenly inferred), but that the MIME > type and subtype are typically "application/octet-stream", Note that TM encodes patches as "application/octet-stream" , type=patch. Now I don't know the mime standard but it seems to me as correct. patch files are really input files to the patch program. That they are also human readabble is accidental :-). I am all in favor of make things more convenient for Ben but it seems to me one should not go out and fix TM for bugs it doesn't contain[1]. It would be better to find another (local) solution to our problem if TM's behaviour complies with the MIME standard. Jan

2 participants
1 comments

[Success] 21.0 "Somali" XEmacs Lucid (beta42) on i586-fga-linux 26 years, 6 months

Oliver Graf

Patched up from b41. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/src/xemacs-21.0-b41/Installation: > (Output from most recent run of ./configure) uname -a: Linux indie.fga-intern.de 2.0.33 #5 Fri May 1 22:23:24 MEST 1998 i586 unknown ./configure 'i586-fga-linux' '--prefix=/usr/local/xemacs' '--gung-ho' '--use-union-type' '--with-mule' '--with-scrollbars=athena3d' '--with-dialogs=athena3d' '--with-menubars=lucid' XEmacs 21.0-b42 "Somali" configured for `i586-fga-linux'. Where should the build process find the source code? /usr/src/xemacs-21.0-b41 What installation prefix should install use? /usr/local/xemacs What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for OffiX. Compiling in EXPERIMENTAL support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /usr/src/xemacs-21.0-b41/beta.err does not exist!

1 participants
0 comments

[bug] grep/compile process exits immediately 26 years, 6 months

Greg Klanderman

I've been seeing this for quite some time and recall Hrvoje submitting a patch once that sounded like it was supposed to fix this. Anyway, occasionally grep or compile will fail immediately with a failed exit status. If I try again, it always works. I have not been able to reproduce it. Anyone else seeing this? greg

1 participants
0 comments

[bug] lpr-region signals void-variable: buffer-file-type 26 years, 6 months

Greg Klanderman

in b42, xemacs -q, highlight a region, and M-x lpr-region: Signaling: (void-variable buffer-file-type) print-region-1(200 216 nil nil) lpr-region(200 216) call-interactively(lpr-region) command-execute(lpr-region t) execute-extended-command(nil) call-interactively(execute-extended-command) I'm not sure what the right solution is. greg

1 participants
0 comments

Re: Patches & MIME 26 years, 6 months

Hrvoje Niksic

Darryl Okahata <darrylo(a)sr.hp.com> writes: > text is not displayed to the user). For patches, encoding such as > base64 is fine, but the MIME type/subtype should be something like > "text/plain" instead of "application/octet-stream". He says that > this is really a bug in gnus. Ben is wrong, because Gnus doesn't support MIME. It is a bug in TM (the add-on MIME support package for Gnus), if anywhere. TM was written by Tomohiko Morioka, not by Lars Ingebrigtsen. > I took a look at my mailer (mh-e), and my patches are being sent out > as application/octet-stream instead of text/plain due to bugs in TM. > I'll fix this in a day or two and submit patches (which I realize > probably won't make it into 21.0). I don't know how much code you plan to touch, but this change looks like a definite bugfix to me. But then again, I'm not a TM user, so I can't really tell. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Jone's law: The man who smiles when things go wrong has thought of someone to blame it on.

1 participants
0 comments

Patches & MIME 26 years, 6 months

Darryl Okahata

Ben Wing wrote: > patches in text/plain! > kyle, your bot should reject patches that aren't. [ Ben recently sent me an audio message describing the problem in more detail, and asked me to send a suggestion to Kyle. ] Ben's complaint is not about MIME and/or the MIME encoding (e.g., base64 -- as I and others mistakenly inferred), but that the MIME type and subtype are typically "application/octet-stream", which his mailreader can't (easily) handle (it's marked as an attachment, and the text is not displayed to the user). For patches, encoding such as base64 is fine, but the MIME type/subtype should be something like "text/plain" instead of "application/octet-stream". He says that this is really a bug in gnus. I took a look at my mailer (mh-e), and my patches are being sent out as application/octet-stream instead of text/plain due to bugs in TM. I'll fix this in a day or two and submit patches (which I realize probably won't make it into 21.0). Ben also suggests that Kyle's patchbot be modified to automatically translate incoming application/octet-stream to text/plain (if appropriate). -- Darryl Okahata Internet: darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

1 participants
0 comments

Re: XEmacs 21.0-beta42 "Somali" is released 26 years, 6 months

Mark Borges

>> On Wed, 03 Jun 1998 08:51:10 +0100, >> Andy Piper(AP) wrote: AP> At 10:39 PM 6/2/98 -0700, SL Baur wrote: >> The newer version Hrvoje has is: >> >> /* >> * This define can be used in code that requires >> * compilation-related definitions specific to a >> * version or versions of the library. Runtime >> * version checking should be done based on the >> * string returned by TIFFGetVersion. >> */ >> #define TIFFLIB_VERSION 19970127 /* January 27, 1997 */ AP> I have this version and tiff builds and runs just fine for me AP> (under mswindows!) I think I have b39 and I have never noticed any AP> problem with it. Same here, under Solaris-2.5. What are we doing wrong to make it apparently work? Is there some stress test I can do to see if it *really* works? -- -mb-

1 participants
0 comments

Mouse cursor switched in customize buffer 26 years, 6 months

David Bush

This in on Cygwin_95, b42, no X11 The mouse cursors are switched in the customize buffer. I was in teh Faces customize option in this case. The cursor is an Ibeam over selectable items and the up-left arrow everyplace else. david

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