December 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Modules (was: Re: How about a feature freeze) 25 years

William M. Perry

Colin Rafferty <colin.rafferty(a)msdw.com> writes: > Jan Vroonhof writes: > > > I haven't seen an mp3 decode in elisp yet. > > And I don't think that you will. Is that a challenge? :) -Bill P.

2 participants
1 comments

Re: Modules (was: Re: How about a feature freeze) 25 years

William M. Perry

Olivier Galibert <galibert(a)pobox.com> writes: > On Tue, Dec 21, 1999 at 06:55:39AM -0700, john s jacobs anderson wrote: > > In order to really be attractive, I think Jan's suggestion would need > > to be accompanied by a mp3 player mode, and the inclusion of one or > > more of the IM/chat modes in the standard tarball. > > I almost exploded laughing reading that... but the worst thing is, I > think you're absolutely right... > > OG. > > PS: M-x playlist-mode anybody ? ;-) Actually, thingsl ike a decent MP3 interface and IRC are exactly what the users of emacspeak need. Since you never have to leave Emacs for even the most complex thing, a lot of emacspeak users use it as their ONLY interface to their computer. They don't care that it is emacs underneath, or linux underneath that, they just know they can use their computer and have everything speech enabled magically. :) This is one of the reasons I'm trying to get the XMMS guys to decouple the UI from their core playing engine, so that a decent Emacs interface could be written to it, and combine that with my plans for a realaudio plugin for XMMS, and they can have a TTY-only, completely speech-enabled funhouse. :) -Bill P.

1 participants
0 comments

patch needed for latest 21.2 CVS 25 years

Damon Lipparelli

I had to apply the following patch to get things compiling under X11R5. Does this make sense? -lipp <<patch1.txt>>

1 participants
0 comments

Merging customize support 25 years

Per Abrahamsen

I'm looking into porting the theme support from XEmacs into Emacs. However, looking at the 21.0 source there are also some features that could be ported the other way, like: Doc improvements. Using customize to set local variables New keyword :set-after (explicit dependencies between options) new font attributes Some of the later could perhaps be emulated with wmperry's font.el package (same way the current font attributes are handled). If I start working on these, will someone look at it?

1 participants
0 comments

Re: Modules (was: Re: How about a feature freeze) 25 years

John S. J. Anderson

>>>>> "Ben" == Ben Wing <ben(a)666.com> writes: Ben> Jan Vroonhof wrote: >> <fatalist> If the purpose is to attract more users, high priority >> should given to implement transpart background support Ben> explain? s/transpart/transparent/, I think. The current 'cool Linux GUI setup' du jour requires (a) some kind of instant messaging client (AIM, ICQ, or IRC for the old school), (b) an mp3 player and (c) xterms with 'transparent' backgrounds -- an effect that is achieved by using a graphics lib to do a screen grab of the area the term is covering, and then using that grab for the background. Wow, that's confusing. Just have a look at <URL:http://genehack.org/Images/eyeCandy.jpg>. You can currently get most of the desired effect by running -nw in such a term, I believe. In order to really be attractive, I think Jan's suggestion would need to be accompanied by a mp3 player mode, and the inclusion of one or more of the IM/chat modes in the standard tarball. john. -- ------------------------------------------------------------------------ John S Jacobs Anderson \ <URL:http://www.xemacs.org> You'll have to pry my Emacs from my cold \ jacobs(a)xemacs.org dead oversized control-pressing left pinky finger. -- Randal L. Schwartz

2 participants
1 comments

Re: Modules (was: Re: How about a feature freeze) 25 years

Colin Rafferty

Jan Vroonhof writes: > I haven't seen an mp3 decode in elisp yet. And I don't think that you will. -- Colin

1 participants
0 comments

bad vm interaction with multiple frames/gnuclient 25 years

Cotton Seed

Start up xemacs. M-x gnuserv-start. M-x vm. inbox and inbox Summary buffers are now displayed. gnuclient -nw. C-x b *scratch* RET. M-x vm. Only "N messages, M new, ..." is displayed in the minibuffer of the gnuclient frame, the vm buffers do not become visible. If there are no vm buffers displayed on the initial frame, then things work properly in the tty frame. - Cotton

2 participants
1 comments

widget patches & friends. 25 years

Andy Piper

