November 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: FSF named in federal antitrust action 26 years, 1 month

Jan Vroonhof

wmperry(a)aventail.com (William M. Perry) writes: > Wasn't sure if everybody had seen this yet. That's what I get for writing > a web browser I guess. :) You actually had me scared for second :-). This is definitely one for r.h.funny Jan

1 participants
0 comments

FSF named in federal antitrust action 26 years, 1 month

William M. Perry

Wasn't sure if everybody had seen this yet. That's what I get for writing a web browser I guess. :) -Bill P. Washington, D.C. -- The U.S. Department of Justice today announced a major new antitrust action against the Free Software Foundation of Cambridge, MA. "After our successful prosecution of Microsoft, we feel ready to pursue similar cases elsewhere in the software industry," said Attorney General Janet Reno in a press conference. "The FSF, under the guidance of Mr. Richard M. Stallman, has pursued, and continues to pursue, anti-competitive practices designed to perpetuate its illegal monopoly of the so-called 'free software' market." In particular, the Attorney General cited the FSF's ongoing effort to gain market share in various product categories by illegally bundling other products into their successful Emacs text editor. "Thanks to Judge Jackson, we now have legal precedent that a web browser cannot be considered part of an operating system," she said. "We feel that this finding is also applicable to text editors. Emacs, in fact, does include a web browser as well as e-mail and other capabilities that are not normally considered to be part and parcel of a text editor." Responding to a reporter's question, Ms. Reno confirmed that "Emacs is the primary focus of our action." Ms. Reno also addressed the FSF's ambitions in the operating system niche. "FSF had been attempting for some time to dominate the market for free operating systems with their 'GNU' platform. However, while they produced a number of user-level tools, their kernel was even more mythical than a reliable version of Windows 98 until their successful takeover of the Linux franchise, now known, significantly, as 'GNU/Linux'." Federal prosecutors Joel Klein and David Boies, both veterans of the successful Microsoft suit, are heading up the FSF enquiry. "I realize that some users feel that they use FSF products by choice," said Klein. "But how many Linux systems have you seen that don't have the core GNU utilities installed? Our estimate is that these programs are present on 100% of Linux machines. When such a high percentage of market share is held by one player, it's clear that an illegal monopoly exists." Initial analysis/speculation by various media talking heads failed to find consensus regarding the possible outcome of the government suit. At minimum, the government will most likely seek to have the FSF break out the various functional components of Emacs into separate products and discontinue the use of the anti-competitive GNU Public License, which has been described as a "free-software virus" which forces third-party software developers to release their products under terms dictated by the FSF. Other possibilities include punitive damages and even the breakup of the FSF into separate operating system and application groups.

1 participants
0 comments

[pdumper] "Cannot open doc string file..." 26 years, 1 month

Robin S. Socha

