May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Can XEmacs NT display on a remote X? 26 years, 6 months

Raymond Toy

Andy Piper <andyp(a)parallax.co.uk> writes: > > You need X11R6.3/bin in your path so that it can find the dll's > Thanks for you help. It's now happily running update-elc now. > >I guess I should join xemacs-nt and take up this discussion there > >where it would be more appropriate. > > Yes. > Just joined. Ray

1 participants
0 comments

Re: Success (was: [failure] 21.0 "Russian White-pre7" XEmacs Lucid (beta39) on cygwin32) 26 years, 6 months

Adrian Aichner

>>>>> "RT" == Remek Trzaska <remek(a)npac.syr.edu> writes: >>>>> "Andy" == Andy Piper <andyp(a)parallax.co.uk> writes: Andy> You evidently don't have the hacked msg select(). I would be Andy> interested to know if you can make this work. Try putting Andy> #include <winsock.h> Andy> at the top of the file. >>> >>> Hmmmm... No good, I would say. The result attached in *compressed* >>> format. Andy> Hmm, cygwin docs say that winsock.h can't be used with select. Andy> Hmm, try Andy> typedef unsigned int SOCKET; Andy> instead. RT> Andy, I simply love you!!! No more substitutes such as ntemacs!!! RT> XEmacs rulez!!! RT> XEmacs-nt guys, you are great--thank you. Plain cygwin32, plain RT> (well, almost) cvs checkout, no additional libraries, and I finally RT> have XEmacs on M$. RT> Current problem: making efs work. Which ftp.exe do you use? When I RT> try to open any remote location, I just get a black window with a RT> `ftp' caption, and nothing ever happens there. You could get the ftp.exe advertised in: http://www.cs.washington.edu/homes/voelker/ntemacs.html#ange-ftp That's what I did for NTEmacs under Windows NT. You won't need to perform any of the ange-ftp fixes but they might get you on the right track what else you may need to check to get EFS working. I suspect it's only the stupid ftp program delivered with NT which causes the problem. Good Luck, Adrian RT> Remek -- 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: [failure] 21.0 "Russian White-pre7" XEmacs Lucid (beta39) on cygwin32 26 years, 6 months

Remek Trzaska

>>>>> "Andy" == Andy Piper <andyp(a)parallax.co.uk> writes: Andy> You evidently don't have the hacked msg select(). I would be Andy> interested to know if you can make this work. Try putting Andy> #include <winsock.h> Andy> at the top of the file. Hmmmm... No good, I would say. The result attached in *compressed* format. Remek

2 participants
2 comments

Re: Can XEmacs NT display on a remote X? 26 years, 6 months

Raymond Toy

Andy Piper <andyp(a)parallax.co.uk> writes: > >Can anyone point me to a binary distribution of X for NT? Or do I > >have to build it myself? > > www.parallax.co.uk/~andyp Thanks for the pointer. Got it, untarred it, reconfig'd xemacs to use X11, and built it. However, when running temacs with update-elc, I get the message The dynamic link library libICE.dll could not be found in the specified path.... I guess I should join xemacs-nt and take up this discussion there where it would be more appropriate. Ray

2 participants
1 comments

Re: proposal for new configure flag 26 years, 6 months

SL Baur

Jeff Miller <jmiller(a)smart.net> writes: > I'm suggesting a "--bare-bones" style option to turn off as much as > possible for those that want a lean & mean xemacs. What flags do you have in mind so far? I need the following: ./configure --with-x11=no --error-checking=none --debug=no \ --extra-verbose=no --with-shlib=no --with-database=no \ --with-sound=none --with-gpm=no > I've already got a bit of something worked up, but of course, it currently > is really one suited to my Linux box. It probably wouldn't configure > correctly for the MS port, for example. > What do others think? Is it worthwhile? There always seem to be chatter > on the xemacs list about wanting a smaller xemacs. > I currently get an xemacs that is ~2.75M in size. That's about what I see. > If there is interest, I can post what I have to xemacs-patches..... I've worked it out on my own, so I definitely have interest in it.

2 participants
1 comments

Re: Startup speed: Still too many stats? 26 years, 6 months

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Now that we are closed to code freeze, I've looked at the startup Hrvoje> speed again, and here is what I got: Hrvoje> $ truss -t stat -o out xemacs -q -nw -f kill-emacs Hrvoje> I tried this with XEmacs 20.3 (the default configuration), and with my Hrvoje> 21.0 installation containing a moderate number of packages (probably Hrvoje> less than there were in 20.3). Hrvoje> Basically, 20.3 performs 96 stats, while 21.0 performs 651 Hrvoje> stats. On the technical side, could you try again with `packages-hierarchy-depth' (in packages.el) changed to 0? Hrvoje> The ones in 21.0 are mostly spent to stat the `.el' and `.elc' Hrvoje> files. Michael, what was your opinion about the optimization Hrvoje> we discussed, which would forbid directories ending with `.el' Hrvoje> or `.elc'? I think it would be worth implementing it, Hrvoje> especially for non-Unix systems, where a stat is extremely Hrvoje> costly. Well, the stat count is one thing. The really important factors though are timings and the subjective startup time. While people complained before I limited recursion depth, nobody has complained since. I'm not sure you're complaining here. Are you? I really would like to keep the complexity of the code down as far as possible to keep it as maintainable as possible. I'm totally not averse to implementing optimization hacks once there's solid proof they're necessary. On another note, is a full stat really necessary on NT to compute file-directory-p? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Startup speed: Still too many stats? 26 years, 6 months

