March 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Jan Vroonhof

Ben Wing <ben(a)666.com> writes: > Jan, prior to the introduction of packages, there was no need to `make > install' to get things to work. I want it to be possible to download a > single tarball and simply do "configure; make" and have things work when you > run the executable. I must be misunderstanding you, because that already works for me! I run XEmacs in-place like this all the time. (The only problem is with $topdir != $srcdir, but that just means configure should be tweaked to create links for ../xemacs-packages and ../site-packages, just like it does for ../lisp. I create them by hand ATM) i.e. tar xzf xemacs-<version>.tar.gz | cd xemacs-<version> | tar xzf xemacs-sumo-<date>.tar.gz | This can be made into one big | tarball. ./configure make ./src/xemacs works (at least on Unix, maybe it is different under windows) What remains to be done (AFAICS) is: - Make $srcdir != $topdir work - Copy the contents of the package trees over at "make install" time. - make the actuall xemacs-<version>-all.tar.gz tarball and release the core as xemacs-<version>-core.tar.gz in the future. - Update docs Jan

1 participants
0 comments

Re: I don't wont the f* underlinings in the menubar (aka accelerators) 25 years

Hrvoje Niksic

Giacomo Boffi <giacomo.boffi(a)polimi.it> writes: > Hrvoje Niksic writes: > > Robert Pluim <rpluim(a)bigfoot.com> writes: > > > > > True. But I for one don't use them > > > > So if you don't use them, how come they bother you so much? I > > don't see how this one piece of decoration can possibly be so > > unacceptable. > > ============== > SHEER UGLINESS > ============== Well, I think they're real purdy. :-)

6 participants
9 comments

Re: I don't wont the f* underlinings in the menubar (aka accelerators) 25 years

Hrvoje Niksic

Robert Pluim <rpluim(a)bigfoot.com> writes: > True. But I for one don't use them So if you don't use them, how come they bother you so much? I don't see how this one piece of decoration can possibly be so unacceptable.

3 participants
2 comments

Re: I don't wont the f* underlinings in the menubar (aka accelerators) 25 years

Hrvoje Niksic

Giacomo Boffi <giacomo.boffi(a)polimi.it> writes: > =============================================================== > I DON'T LIKE THE UNDERLININGS IN THE MENUBAR (AKA ACCELERATORS) > =============================================================== Oh come on. How do you use other window-system applications? Most of them have them.

3 participants
2 comments

Re: Package hierarchy location [was: Re:] 25 years

Michael Sperber

>>>>> "Ben" == Ben Wing <ben(a)666.com> writes: Ben> Jan, prior to the introduction of packages, there was no need to `make Ben> install' to get things to work. I want it to be possible to download a Ben> single tarball and simply do "configure; make" and have things work when you Ben> run the executable. This has nothing to do with separate packages for Ben> separate versions, and everything to do with "it should just work". Maybe I'm beginning to see what you're suggesting here: You want a package tree alongside the *source tree* for an *in-place* XEmacs. Right? I have no objection to that, as long as we don't use this setup for the installed XEmacs. I'll even implement this. And please, guys, once again, I'M BEGGING YOU ... SUBJECT HEADERS? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

Re: 25 years

Jan Vroonhof

Ben Wing <ben(a)666.com> writes: > Oh yeah, another thing waiting to be completed: I put in a change to > package loading so it will find the packages in a structure like this: > > .../xemacs-packages/ > .../xemacs-21.2.30/ > > which is exactly what's needed for a truly unified tarball. Why? I though it would be sufficient to have the Make file create a ${prefix}/lib/xemacs/site-packages ${prefix}/lib/xemacs/xemacs-packages and copy ${srcdir}/xemacs-package to it if it exists? I can see that maybe you would want have separate packages for separate versions, but I would rather see a solution on the lines you give in your other message for that? Jan

2 participants
1 comments

'kill-region' replaces primary selection? 25 years

Daniel Pittman

I believe this is a fairly recent change in XEmacs behavior. 'kill-word' currently replaces the primary selection with the killed word, where previously (circa b29, I think) the primary selection was left alone. Is this an intentional change in behavior and, if so, how might I go about reverting to the old way? It used to be really easy to do a semi-automatic query-replace with the old bindings and I miss it. :) Thanks, Daniel -- A tranquil city of good laws, fine architecture, and clean streets is like a classroom of obedient dullards, or a field of gelded bulls -- whereas a city of anarchy is a city of promise. -- Mark Helprin

1 participants
0 comments

Re: 25 years

Vin Shelton

And please submit the patches separately in small batches to make for easier review and application. I still haven't had the time to tease out the GC patches from your last monster submission. Thanks, Ben. - vin >>>>> On 19 Mar 2000 17:32:39 +0100, Hrvoje Niksic <hniksic(a)iskon.hr> said: Hrvoje> Ben Wing <ben(a)666.com> writes: >> Currently I'm working on some process stuff (implementing >> `call-process' in Lisp, so it works under MSWin). If I ever get >> that finished, I'm also almost finished with some code to implement >> hyperlinks in the Help buffer and provide a general means of >> "activation" (what happens when you press button2 in a completion >> buffer, e.g.; but I want to make it so you can use >> button1-double-click as well, and use button2drag separately, >> i.e. activation will happen on button2 click instead of button2 >> down). I'm basically done with these, but got started this other >> project that's become a monster, and haven't had a chance to merge >> in anything in that other workspace in awhile. Hrvoje> This sounds like a bunch of projects. It would be nice if you could Hrvoje> specify which ones you plan to finish by 21.2 release. We'll have to Hrvoje> introduce a feature freeze sooner or later, and it's been a long time Hrvoje> since the last release. Hrvoje> Note that feature freeze does not mean that your work stops; soon Hrvoje> after the freeze, a new development branch is opened.

1 participants
0 comments

Re: I don't wont the f* underlinings in the menubar (aka accelerators) 25 years

Jan Vroonhof

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > So if you don't use them, how come they bother you so much? I don't > see how this one piece of decoration can possibly be so unacceptable. This isn't directly related to the underlining, but frankly, some of auto generated accelerators are awful. Try Options->Size. Jan P.S. It took me quite some time to get used to the underlining.

1 participants
0 comments

Re: I don't wont the f* underlinings in the menubar (aka accelerators) 25 years

William M. Perry

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > Robert Pluim <rpluim(a)bigfoot.com> writes: > > > True. But I for one don't use them > > So if you don't use them, how come they bother you so much? I don't > see how this one piece of decoration can possibly be so unacceptable. They are a bit more obtrusive than accelerator indications used in gtk/gnome applications. They seem to use the bevel color instead of the text color. Not sure which is better though. -Bill P.

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