January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

syntax highlighting breakage 25 years, 3 months

Neal D. Becker

i686-pc-linux-gnu Latest packages. After some period of usage, syntax highlighting broke. I'm typing in a new C++ header file. After class xxx {, I type public: It indents public and makes it green. The only way to regain sanity is to kill emacs and restart. Then it's fine. No clue what caused it.

1 participants
0 comments

Re: Feedback on pui-list-packages 25 years, 3 months

William M. Perry

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Andy Piper <andyp(a)parallax.co.uk> writes: > > > At 11:31 06/01/99 +0100, Jan Vroonhof wrote: > > >> get downloaded. > > >> - It would be good to have a progressive indicator as things are > > >> getting installed. I thought for example xemacs-base had just hung, > > >> but (I think) it was just taking a long time. > > > > > >This would indeed be nice. > > > > You could use the progress gauge glyph support that's in 21.2 now - > > but it only works under mswindows untill someone tries to add the X > > support. > > And it won't work on TTY's. No reason it couldn't. Would just have to implement them ourselves, like any other `widgets' on a TTY. widget.el should provide the abstraction we need on whether to use 'native' widgets (when in X or Windows or whatever), and a text-only representation (like it uses now) on a TTY. A gauge could easily be mocked up on a tty... we already have the slider stuff, someone could adapt that pretty easily I think. -Bill P.

1 participants
0 comments

Re: patch to tunnel CVS connections through firewalls. 25 years, 3 months

William M. Perry

Martin Buchholz <martin(a)xemacs.org> writes: > >>>>> "Bill" == William M Perry <wmperry(a)aventail.com> writes: > > Bill> ObXEmacs: Is XEmacs Y2K compliant? :) > > http://www.xemacs.org/year2000.html I was being sarcastic, just for the record. :) You might want to add something to that page that while XEmacs may be y2k safe, _packages_ that run in it are a totally separate ball of sticky wax. -Bill P.

1 participants
0 comments

Re: patch to tunnel CVS connections through firewalls. 25 years, 3 months

William M. Perry

Andy Piper <andyp(a)parallax.co.uk> writes: > At 01:04 05/01/99 -0800, Kyle Jones wrote: > >I have to wonder, living behind a corporate firewall myself at > >my day-job, how the person in charge of security would feel > >about this clever tunneling. Why is asking the company security > >guru to allow outbound connections to TCP port 443 not the right > >solution to this problem? Wriggling under the firewall might > >buy you some short term gain--- but it might also get you fired. They'll probably not be very happy when I make our socks server able to listen on mulitiple ports and we document how to make it run on port 443 to achieve specifically the generic tunelling that andy is talking about. :) > Well there are two answers to this: > > 1. They can't fire me becuse I have already resigned :) Where are you heading? > 2. It seems many sysadmins are unhappy to do this. I don't know why this > is but I know that setting up another proxy on our firewall is a pain > because it has to be a specific port for a specific location (so you need > a plug gateway for each cvs server you want to connect to). Allowing > access via the web-proxy is much easier to administer, but I couldn't > comment on the security implications. My sysadmin was happy to allow 2401 > on the web proxy - but then he was also happy to add a plug-gateway for > cvs.xemacs.org. YMMV. Sounds like you've got a pretty decent admin... consider yourself lucky (for as long as you've got left there). > BillP might know more. The quality of system administrators seems to have gone down drastically (or the # of admins has gone drastically up, therefore dragging the average _WAY_ down). This tends to lead to draconian `security' policies, as well taking the easy way out and denying _all_ services and requiring a `business case' to open up any service. I weep for the future. I had to present such a case to allow _inbound_ telnet access from terminal servers that WE OWNED AND CONTROLLED for all the unix people at SPRY after compusuck bought us. The mind spins until it gets dizzy and pukes up a mission statement I guess. A little birdie once told me that an idiot MIS person put _BETA_ software into production, bitched when something minor broke, and then could not do the simplest things to help diagnose the problem (like change the logging level) without getting written authorization from someone 3 rungs higher on the MIS ladder, who happened to be on vacation. Not that we'd sell software to someone that stupid. Never. In fact, that was fictional! I swear. ObXEmacs: Is XEmacs Y2K compliant? :) -Bill "Stream of Consiusness Today" Perry

2 participants
1 comments