I tried compiling sneaky bastard with --pdump=yes. The make process failed (as promised) but when running temacs -f gnus, I get the following backtrace: Signaling: (error "Cannot open doc string file \"../lib-src/../lisp/gnus-art.elc\"") ad-Orig-documentation(article-hide-headers t) documentation(article-hide-headers t) #<compiled-function (func) "...(61)" [nil gfunc afunc func intern format "gnus-%s" fboundp lambda (&optional interactive &rest args) documentation t (interactive ...) save-excursion (set-buffer gnus-article-buffer) if interactive call-interactively quote apply (args)] 13>(article-hide-headers) mapcar(#<compiled-function (func) "...(61)" [nil gfunc afunc func intern format "gnus-%s" fboundp lambda (&optional interactive &rest args) documentation t (interactive ...) save-excursion (set-buffer gnus-article-buffer) if interactive call-interactively quote apply (args)] 13> (article-hide-headers article-hide-boring-headers article-treat-overstrike article-fill-long-lines article-capitalize-sentences article-remove-cr article-display-x-face article-de-quoted-unreadable article-mime-decode-quoted-printable article-hide-list-identifiers article-hide-pgp article-strip-banner article-babel article-hide-pem article-hide-signature article-strip-headers-in-body article-remove-trailing-blank-lines article-strip-leading-blank-lines article-strip-multiple-blank-lines article-strip-leading-space article-strip-trailing-space article-strip-blank-lines article-strip-all-blank-lines article-date-local article-date-iso8601 article-date-original article-date-ut article-decode-mime-words ! article-decode-charset article-decode-encoded-words article-date-user article-date-lapsed article-emphasize article-treat-dumbquotes article-normalize-headers (article-show-all . gnus-article-show-all-headers))) byte-code("..." [mapcar #<compiled-function (func) "...(61)" [nil gfunc afunc func intern format "gnus-%s" fboundp lambda ... documentation t ... save-excursion ... if interactive call-interactively quote apply ...] 13> (article-hide-headers article-hide-boring-headers article-treat-overstrike article-fill-long-lines article-capitalize-sentences article-remove-cr article-display-x-face article-de-quoted-unreadable article-mime-decode-quoted-printable article-hide-list-identifiers article-hide-pgp article-strip-banner article-babel article-hide-pem article-hide-signature article-strip-headers-in-body article-remove-trailing-blank-lines article-strip-leading-blank-lines article-strip-multiple-blank-lines article-strip-leading-space article-strip-trailing-space article-strip-blank-lines article-strip-all-blank-lines article-date-local article-date-iso8601 article-date-original article-date-ut article-decode-mime-words article-decode-charset article-decode-encoded-words article-! date-user article-date-lapsed article-emphasize article-treat-dumbquotes article-normalize-headers (article-show-all . gnus-article-show-all-headers)) put gnus-article-mode mode-class special set-keymap-parent gnus-article-mode-map widget-keymap gnus-define-keys-1 (" " gnus-article-goto-next-page "" gnus-article-goto-prev-page [delete] gnus-article-goto-prev-page [backspace] gnus-article-goto-prev-page "^" gnus-article-refer-article "h" gnus-article-show-summary "s" gnus-article-show-summary " " gnus-article-mail "?" gnus-article-describe-briefly "e" gnus-article-edit "<" beginning-of-buffer ">" end-of-buffer " " gnus-info-find-node "" gnus-bug "" gnus-article-read-summary-keys "ª" gnus-article-read-summary-keys "£" gnus-article-read-summary-keys "Þ" gnus-article-read-summary-keys "ç" gnus-article-read-summary-keys) substitute-key-definition undefined gnus-article-read-summary-keys] 4) load-internal("gnus-art" nil nil nil nil nil) load("gnus-art" nil nil nil) gnus-article-prepare(3782 nil) gnus-summary-display-article(3782 nil) gnus-summary-select-article(nil nil pseudo) gnus-summary-scroll-up(1) call-interactively(gnus-summary-scroll-up) I will be away from my mail for a few days, so if that isn't enough, I'm really sorry ;-) -- Robin S. Socha <http://socha.net/>

1 participants
0 comments

Re: [HEADS UP] movemail locking overhaul ahead 26 years, 1 month

Michael Sperber

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: Jan> I propose that it should (by default) always use dotlocking (even Jan> together with any other method). >> >> I don't believe that's a good idea: Locking would no longer be atomic, >> and you can get deadlocks that way. Jan> Not if everybody acquires the locks in the same order. Which is indeed Jan> the case. What's the order? And why is this the case? Is there a standard or agreement on this? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: JOBS list for XEmacs 26 years, 1 month

Jan Vroonhof

Ben Wing <ben(a)xemacs.org>, Martin Buchholz <martin(a)xemacs.org> writes: > Core Patch Tender Jan Vroonhof Andy Piper, Martin Buchholz What have I just volunteered for? i.e. what is job description for this. > Bug Tracker This currently de facto "Gunnar Evermann" > README README Martin Buchholz Is the README maintaining itself? > Configure support Martin Buchholz > Mule Ben Wing, Martin Buchhlz, Olivier Galibert > GUI support Andy Piper > Redisplay Andy Piper Customize Jan Vroonhof Jan

1 participants
0 comments

Re: [HEADS UP] movemail locking overhaul ahead 26 years, 1 month

Jan Vroonhof

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > Jan> I propose that it should (by default) always use dotlocking (even > Jan> together with any other method). > > I don't believe that's a good idea: Locking would no longer be atomic, > and you can get deadlocks that way. Not if everybody acquires the locks in the same order. Which is indeed the case. Note that for instance mutt uses the combination .lock+fcntl() by default. Jan

1 participants
0 comments

Re: [HEADS UP] movemail locking overhaul ahead 26 years, 1 month

Michael Sperber

