June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: WAV support under linux - odd file (was Re: Patches & MIME) 26 years, 6 months

William M. Perry

sperber(a)Informatik.Uni-Tuebingen.De (Michael Sperber [Mr. Preprocessor]) writes: > >>>>> "BP" == William M Perry <wmperry(a)aventail.com> writes: > > BP> Ben Wing <ben(a)666.com> writes: > > >> [3 19980604-1-gsm-8k.wav <audio/x-wav>] > > BP> Was anybody able to play this wav file through XEmacs? I get the error: > > BP> audio: Unsupported file format (neither RAW, nor Sun/DECAudio, nor WAVE > > BP> but according to 'file', it is: > > BP> /tmp/19980604-1-gsm-8k.wav: Microsoft RIFF, WAVE audio data, mono 8000 Hz > > BP> This is under linux w/b42 > > It's a special encoding (GSM) of the frames of the WAV file. Under > Linux, you should probably play the RealAudio attachment with RealAudio. Yup - done... just wondering if this was a bug we could fix. :) -Bill P.

1 participants
0 comments

Re: WAV support under linux - odd file (was Re: Patches & MIME) 26 years, 6 months

Michael Sperber

>>>>> "BP" == William M Perry <wmperry(a)aventail.com> writes: BP> Ben Wing <ben(a)666.com> writes: >> [3 19980604-1-gsm-8k.wav <audio/x-wav>] BP> Was anybody able to play this wav file through XEmacs? I get the error: BP> audio: Unsupported file format (neither RAW, nor Sun/DECAudio, nor WAVE BP> but according to 'file', it is: BP> /tmp/19980604-1-gsm-8k.wav: Microsoft RIFF, WAVE audio data, mono 8000 Hz BP> This is under linux w/b42 It's a special encoding (GSM) of the frames of the WAV file. Under Linux, you should probably play the RealAudio attachment with RealAudio. For playing the WAV attachment, I use XAnim as suggested by Ben. http://xanim.va.pubnix.com/home.html http://smurfland.cit.buffalo.edu/xanim/home.html -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Info warnings 26 years, 6 months

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: >> >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: >> Hrvoje> OK, for quite a few betas Info has been pretty insistent Hrvoje> in throwing warnings in my face. I was kind of hoping Hrvoje> this would be resolved, so I stayed silent. However, it Hrvoje> is not getting solved, so I have to speak up. >> >> The subject has been discussed for a while some time ago. I made >> some changes according to the state that discussion was left and >> since nobody complained, I assumed that everybody accepted the >> current behaviour. Hrvoje> You certainly haven't made changes according to my suggestions, Hrvoje> because I surely wanted the warning to go away, and so did Jan and Hrvoje> Chipsy. Exactly. I only didn't speak up because I hadn't used Info in quite a while, as I now notice. I'll reiterate: The concept of "dir" files is broken. The current behavior amounts to telling the user something she already knows on every single startup. Options: - If we don't consider "dir" files broken, then XEmacs should always use the dir files which are there without complaining. - If we do, XEmacs should always rebuild on the fly, again without complaining. Just to make it clear again, I'd prefer the latter. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

WAV support under linux - odd file (was Re: Patches & MIME) 26 years, 6 months

William M. Perry

Ben Wing <ben(a)666.com> writes: > [3 19980604-1-gsm-8k.wav <audio/x-wav>] Was anybody able to play this wav file through XEmacs? I get the error: audio: Unsupported file format (neither RAW, nor Sun/DECAudio, nor WAVE but according to 'file', it is: /tmp/19980604-1-gsm-8k.wav: Microsoft RIFF, WAVE audio data, mono 8000 Hz This is under linux w/b42 -Bill P.

1 participants
0 comments

Re: Info warnings 26 years, 6 months

Hrvoje Niksic

Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: > >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: > > Hrvoje> OK, for quite a few betas Info has been pretty insistent > Hrvoje> in throwing warnings in my face. I was kind of hoping > Hrvoje> this would be resolved, so I stayed silent. However, it > Hrvoje> is not getting solved, so I have to speak up. > > The subject has been discussed for a while some time ago. I made > some changes according to the state that discussion was left and > since nobody complained, I assumed that everybody accepted the > current behaviour. You certainly haven't made changes according to my suggestions, because I surely wanted the warning to go away, and so did Jan and Chipsy. > Hrvoje> The warning is this: > > Hrvoje> (1) (info/notice) Outdated info dir file: /usr/local/info/dir > > This is not strictly a warning but a notice. But it is flashed in my face and I have to press C-x 1 every time I see it. This is more serious than you might think. Warnings should *never* be flashed without a good reason for them, or the users will learn to ignore them. > Hrvoje> Of course, I don't even have permission to modify the > Hrvoje> /usr/local/info/dir file, and neither has any of the users > Hrvoje> on the machine I run XEmacs on. So, the warning will be > Hrvoje> seen by all of them, and likely many more of our users in > Hrvoje> the world. What is the *purpose* of this warning, anyway? > Hrvoje> Warnings should inform the user of a condition he/she > Hrvoje> should remedy. > > Your not having the right to overwrite that file at the moment you > run Info does not mean you can not acquire that right. ????????????????????? How do you expect me to be able to write to /usr/local/info/dir?! I run XEmacs on a multi-user machine, for Christ's sake! > - set `Info-rebuild-outdated-dir' to `never' or `always' > - set `display-warning-minimum-level' to 'warning > - set `display-warning-suppressed-classes' to '(info) I don't want to do either of these things. I want the warning to go away. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Oh lord won't you buy me a color TV...

1 participants
0 comments

Re: Patches & MIME 26 years, 6 months

Hrvoje Niksic

Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: > I agree however that TM should provide a means to display > application/octet-stream typed attachments as text on user request > (what I currently do in Gnus is toggle MIME processing on and off > with 'W m'). This is totally irrelevant because Ben (and a bunch of other people) are not using TM at all. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- I'm a Lisp variable -- bind me!

1 participants
0 comments

Samle.emacs still contains ange-ftp setup 26 years, 6 months

David Bush

I don't feel qualified to proppose an actual change, but if ange-ftp is depricated in favor of efs, does it make sense to have ange-ftp setup support in the Sample.emacs file? My view of such files is that it is for new users and new installations which ought not have the older package. david

1 participants
0 comments

Re: Patches & MIME 26 years, 6 months

Oscar Figueiredo

>>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: >>>>> "Oscar" == Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: Oscar> I have the same comment as Jan Vroonhof: patch files having an Oscar> application/octet-stream type is not a bug it's definitely a feature. Patch Oscar> files are input for the patch program not plain text. Michael> Input for the patch program *is* plain text. As long as it has been generated by diff with intent to feeding patch with it, it is not, it happens to be readable that's all. text/plain is subject to modifications by the MUA which is definitely not what you want for patches. You should get advice on the question from Tomohiko Morioka who certainly is the more competent in the field and who has precise references to give you on the subject. Michael> More specifically, patches sent to xemacs-patches are *primarily* Michael> text because someone needs to read them before patch ever gets to Michael> chew on them. Yes we need to read patches but tagging them as text/plain is not the right way to achieve that. Oscar

1 participants
0 comments

Strange baloon help behavior followed by crash 26 years, 6 months

David Bush

Balloon help got itself in a very strange state and started displaying as Windows dialogs rather than the simple yellow background boxes. I think the context is important so here's a little background. There were about 6 Xemacs windows up. Also Adobe Framemaker, a telnet emulator from Netmanage, and the Cygwin bash window. The toolbar has been moved to the left side to avoid the dialog box problem. The toolbar on one of the Xemacs frames was about half covered by teh Framemaker window. While I was working and switching back and forth between windows, a balloon help box would appear except it had the colors and decorations of a Windows dialog. I could tell it was balloon help from the contained text. These boxes did go away as expected, but it seemed a little slower than normal. I was not able to reproduce the behavior by putting the mouse cursor over a toolbar button (?). Finally, one of these hybrid balloon help boxes ended up next to the open button. The help box seem to only have its right side. This one did not go away, and even though it had some of the buttons in the upper right cornet, they were not responsive. I tried to drag the box with the mouse and got an Xemacs crash. The lisp trace follows. There was no core file. This is Cygwin, Windows 95, no X11, b42 w/o follow on patches. Lisp trace event-window(#<motion-event 65, 2>) # bind (event) event-buffer(#motion-event 65, 2>) # bind (event) balloon-help-motion-hook(#<motion-event 65, 2>) run-hook-with-args(balloon-help-motion-hook #<motion-event 65, 2>) # bind (event) mouse-motion-hook(#<motion-event 65, 2>) # (condition-case ... , errot) # (catch top-level ...) < david

1 participants
0 comments

[Success + MULE + CDE DnD] 21.0 "Somali" XEmacs Lucid (beta42) on sparc-sun-solaris2.6 26 years, 6 months

Oliver Graf

This time with MULE. CDE DnD still works. Now we have to see if it works for everyone. Patch follows tonight. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /import/sw/epoch/lib/xemacs/api/build/xemacs-21.0-b42/Installation: > (Output from most recent run of ./configure) uname -a: SunOS benn 5.6 Generic sun4u sparc SUNW,Ultra-1 ./configure '--prefix=/import/sw/epoch/lib/xemacs/api/install' '--gung-ho' '--use-union-type' '--with-mule' XEmacs 21.0-b42 "Somali" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /import/sw/epoch/lib/xemacs/api/build/xemacs-21.0-b42 What installation prefix should install use? /import/sw/epoch/lib/xemacs/api/install What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes 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/dt/include /usr/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/X11R6/lib Runtime library search path: /usr/dt/lib:/usr/X11R6/lib:/usr/local/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for JPEG image conversion. Compiling in support for TIFF image conversion. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for LDAP (UMich libs). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif 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: --------------------------------------------------------- > /import/sw/epoch/lib/xemacs/api/build/xemacs-21.0-b42/beta.err does not exist!

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