SL Baur

Olivier Galibert <galibert(a)pobox.com> writes: > As of today, except for the info issues, there have only been a > deafening silence. You are welcome to try it that way manually and report the results. I don't think the current distribution format should change. I have promised to support installation merging all lisp .elc files into one directory, that will be complete before 21.0 goes out.

2 participants
1 comments

Re: Startup speed: Still too many stats? 26 years, 6 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Michael, what was your opinion about the optimization we discussed, > which would forbid directories ending with `.el' or `.elc'? I think > it would be worth implementing it, especially for non-Unix systems, > where a stat is extremely costly. I thought this was taken care of by limiting the recursion depth? Jan

1 participants
0 comments

Startup speed: Still too many stats? 26 years, 6 months

Hrvoje Niksic

Now that we are closed to code freeze, I've looked at the startup speed again, and here is what I got: $ truss -t stat -o out xemacs -q -nw -f kill-emacs I tried this with XEmacs 20.3 (the default configuration), and with my 21.0 installation containing a moderate number of packages (probably less than there were in 20.3). Basically, 20.3 performs 96 stats, while 21.0 performs 651 stats. The ones in 21.0 are mostly spent to stat the `.el' and `.elc' files. Michael, what was your opinion about the optimization we discussed, which would forbid directories ending with `.el' or `.elc'? I think it would be worth implementing it, especially for non-Unix systems, where a stat is extremely costly. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Idle RAM is the Devil's playground.

2 participants
1 comments

Re: [PATCH] Changes to man/xemacs-faq.texi 26 years, 6 months

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > Hacking off RMS gains us nothing, if we can be sensitive to him > without compromising XEmacs goals then I think we should do that. I > suspect that the vast majority of users who read the faq will just > think we are being anal and /or not care. The users will be confused if Emacs is once used as a generic term, and the other time to mean `FSF Emacs'. So let's please stick to `Emacs' as generic. As the rationale in NEWS explains: N.B. The term "GNU Emacs" refers to any release of Emacs Version 19 from the Free Software Foundation's GNU Project. (We do not say just "Emacs" as Richard M. Stallman ["RMS"] prefers, because it is clearly a more generic term.) The term "XEmacs" refers to this program or to its predecessors "Era" and "Lucid Emacs". The predecessor of all these program is called "Emacs 18". When no particular version is implied, "Emacs" will be used. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Listen, kid, we're all in it together!" -- Harry Tuttle in _Brazil_

2 participants
1 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 May 1998