August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

[SITE] update deployed (was: [SITE] make over finished(?)) 24 years, 9 months

john s jacobs anderson

> Everything is basically in place; all I have to do is move the new > front page into place, and the new site will be live. I'm planning on > doing that later tonight (say, around 11 PM MDT, or 1600 UTC). I'll > post a notice on the front page and the newsgroup when it does go live. switch flipped apx. 2320 MST / 1620 UTC. newsgroup notice on the way. [ BTW: I'm up to about mid-chest level in email. Thanks for all the kind words and suggestions; I'll be getting back to everyone, but it may take some time. Don't worry, I'm not ignoring you...] john. -- ------------------------------------------------------------------------ John S Jacobs Anderson Apprentice Geek jacobs(a)azstarnet.com Journeyman Molecular Biologist <URL:http://www.treefort.org/~jacobs/> <- GeneHack:bioinfo*linux*opinion

1 participants
0 comments

Re: [SITE] make over finished(?) 24 years, 9 months

john s jacobs anderson

SL Baur <steve(a)xemacs.org> writes: > Please add ETL/Electrotechnical Laboratory (http://www.etl.go.jp/) to > the list of sponsors (after BeOpen.com) on the home page. Thanks. We > should probably also put an acknowledgement and link to the good folks > of www.tux.org for graciously hosting our main web and ftp sites. both done. > We need a link to the CVS sources at cvs.xemacs.org somewhere. I added this to the 'How to Help' (Develop/index.html) and put a note on the download page (Download/index.html) that people seeking unreleased developmental versions should go to cvs.xemacs.org. > It really looks good, John. Thank you so much for your efforts. Thanks! john. -- ------------------------------------------------------------------------ John S Jacobs Anderson Apprentice Geek jacobs(a)azstarnet.com Journeyman Molecular Biologist <URL:http://www.treefort.org/~jacobs/> <- GeneHack:bioinfo*linux*opinion

1 participants
0 comments

Re: CVS, www.xemacs.org, and not solving the problem ( was Re: Yeah! Using instructions missing from the README, xemacs installed! (was Re: How can xemacs have been made so hard to install? Do the developers have any clue it is needlessly 24 years, 9 months

Jan Vroonhof

john s jacobs anderson <jacobs(a)azstarnet.com> writes: > [ *META* could we please cc: xemacs-webmaint or webmaster(a)xemacs.org > when we start jawing about the web site? ] Consider it done! (I didn't know there was a xemacs-webmaint list). > [ META2 hey i'm the new guy blah blah blah ] Welcome. [BTW1 I like /newlook] > people who make critical decisions. That person or small group of > people is going to be the 'core' group that keeps the site going, and > CVS makes their lives *harder*. I can guess why having multiple people hack on it randomly will cause problems. But how does CVS do so? First of all CVS will make your access problem easier: You just edit the stuff locally and CVS will take care of what needs go to the site. More importantly, CVS is designed for group collaboration, that means that you can see _what_ is changed and by who. > Not to stomp on toes, or anything, but in the long run, *CONTENT* > *IS* *EASY*. And CVS only simplies content addition. Yes, but our current problem is (or better was) one of content, I can write all the READMEs , installation notes, little items telling people there is know problem with version so-and-so of the mule-base package but I have no way of getting it to the site. > as we're working!) Give us a bit of time (like a couple weeks or so) > to make some changes. > > SUMMARY MESSAGE FROM A WEB SITE VOLUNTEER: Implementing a whole bunch > of cruft (like CVS, IMHO) is only going to make the whole thing > messier in the long run. Well, I respect your opinion and I promise to leave you alone while you do your work. However when your work has stabilized I would like you to consider a solution that allows multiple people to work on the website, if need be[1]. A solution that no longer makes the maintenance[2] of the website dependent on one (or a few) persons time. For me such a solution is CVS, it isn't perfect but we already have the infra structure in place. Footnotes: [1] I am not claiming this should be the normal mode of operation. [2] Note: That is maintenance, _not_ design. I think we are disciplined enough to keep a make minor (but possibly crucial information wise) changes in accordance with your style guides if you are on that round the world trip. Jan P.S. Are you now also de facto FAQ maintainer or do we need a new volunteer for that too.

2 participants
1 comments

[SITE] update progress 24 years, 9 months

john s jacobs anderson

okay, the first pass changes to the site are about half or 2/3's done. i'm going to go collapse for a bit, then i'll hack on this some more tomorrow afternoon and early evening. ghu willing, i'll switch things over tomorrow night, about this time.[1] announcements will be made in pertinent places. if you're going to bitch about stuff, doing it now would be a Good Thing. 8^)= the new pages are all in the <URL:http://www.xemacs.org/newlook/> directory, but are symlinked into the root dir (leaving the current site intact). Basically, if you go from /newlook/index.html -> any of the new pages -> back to www.xemacs.org/index.html, you're going to be back at the old index page.[2] just don't get too lost. 8^)= *THINGS I NEED* if anyone would like to contribute some screenshots of cool looking XEmacsen, that would be nice. also, one of the things to do tomorrow is the links sections, so if you're got (X)Emacs-related content that's not on www.xemacs.org and you'd like a pointer to it, please send the URL. a short description of the content would also save me some time. finally, someone from the development group (what do you guys call yourselves in a collective sense?) should have a look at <URL:http://www.xemacs.org/newlook/Develop/index.html>. that's the 'how to help out' page. i wasn't sure how people went about joining the effort, so what's there is probably not accurate. okay, off to bed... john. Footnotes: [1] i'm in UTC-7, for those of you playing the home version. [2] yes, you're lost in a twisty little maze of web pages, all alike. -- ------------------------------------------------------------------- John S Jacobs Anderson jacobs(a)azstarnet.com http://www.treefort.org/~jacobs/ <-- GeneHack:bioinfo*linux*opinion

2 participants
1 comments

Re: kde-xemacs or gnome-xemacs? 24 years, 9 months

William M. Perry

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > William Perry <wmperry(a)aventail.com> writes: > > > I think mostly-xt would be the easiest way to get it to work under XEmacs. > > > > The real downside is using C++ :) > > And the fact that your are never going to get RMS's permissions for that > all important "as a special exception you are allowed to link with the QT > 2.00, free edition". Who cares? :) And Qt 2.x is now under the 'QPL', which is an officially 'liked' license and approved by all the open source goody-goodies. :) I think it is GPL compliant now. > Unless they changed the licence yet again, QT 2.00 is Free, but not > GPL compatible. They changed it for 2.xx - 1.xx is still under the old license. You still need to buy a windows version though. But I have several and could try to find someone to do the porting, etc. -Bill P.

4 participants
3 comments

Re: screenshot (Re: [SITE] update progress) 24 years, 9 months

john s jacobs anderson

Stephen Tse <stephent(a)sfu.ca> writes: > http://www.sfu.ca/~stephent/eicq/eicq.gif > > This is my desktop screenshot containing only two frames of xemacs. > But it is mule'd and running my eicq; I am not sure that's what you > want. > > I appreciate you put some caption for it. This is exactly what I was looking for. Link added to <URL:http://www.xemacs.org/About/Screenshots/> I also added the eicq site to <URL:http://www.xemacs.org/Links/customization.html> Thanks, john. -- ------------------------------------------------------------------------ John S Jacobs Anderson Apprentice Geek jacobs(a)azstarnet.com Journeyman Molecular Biologist <URL:http://www.treefort.org/~jacobs/> <- GeneHack:bioinfo*linux*opinion

1 participants
0 comments

Re: [Fwd: Xemacs 21.1.6 minor build problem.] 24 years, 9 months

Jan Vroonhof

Jason Kim <jason(a)meta4.net> writes: > What I did was: > > ./configure --prefix=/apps/pkgs/xemacs-21.1.6 > make > make install Can you run "in place"? i.e. by starting "src/xemacs" where you compiled XEmacs? Jan

1 participants
0 comments

XEmacs-Patches list problems 24 years, 9 months

XEmacs Team

To all people who have send patches to the XEmacs Patches list and have not had feedback. The XEmacs-patches(a)xemacs.org list is the entry point for all contributions to the XEmacs source and/or packages. It is "moderated" by a bot that checks whether the messages actually contains a patch. The normal procedure after send a patch to this address is as follows: 1. Immediately you will get a message from the bot confirming the receipt of the patch. 2. The patch is archived at www.xemacs.org. 3. Either 3.a.1 You will receive a message that your patch has been Checked & Approved for inclusion, followed by 3.a.2 A message confirming the patch has been applied to the CVS. or 3.b. A message telling you the patch has been rejected and why (normally with suggestions for improvement). However, it has been discovered that the bot had a configuration error that dropped some patches on the floor after sending out the automated confirmation messages. This problem as how been rectified. If you have send a patch to XEmacs-patches(a)xemacs.org and hear nothing except for the automated replay then please do so again. We apologize for the inconvenience. Please be advised, however, that we are not able to give refunds. P.S. Now what I have your attention, let me point out that the ideal patch contains - A short description of the problem solved. - A ChangeLog entry (c.f M-x add-change-log-entry) included literally (not as a diff). - A unified diff (diff -u) of the changed file, made from the toplevel XEmacs directory. This greatly simplifies the jobs of the patch reviewers and appliers.

1 participants
0 comments

Re: [SITE] update progress 24 years, 9 months

Jan Vroonhof

john s jacobs anderson <jacobs(a)azstarnet.com> writes: > also, one of the things to do tomorrow is the links sections, > so if you're got (X)Emacs-related content that's not on www.xemacs.org > and you'd like a pointer to it, please send the URL. a short > description of the content would also save me some time. None of this my own === XEmacs lisp software not currently bundled with XEmacs/available as official packages <a href="http://www.fmi.uni-passau.de/~wedler/x-symbol/"> X-Symbol </a> is a package by Christoph Wedler> The main purpose of package x-symbol is to provide some WYSIWYGness in an area where it greatly enhance the readability of your LaTeX or HTML source: using "real" characters for "tokens" like \oplus or ™. It also provides input methods for these characters, both for the beginner and the expert (some users regard this as the main reason to use package x-symbol). WYSIWYG super- and subscripts and images/figures are also supported. There is an XEmacs 21 installable lisp package available from his site. <a href="http://members.tripod.com/gchen2/xemacs/">Gongquan Chen</a> has a few nifty enhancements on his site. Including a hack that allows you to use <em>multiple major modes</em> in one buffer, f.i. to edit CSS inside an HTML file. > finally, someone from the development group (what do you guys call > yourselves in a collective sense?) I don't know. I think a few people (including me, Didier, Vinnie, ...) need to be added to http://www.xemacs.org/Develop/devTeam.html anyway. May be I should also submit something for the about XEmacs buffer. Jan P.S. You can borrow a screen shot of Gnus from http://socha.net/Gnus/screenshots/mime.html (doesn't hurt to have a nice Girl on the site anyway)

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 24 years, 9 months

Jan Vroonhof

Glynn Clements <glynn(a)sensei.co.uk> writes: > Looking at XtWindowToWidget (in xc/lib/Xt/Event.c) indicates that Xt > keeps a per-display hashtable of Widget/Window pairs, with the Window > as the key. So, it's not having to do anything as expensive as > scanning the Widget tree. And thus cheaper than the window structure walk we do now to find the scrollbars. It seems like using XtWindowToWidget and also looking for parents is the way too go. Jan

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