Re: Feedback on pui-list-packages 25 years, 3 months

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > At 11:31 06/01/99 +0100, Jan Vroonhof wrote: > >> get downloaded. > >> - It would be good to have a progressive indicator as things are > >> getting installed. I thought for example xemacs-base had just hung, > >> but (I think) it was just taking a long time. > > > >This would indeed be nice. > > You could use the progress gauge glyph support that's in 21.2 now - > but it only works under mswindows untill someone tries to add the X > support. And it won't work on TTY's.

1 participants
0 comments

Is there no more need of our xemacs-beta mirror? 25 years, 3 months

M. Schmidt

Hi, I'm mirroring several other stuff/sites at our FTP server. But since a very long time I see that there is almost no traffic regarding the xemacs-beta part of our FTP mirror. What I would like to know is: If there is no more need of it or almost none then feel free to send me any message whether I may kick off our xemacs-beta mirror. I would like to get your responses to this. Have a nice day Michael -- Michael Schmidt mschmidt(a)fh-koblenz.de Mirror of: SAMBA: IPFilter, Ghostscript Server for Win95, Linux-HOWTO, XEmacs-beta WinNT, LANManager

2 participants
1 comments

Re: Feedback on pui-list-packages 25 years, 3 months

Jan Vroonhof

"Barry A. Warsaw" <bwarsaw(a)cnri.reston.va.us> writes: > - It would be nice if package-get-remote were set to point to > ftp.xemacs.org by default. I had to set this before I could get > anything working. No, this is intentional. The package-get-remote is empty for 2 reasons 1. To make sure XEmacs does not go remote unintentionally. There however is now also some logic to try to only go remote if that would be 'logical' to users. This is not likely to be 100% correct. 2. To force people to make a conscious decision about choosing the site/mirror. Just defaulting to a site killed ftp.us.debian.org when the new experimental package fetcher for debian did that. > - It seems that any error in unpacking a package stops the whole > process. It would be better if the other packages could be > installed and some indicator in the *Packages* buffer could be > used [..] > - It would be useful to include package sizes to know how much has to > get downloaded. > - It would be good to have a progressive indicator as things are > getting installed. I thought for example xemacs-base had just hung, > but (I think) it was just taking a long time. This would indeed be nice. > - I've had some problems installing a package which I had done some > edits in, creating an RCS subdirectory. XEmacs complained that it > couldn't find .../package/RCS and the install process just hung. Strange... Jan

3 participants
2 comments

patch to tunnel CVS connections through firewalls. 25 years, 3 months

Andy Piper

Hi there, Many open source projects provide access to their source code via remote cvs (usually pserver). Unfortunately, many people are prevented from using these facilities because they are behind firewalls which prevent uncontrolled tcp access outside of their LAN. However, this is also often the case for things like HTTPS and so Netscape have defined a way of circumventing these restrictions by tunnelling connections through HTTP. See http://home.netscape.com/newsref/std/tunneling_ssl.html. This facility can easily be added to cvs and the attached patch achieves this. To use the proxy www on port 8080 to connect to the external machine there.somedomain use: cvs -d :pserver;proxy=www;proxyport=8080:me＠there.somedomain:/somerepository The patch includes Jim Kingdon's port patch as many web servers restrict the use of CONNECT to well known ports. A way of circumventing this is to make a cvs server listen on one of these ports - for instance 443 the HTTPS port. To access a server set up in this way do: cvs -d :pserver;proxy=www;proxyport=8080;port=443:me＠there.somedomain:/somerepository The patch was inspired by ssh-tunnel.pl written by Urban Kaveus <urban(a)statt.ericsson.se>. It adheres to HACKING so I hope it can be incorporated in the main development tree. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

4 participants
5 comments

rot13 in 21.0 packages 25 years, 3 months

Brent B. Powers

rot13.el is included in misc-games in 21.0. Unfortunately, it doesn't work, as it relies on something called window-display-table

1 participants
0 comments

Re: Source Comment Formatting 25 years, 3 months

Remek Trzaska

>On Jan 6, 11:34, Remek Trzaska wrote: >> Subject: Re: Source Comment Formatting >> Have you tried to press M-q in one of long commented lines? Works great for >> me. > > >That is EXACTLY what I was looking for! You've saved me a lot of time. What >do I owe you? 364 days of testing XEmacs betas. Weekly progress reports :-) Remek

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