May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Custom font-handling is broken yet again 25 years, 6 months

Jan Vroonhof

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > It's removing specifications with tags on them (specifically, it is > once again nuking _all_ '(mule-tags) fonts on 'default). This is in > 21.2.14 Dionysos. That is strange. The new specifier tags based mechanism is supposed to touch (create/remove) only those specification with a "custom" tag. Could you find out where this is happening? > IMHO, Custom should not be touching _anything_ it doesn't put on the > specifier itself. But that's arguable. > > It is not arguable that it is evil for Custom to touch any > specification with a non-null tagset that doesn't include Custom's > signature. If I put a specification with a tag on it on a specifier, > Custom had better leave it alone. The tag based mechanism should do neither of these. Jan

1 participants
0 comments

package-get and PGP signature 25 years, 6 months

Norbert Koch

Hi, have I missed something or why do I get a Package-get PGP signature failed to verify error message when I try to pui-list-packages (from the mirror ftp.tu-darmstadt.de)? Thanks, norbert.

1 participants
0 comments

Custom font-handling is broken yet again 25 years, 6 months

Stephen J. Turnbull

It's removing specifications with tags on them (specifically, it is once again nuking _all_ '(mule-tags) fonts on 'default). This is in 21.2.14 Dionysos. IMHO, Custom should not be touching _anything_ it doesn't put on the specifier itself. But that's arguable. It is not arguable that it is evil for Custom to touch any specification with a non-null tagset that doesn't include Custom's signature. If I put a specification with a tag on it on a specifier, Custom had better leave it alone. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."

1 participants
0 comments

Re: Wie werde ich eine Mailingliste los [was Re: Test] 25 years, 6 months

Jason R Mastaler

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > P.P.S F�r weitere fragen k�nnen Sie sich (auf English!) melden bei > list-manager(a)xemacs.org Ja. Englisch bitte, weil ich nicht Deutsches verstehe. :-) Entsprechend meinen S�tzen wird `kalleske(a)redseven.de' zur "xemacs-beta" unterzeichnet. Dank.

1 participants
0 comments

Re: base64 decoding ignore whitespace 25 years, 6 months

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > It's required by the MIME spec. RFC 2045, page 26, > > Any characters outside of the base64 alphabet are to be ignored in > base64-encoded data. > > So this is a very welcome patch. I added base64 en/decoding without ever reading the specs. Ain't I cool? All out of my clever little head. :-) Just kidding... But that snippet means that we should ignore *anything* outside the base64 alphabet. In that case, *every* string would "decode" validly, even "\0\1\hi!". Do you think that's a good idea? If yes, I'll change the code (it's easy.)

2 participants
1 comments

mm.el in pgnus outdated 25 years, 6 months

Tom Roth

I could just track down my problems with inline decoding of html-mail in vm to an outdated version of mm.el in pgnus. i was receiving "Replacing authorization method `%s' - this could be bad." warnings. This i tracked down to an undeclared variable mm-mime-data-default. This again was due to an outdated version of mm.el that gets loaded from the pgnus directorie. Therefore the correct version of mm.el was never loaded from the w3 directorie. Though this probably only an issue with my installation of pgnus, I would like to sugest now that there should be only one file of mm.el. gruss/regards tom roth

1 participants
0 comments

base64 decoding ignore whitespace 25 years, 6 months

Kyle Jones

Hrvoje Niksic writes: > This patch makes base64 decoding process ignore whitespace, resulting > in a more robust decoding process. This is what many other decoders > do. It's required by the MIME spec. RFC 2045, page 26, Any characters outside of the base64 alphabet are to be ignored in base64-encoded data. So this is a very welcome patch.

1 participants
0 comments

Re: Test 25 years, 6 months

Leonard Blanks

>>>>> "K" == Kalleske <Kalleske(a)t-online.de> writes in >>>>> xemacs-beta(a)xemacs.org: K> Test-e-Mail! K> Sämtliche eMails, die an diese Adresse (xemacs-beta(a)xemacs.org) geschickt K> werden, werden weitergeleitet nach Kalleskeke(a)t-online.de !!! K> WARUM ??? K> (Bitte kontrollieren sie ihr e-Mail-Management-System) He wants to know why he has been receiving xemacs-beta posts since he is not - one assumes - subscribed to the list. I saw this as my chance to contribute *something* even though the list is awash with native German speakers (who understandably might be speechless following last night's debacle in the cup final) who are certainly more adept at translation than I. -- Len If the radiance of a thousand suns were to burst at once into the sky that would be like the splendor of the Mighty One ... I am become Death, the Shatterer of Worlds. -- J. Robert Oppenheimer, quoting "The Bhagavad Gita", 1945

1 participants
0 comments

Re: Wie werde ich eine Mailingliste los [was Re: Test] 25 years, 6 months

Didier Verna

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > P.S. Bitte benutzen Sie English wenn sie nicht 100% sicher sind das > die Angesprochene Personen Deutsch verstehen. This, I think I understood :-) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Wie werde ich eine Mailingliste los [was Re: Test] 25 years, 6 months

Jan Vroonhof

Kalleske(a)t-online.de (Kalleske) writes: > Sämtliche eMails, die an diese Adresse (xemacs-beta(a)xemacs.org) geschickt > werden, werden weitergeleitet nach Kalleskeke(a)t-online.de !!! > WARUM ??? Weil xemacs-beta(a)xemacs.org eine Diskusionsliste ist worauf man sich abonnieren kann. Sie sind anscheinend abonniert worden, das bedeutet also entweder 1. Sie haben sich selber versehentlich abonniert (unwahrscheinlich). 2. Sie sind neu beim T online und haben die gleiche Adresse gekriegt wie eine frühere Benützer der abonniert war. 3. Jemand hat Sie Böswillig abonniert. Sie können den Abo aufheben, indem Sie eine Mail zu schicken an xemacs-request(a)xemacs.org mit als Inhalt == schneiden === unsubscribe end == schneiden === Jan P.S. Bitte benutzen Sie English wenn sie nicht 100% sicher sind das die Angesprochene Personen Deutsch verstehen. P.P.S Für weitere fragen können Sie sich (auf English!) melden bei list-manager(a)xemacs.org

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