This clears the backlog in my local environment: - FIxes tab font change problems under X - Fixes widget copying problems - Syncs with the latest Tabs version - Starts on layouts. andy 1999-12-21 Andy Piper <andy(a)xemacs.org> * redisplay.c (redisplay_frame): check for faces changed when reseting subwindow caches. * glyphs.h (struct ii_keyword_entry): add copy_p. (struct image_instantiator_methods): add query_geometry_method and layout_children_method. (IIFORMAT_VALID_GENERIC_KEYWORD): new macro to take into account copying characteristics of keywords. (IIFORMAT_VALID_NONCOPY_KEYWORD): new macro for defining keywords whose arguments should not be copied by the specifier code. (image_instance_geometry): new enum for layouts. (struct Lisp_Image_Instance): re-jig for layouts and update macros. * glyphs.c (string_instantiate): rename variables. (image_instantiate): add strings to those widgets that are instantiated per-window. (image_copy_vector_instantiator): new function for copying glyph specifier instantiators. (image_copy_instantiator): ditto. * glyphs-x.c (x_update_subwindow): use new face update functions. (update_widget_face): update to use new lwlib arg functions. (update_tab_widget_face): new function for updating tab control label faces. (x_widget_instantiate): use new face update functions and new lwlib arg functions. (x_tab_control_instantiate): ditto. (x_tab_control_set_property): ditto. * glyphs-widget.c (VALID_GUI_KEYWORDS): use NONCOPY keyword for callbacks and other things that could recurse. (VALID_GUI_KEYWORDS): * event-msw.c: fix cpp stuff for cygwin < b20. * config.h.in: move uid_t and friends to before the s&m files so that they can be used there. * Makefile.in.in (debug-temacs): new target that adds emacs environment before invoking gdb. * lwlib.h (_widget_args): new structure for holding widget args. It is reference counted so that we don't have to copy Xt args. (_widget_value): remove widget args. Add reference to widget_args. * lwlib.c (free_widget_value_contents): free widget args using free_widget_value_args. * lwlib-Xaw.c (xaw_update_one_widget): use new arg packet. (xaw_update_one_widget): use XtIsSubclass for determining labels. * lwlib.c (lw_add_value_args_to_args): modify to use our reference counted arg packet. (lw_add_widget_value_arg): new function. Add an arg to the arg packet. (free_widget_value_args): new function. Remove a reference counted arg packet. (lw_copy_widget_value_args): new function. Copy reference counted arg packet. (merge_widget_value_args): new function. Do a merge of widget args. (merge_widget_value): use it. (copy_widget_value_tree): copy widget args using reference counting, since we can't easily copy the args we have been given. * specifier.h (struct specifier_methods): add copy_instantiator_method. * specifier.c (build_up_processed_list): use copy_instantiator_method if defined. 1999-12-08 Andy Piper <andy(a)xemacs.org> * xlwtabs.c: sync with Tabs 2.1. * xlwtabP.h: ditto. 1999-11-25 Andy Piper <andy(a)xemacs.org> * cus-edit.el (custom-buffer-create-buttons): Use native widgets for buttons. -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

update packages screws gdb-mode 25 years

Neal D. Becker

After updating packages I'm not enjoying gdb. This is; "21.1 (patch 8) \"Bryce Canyon\" XEmacs Lucid" i686-pc-linux-gnu gdb-4.18 (RH6.1) For example: Starting program: /home/nbecker/TES/Test14 Breakpoint 1, main (argc=1, argv ---Type <return> to continue, or q <return> to quit---quit Instead of talking to gdb for me, it's acting as if I'm using raw gdb with just a terminal interface. It didn't display the source (at least, not at this point in the interaction), but it's asking me to hit return or quit. Is M-x gdb hosed, or do I need to set some variables to get reasonable behaviour?

1 participants
0 comments

Re: minibuf.texi question 25 years

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > > I think it is a very weird feature for a first time user, > > > however it also very practical, and it doesn't get in the > > > way. Now that we start passing in the default value anyway for > > > the history stuff, it seems to be "cheap" to implement. > > > > Do you think the two features could coexist? I don't see the point of > > our DEFAULT parameter if FSF-style DEFAULT is one M-n away. > > Our style default parameter is about putting the default answer in > the history when you just hit RET. That is totally independent of > the cursor-down feature. Indeed, it is. Okay, I withdraw the above sentence ("I don't see the point..."). But I maintain that the fact that the features are named the same and similar in nature is bound to create confusion among the (Lisp) users. Consider: if we are adding the DEFAULT argument to read-string, read-command, and read-variable, which one do we add? Obviously, we're adding our "returned-value-if-you-just-press-RET" version of the DEFAULT argument. Don't you think that this creates a dangerously silent and subtle incompatibility with FSF? Code that says (read-string "prompt: " nil nil "default") will do one thing in FSF, and something else in XEmacs. All subtly and silently. > Otherwise you would have to say "To get your prompt in the history > type M-n before RET". IMHO that requires too much foresight on the > part of the user. I agree.

1 participants
0 comments

2025

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 December 1999