February 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Anybody using vc-cc.el with success in Windows NT native build? 25 years, 1 month

Adrian Aichner

If so, please let me know. cleartool gets started for me, but fails to "cooperate". XEmacs hangs, displaying: waiting for cleartool to start... Luckily this is C-g-able. I have this in my site-start.el: (require 'vc-hooks) which worked fine with package vc and pcl-cvs, using CVS. Now I uninstalled vc and installed vc-cc because I seem to remember the two are incompatible. Anything else I could try? Env. vars? Switches? Thanks in advance, Adrian

1 participants
0 comments

Proposed (subsidiary-coding-system) change 25 years, 1 month

Kirill 'Big K' Katsnelson

Currently, (subsidiary-coding-system) returns its parameter if it has not an autodetect property: (subsidiary-coding-system (find-coding-system 'undecided) 'crlf) =>> #<coding_system undecided-dos> (subsidiary-coding-system (find-coding-system 'undecided-unix) 'crlf) =>> #<coding_system undecided-unix> I might be missing something obvious, but I cannot easily deduce a coding system different from a given one only by eol-type. I think either this function should be changed so that it finds a coding system even when given a no-autodecect coding system or, if this change is going to break anything, a new function must be introduced which does what I want. Again if only I am not missing "the right" way of doing this. Big K

2 participants
1 comments

Gutter tabs background 25 years, 1 month

Fred

Is there a resouce that can be set to force the color of the gutter tabs to match the color of the menubar and toolbar? -- Fred Hart (cfhart(a)z-tel.com)

1 participants
0 comments

tab breakage yet again (XEmacs 21.2.29 is released.) 25 years, 1 month

Karl Kleinpaste

Enclosed .gif for your edification and amusement. Just built 21.2-b29. xemacs -vanilla The background of the whole screen is white, showing the beta logo. Fine. But no tab is showing in the gutter at all. Type any key, it reverts to *scratch* buffer, still no tab showing. C-x C-b RET a few times, I can see a "*scratch*" tab flickering ever so briefly in the gutter, but it doesn't last, disappearing in a fraction of a second. C-x C-f .emacs RET and it loads my .emacs. Now there are two tabs showing in the gutter, for .emacs and *scratch*. M-x font-lock-mode RET and it colors the buffer properly. OK. C-x C-b RET a few times to switch back and forth between .emacs and *scratch*. When *scratch* is showing, there is no tab at all. When .emacs is showing, a "*scratch*" tab now appears by itself. For the final weirdness, please note from the image that the end of my .emacs contains a tab customization: '(buffers-tab ((t (:foreground "black" :background "wheat"))) t) I do this to ensure that tabs have discernible tab borders, because otherwise the white tab background is indistinguishable from the white gutter in which they sit. You will observe that the tab is in fact nonetheless in B&W, having disregarded the customization. This is the case even though M-x customize RET gutter RET, selecting the buffer tab selection, and opening the face spec shows that I do in fact have black-on-wheat selected. I'd like to nominate gutter & tabs as the most disastrous feature XEmacs 21.2 has had, because it's been in progress for months upon months, yet is still evidently nowhere near any concept of "right". --karl

2 participants
1 comments

Re: [pcl-cvs] I've got 2.9.7 working, and packages. 25 years, 1 month

Karl M. Hegbloom

>>>>> "Charles" == Charles G Waldman <cgw(a)fnal.gov> writes: Charles> I suggest we patch pcl-cvs.el to not use [easy-mmode]; I have the patch. May I have it? Charles> As far as diff-mode, I suggest that we add it to our pcl-cvs package. Or to `xemacs-devel'.

1 participants
0 comments

21.2.29 cygwin patch? Re: Problem compiling 21.2.28 on cygwin because of missing winspool.h 25 years, 1 month

Raymond Toy

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> At 10:56 AM 2/11/00 -0500, Raymond Toy wrote: >> I'd make the patch if someone could tell me what to do. Where is >> winspool.h? Can I just remove that? What about the Andy> Just #ifdef it out for cygwin < b21 Andy> PHYSICALHEIGHT >> warnings? Can I include Windows/Defines.h in s/cygwin32.h? Or just >> leave it out completely? Andy> You can just ignore them although its not tidy. Ok, here is the obvious patch for the winspool problem. Hope I got it right. :-) This lets me get past that problem on 21.2.29 and Cygwin B20.1 (finally upgraded). However, there's another problem in gui-msw.c: SE_ERR_PNF doesn't seem to be defined anywhere for me. I just patched the offending lines. I'm not sending these to xemacs-patches because I have no clue if these are even remotely correct. Ray winspool patch: --- device-msw.c~ Fri Feb 04 08:22:48 2000 +++ device-msw.c Wed Feb 16 13:14:30 2000 ＠＠ -39,7 +39,9 ＠＠ #include "frame.h" #include "sysdep.h" +#if CYGWIN_VERSION_DLL_MAJOR > 20 #include <winspool.h> +#endif /* win32 DDE management library globals */ #ifdef HAVE_DRAGNDROP SE_ERR_PNF patch: --- gui-msw.c~ Thu Feb 10 09:13:53 2000 +++ gui-msw.c Wed Feb 16 13:24:53 2000 ＠＠ -136,9 +136,17 ＠＠ if (ret > 32) return Qt; - if (ret == ERROR_FILE_NOT_FOUND || ret == SE_ERR_FNF) + if (ret == ERROR_FILE_NOT_FOUND +#if CYGWIN_VERSION_DLL_MAJOR > 20 + || ret == SE_ERR_FNF +#endif + ) signal_simple_error ("file not found", document); - else if (ret == ERROR_PATH_NOT_FOUND || ret == SE_ERR_PNF) + else if (ret == ERROR_PATH_NOT_FOUND +#if CYGWIN_VERSION_DLL_MAJOR > 20 + || ret == SE_ERR_PNF +#endif + ) signal_simple_error ("path not found", current_dir); else if (ret == ERROR_BAD_FORMAT) signal_simple_error ("bad executable format", document);

1 participants
0 comments

https://sourceforge.net/docs/site/services.php 25 years, 1 month

Martin Buchholz

Every sign indicates that sourceforge.net is really making a major effor to become the free software home that the FSF should have been and never quite was. Rumor has it they have 4 people working full-time to keep sourceforge.net running. People I respect have recommended it. Summary of SourceForge Services Following is a list of the services which we currently provide to SourceForge projects. We expect to continually add services and improve upon the services on this list. The SourceForge Team Development Environment (TDE) TDE Web Administrative Tools Advanced web-based administrative tools provide easy maintenance for all facets of your project. Web Server Apache HTTP Server, PHP3/PERL/CGI support, and a dedicated subdomain. Accounts are Apache VirtualHosts with separate /cgi-bin directories. 100MB space without monitoring - more if the space is justified. [Details...] MySQL Database Your shell account and web server have access to your own MySQL database. Your Own Domain If you make the registration with Internic, we can answer for your domain. This will affect all domains that would otherwise be referenced by yourproject.SourceForge.net. E-mail Lists (Public & Private) The Mailman mailing list manager and majordomo are available for your mailing lists. CVS Repository Each project has its own CVS repository (with separate CVSROOT). Developers are granted secure access to the tree through SSH. Anonymous CVS/pserver access is granted to the general public. [Details...] High-capacity File Server Released versions of your project are stored on our extreme-capacity fileserver. Current capacity for this server is 1000 concurrent ftp and 3000 concurrent http connections. Mid-capacity FTP directory Full read/write access to your own FTP directory, available anonymously to the outside world. Project Management Software Bug-Tracking System (Public & Private) Discussion Forums (Public & Private) SSH Account A restricted SSH account provides basic shell functions, your own crontab, and access to your HTTP account for you and all of your developers.

1 participants
0 comments

Re: CONST ==> const 25 years, 1 month

Tor Arntsen

n> Is this really a good idea? There's a really good reason that Jaime n> put in CONST, it's because const is broken in lots of environments n> (compilers+header files). m>The deed is done. Show me a broken system, and it'll be one that was m>already broken before the change. Jamie probably made that change m>around 1992, when ANSI C was only 3 years old. 'const' is broken on AIX 4.1/4.2, not for ordinary usage but debuggers don't want to show you the value of any 'const' parameter. Whenever I want to use a debugger I have to compile my stuff with '-Dconst=""'. Of course it's not any easier to mess around with the definition of CONST, but I thought I should just point it out. -Tor

1 participants
0 comments

Re: CONST ==> const 25 years, 1 month

Neal D. Becker

Is this really a good idea? There's a really good reason that Jaime put in CONST, it's because const is broken in lots of environments (compilers+header files).

2 participants
1 comments

Relocating allocator on Linux 25 years, 1 month

Hrvoje Niksic

On my Linux system, Libc info documentation states this about malloc(): Very large blocks (much larger than a page) are allocated with `mmap' (anonymous or via `/dev/zero') by this implementation. This has the great advantage that these chunks are returned to the system immediately when they are freed. Therefore, it cannot happen that a large chunk becomes "locked" in between smaller ones and even after calling `free' wastes memory. The size threshold for `mmap' to be used can be adjusted with `mallopt' [the default one is 128K --hniksic]. The use of `mmap' can also be disabled completely. It seems that our relocating allocator attempts to do what Doug Lea malloc() already does. The system-provided mmap-based allocation seems a better idea in XEmacs because it's performed for *all* large allocations (large vectors, strings, frob blocks etc.) rather than only for buffers, as our ralloc does. So I conducted the following test: 1) Allocate a 10M string with (prog1 nil (setq a (make-string 10000000 ?x))) 2) Allocate a 5M string with (prog1 nil (setq b (make-string 5000000 ?x))) 3) Remove reference to the first string and garbage collect. (setq a nil) (garbage-collect) 4) Remove reference to the second string, the same way. Sizes of the XEmacs process go like this (size/resident size, as reported by ps): Start: 8860 5640 (1) 18644 15444 (2) 23532 20332 (3) 13776 10572 (4) 8892 5692 Obviously, XEmacs grows by 10M, then by 5M more, then shrinks by 10M, and finally removes to original state. All that memory comes from strings, on an XEmacs compiled without relocating allocator. To me it seems that things work as advertised in the manual. Does this mean we ought to turn off relalloc on Linux for 21.2?

3 participants
2 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 February 2000