June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Comments on 21.0 "Somali" 26 years, 5 months

Mark Borges

>> On 06 Jun 1998 00:25:37 +0200, >> Adrian Aichner(APA) wrote: APA> Try running APA> xemacs -no-init-file -no-site-file APA> which will not read the site start file nor the user init file. APA> I predict this will not put the *scratch* buffer in PenDel minor mode. It does for me. Do I win anything? ;-). Of course, it must not for you, otherwise you wouldn't have made that prediction. Any idea what else could be pulling it in then? -- -mb-

1 participants
0 comments

Re: Comments on 21.0 "Somali" 26 years, 5 months

Adrian Aichner

>>>>> "mb" == Mark Borges <mdb(a)cdc.noaa.gov> writes: mb> and if I type `xemacs -q' I'm put into a Lisp Interaction mode with mb> PenDel as a minor mode. If this PenDel minor mode is required even mb> with `-q', shouldn't it be moved to xemacs-base (or the dependence mb> removed)? -q is a synonym for just -no-init-file. Try running xemacs -no-init-file -no-site-file which will not read the site start file nor the user init file. I predict this will not put the *scratch* buffer in PenDel minor mode. Regards, Adrian mb> -- mb> -mb- -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Straße 2 Fax +49/89/41861-217 D-81673 MÜNCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Re: Comments on 21.0 "Somali" 26 years, 5 months

Mark Borges

>> On 05 Jun 1998 23:22:05 +0200, >> Adrian Aichner(APA) wrote: >>>>>> "Kevin" == Kevin Oberman <oberman(a)es.net> writes: Kevin> Is there a way of declaring the dependencies required by some package Kevin> or must it be trial and error? APA> The package interface can help you with this, although support is APA> rather low-level as of yet. APA> You may start with APA> M-x load-library RET package-get RET APA> ;;; Or evaluate the following line APA> (load-library "package-get") APA> ;;; Which package provides 'gnus? APA> (package-get-package-provider 'gnus) APA> (gnus "1.16") Thanks, that's very useful. It reminded me that awhile back I wrote, >> On 05 May 1998 17:01:27 -0600, >> Mark Borges(mb) wrote: mb> (1) trying to run `xemacs -q', XEmacs bailed out looking for mb> pending-del. I went to the packages site, mb> ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/packages/ mb> and after a few bad guesses, finally figured out it would be in mb> the pc-*pkg.tar.gz package. If this is required under `-q', mb> shouldn't it be in the base package (or is my local setup mb> somehow messed up even with `-q')? So, (package-get-package-provider 'pending-del) => (pc "1.10") and if I type `xemacs -q' I'm put into a Lisp Interaction mode with PenDel as a minor mode. If this PenDel minor mode is required even with `-q', shouldn't it be moved to xemacs-base (or the dependence removed)? -- -mb-

1 participants
0 comments

gcc 2.8.1 -O3 and -O2 fails on Solaris 26 years, 5 months

Raymond Toy

Just a quick note that gcc 2.8.1 fails to produce a working xemacs 21.0-b42 on Solaris. It gets as far as building and linking temacs, but when temacs runs, it eventually dumps core. I don't have the lisp or C traceback right now, but can easily generate one if you want it. (I went back to 2.7.2.x to build a working xemacs.) Ray

1 participants
0 comments

More balloon help wierdness in Customize buffers 26 years, 5 months

David Bush

If I go into a customize buffer I see at least two problems with balloon help. If I get balloon help for any of the buttons "Set", "Save", etc, the help ins in a windows style dialog box. Any time the balloon help comes up I also get a little Windows style dialog box with the open button from the toolbar with just a little cut off the bottom. It as a border and top bar with the standard window close "X". The close button changes visually if clicked but does nothing else. The Open button floating in the middle of the window actually causes an open dialog box to be created! This "mini-toolbar" which is floating over the text of the customize buffer stays around until I click somewhere else in the buffer. The environment is W95, Cygwin, b42. The toolbar is on the left. If I move the toolbar to the top I get slightly different behavior. The little box that first shows up is only a few pixels wide. If I click on it it expands to a toolbar with the first 3-1/4 buttons. I'll try to capture a screen image if someone will refresh my memory on how to do this unders Windows 95. david