>>>>> "Glynn" == Glynn Clements <glynn(a)sensei.co.uk> writes: Glynn> Michael Sperber [Mr. Preprocessor] wrote: Jan> I propose that it should (by default) always use dotlocking (even Jan> together with any other method). >> >> I don't believe that's a good idea: Locking would no longer be atomic, >> and you can get deadlocks that way. Glynn> I don't think that it's that big a problem. If the second lock fails, Glynn> you release the first lock and wait for a bit. Then the worst that can Glynn> happen is a livelock. I'd rather avoid the complexity. Sysadmins *need* to coordinate locking methods between MDA and MUA, and that's easiest when theres a 1-1 match. Glynn> FWIW, procmail (on Linux at least) uses both dot-locking and kernel Glynn> locks (can't remember whether it's flock, fcntl or lockf). That depends on how it's configured. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: URL loading library? 26 years, 1 month

William M. Perry

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > I was contemplating finally rewriting the HTTP code in Emacs/W3 in > > C. Does anybody have ideas for what HTTP library to use? I'd > > prefer not having to write it myself. The `libghttp' stuff from > > gnome looks like it could be useful. It can do asynch fetches, etc. > > A friend of mine has looked into libghttp and told me it's entirely > broken. I haven't checked, but I've a hunch that he might be right. It seems to be woefully inadequate for what we need. :( > Wget is hardly useful for your purposes -- as I no longer have time for > it (see > http://fly.srk.fer.hr/archive/wget?id=87wvs347gk.fsf＠pc-hrvoje.srce.hr), > it grows dusty, and it was never able to do async downloads in the first > place. That's what I was afraid of. :( Oh well. :) > I was told that libwww is in much better shape than it was four years ago > (people in the Lynx project also had bad experiences with old versions), > and it's compatible with the GPL. The old versions were pretty nasty... I added SSL and HTTPS support to the (then CERN) web server at spry. God what a memory. :) I downloaded it last night, but can't get it to even configure because of automake weirdness. *sigh* -Bill P.

1 participants
0 comments

Re: (insert 8000) crashes XEmacs 21.2.16 26 years, 1 month

Hrvoje Niksic

Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> writes: > 1999-11-08 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> > > * mule-charset.h (breakup_char_1): Check whether > charset exists or not. > breakup_char_1() might not be the right place for this fix. It seems that function assumes it will get an existing charset. Maybe a more appropriate fix would be up at the callers? Also, I see that BREAKUP_CHAR is called from within redisplay. In redisplay, an error will cause a coredump.

5 participants
8 comments

Re: JOBS list for XEmacs 26 years, 1 month

Andreas Jaeger

>>>>> Ben Wing writes: Ben> Ben and I have come up with a tentative list of XEmacs `jobs', or Ben> areas of responsibility. The idea here is that the people listed as Ben> `Primary' are responsible for any problems in this area. However, in Ben> the event that all of the listed Primaries disapppear and become Ben> unresponsive to email, the Secondary agrees to step up and take over, Ben> at least temporarily. Please suggest changes and additions to this Ben> list. It will be wonderful if people would volunteer for unfilled Ben> positions. Thanks a lot for coming up with this list. We should archive this file somewhere for _internal_ together use with email addresses. I'm missing one position: Package Release Maintainer. It seems that this will be part of my job but I'd like to have it as a separat position for documentation and in case anybody else likes to do this. Ben> Position Primary Secondary Ben> ------------------------------------------------------------ Ben> Beta Release Maintainer Martin Buchholz Ben> Stable Release Maintainer Vinnie Shelton Ben> Jobs-List-Maintainer Ben Wing Ben> Japanese Liaison Stephen Turnbull Ben> Core Patch Tender Jan Vroonhof Andy Piper, Martin Buchholz Ben> Package Patch Tender Andreas Jaeger Martin Buchholz Ben> CVS Manager Jareth Hein Ben> Mailing List Manager Jason Mastaler Martin Buchholz Ben> Webmaster John Anderson Ben> Bug Tracker Ben> Miscellaneous Documentation Ben> --------------------------- Ben> Lisp Reference Manual Martin Buchholz Ben> XEmacs User Manual Martin Buchholz Ben> Internals Manual Martin Buchholz Ben> PROBLEMS Martin Buchholz Ben> FAQ Martin Buchholz Ben> NEWS Hrvoje Niksic Martin Buchholz Ben> README README Martin Buchholz Ben> Coding Projects Ben> --------------- Ben> Coding Standards Martin Buchholz Ben> Portable Dumper Olivier Galibert Ben> Windows support Ben> Configure support Martin Buchholz Ben> Mule Ben Wing, Martin Buchhlz, Olivier Galibert Martin, there's a typo in your name - it seems you've written it down to often;-) Ben> GUI support Andy Piper Ben> Redisplay Andy Piper I hope others fill in the empty spaces, Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

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