2 participants
1 comments

Re: Info warnings 26 years, 5 months

SL Baur

Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: Hrvoje> I don't want to do either of these things. I want the warning Hrvoje> to go away. > The message is informative, the user must be notified that what he's > seeing is not what is on his dir file. I believe it should stay the > default and it is up to anyone to change that behaviour with full > knowledge of the fact. > I will let Steve arbitrate on this. Oscar, I think the changes you've made have gone a long ways to make info more useful -- I too believe dir (and localdir) files are broken by design and the ability to deal with an info directory without them is *important*. The warning by default has got to go IMO. As it is currently coded, a freshly installed XEmacs will always give a warning because the installed XEmacs info is going to appear out of date. I don't view this as an installation bug. I think Chipsy's patch "Make Info behave sensibly", is probably the way to go. It would also be useful to have a `batch-update-info-dir' function to call with `-batch' that a system administrator might use to update the system (/usr/info/dir, /usr/local/info/dir) dir files.

1 participants
0 comments

Comments on 21.0 "Somali" 26 years, 5 months

Kevin Oberman

I just managed to start 21.0 without getting any errors from my .emacs. I fully appreciate the idea of breaking out the packages from XEmacs, but there has got to be a better way of figuring out the dependencies for each package. I spent over an hour trying to get through the startup, scanning the roadmaps for the file needed and then getting the package and installing it. And I have every reason to believe that I have many more to go that won't hit me until I enter some command. Is there a way of declaring the dependencies required by some package or must it be trial and error? Some specifics: ps-print.el seems to be missing. It's not in any roadmap file. Likewise term.el seems MIA. And Gnus calls sort-subr which is not found. The jka-compr package also seems to be missing. I suspect that I'll eventually find all of them, but there needs to be a better way of helping the user through this! On the other hand, tpu-edt seems happy in 21.0 once you get all of the packages it calls. I have only a single bug to track down so far. Thanks, R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 participants
0 comments

Re: Info warnings 26 years, 5 months

Raymond Toy

siv_911254(a)debet.nhh.no (Christian Nybø) writes: > Raymond Toy <toy(a)rtp.ericsson.se> writes: > > > I will fix these once I figure out how to get the description into the > > info file. (I rarely write info files.) > > No wonder, it's the texi files you'll want to fix. Info files are > made from Texinfo (*.texi) files. Do what I mean, not what I say. :-) That's what I meant. I still have to figure out how to do in the texinfo files, which I very rarely write. Ray

1 participants
0 comments

Emacs-P4 integration p4.el 26 years, 5 months

Rajesh Vaidheeswarran

Hi GentleLispers: This is my very first attempt at submission to this group. When I sent out a mail to gnu.emacs.help and comp.emacs.xemacs asking for directions on how to submit sources to the emacs maintainers, I was told to contact RMS, and also to post in this group. And for XEmacs, I was told to mail xemacs-beta(a)xemacs.org.. So, here goes... The file p4.el is a minor mode for the P4 revision control system written by Perforce (www.perforce.com). It is not integrated into the vc.el that exists with Emacs since I didn't know if the vc library exported any hooks that I could use here. (Also, this library is my very first in elisp land). All the commands start with p4- and all the variables and constants use p4- prefix too. Please pass on your comments/suggestions/improvements to me and I'll be glad to get the feedback. Thanks rv

1 participants
0 comments

Re: Info warnings 26 years, 5 months

Christian Nybø

Raymond Toy <toy(a)rtp.ericsson.se> writes: > I will fix these once I figure out how to get the description into the > info file. (I rarely write info files.) No wonder, it's the texi files you'll want to fix. Info files are made from Texinfo (*.texi) files. -- chr

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