March 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Strange behavior with MULE and punctuation on 21.0.65,Solaris 25 years, 8 months

Andrew S. Howell

Hello, I'm seeing very strange behavior when typing away. Sometimes, when I type some punctuation, such as a comma or period, if a space follows it,a space gets put before the punctuation and the cursor moves to the left of the space. For example: A sentence . To get it to not do that, I have to type a letter right after the punctuation. This is OK.Note lack of space between sentences. Something even stranger, it sometimes makes the text like: The comma keeps following the next phrase ,this one right here. I have not used any input methods during this session with XEmacs. Any clues? Thanks, Andy

1 participants
0 comments

Error in XEmacs initialization 25 years, 8 months

Guido Van Hoecke

I have build xemacs-21.0.65 on an NT box using the egcs compiler and the cygwin b20.1 environment. I get an error after buidling temacs.exe. I have appended the shell buffer containing the configure process as well as the make process. I have no clue what went wrong, but I assume that this problem should better be known as early as possible. Guido.

2 participants
1 comments

[Didier Verna <verna@inf.enst.fr>] Re: extent-data in bbdb-xemacs.el :-( 25 years, 8 months

Didier Verna

This is probably of general interest after all. -- / / _ _ 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

Re: XEmacs GIF bug? 25 years, 8 months

Jareth Hein

>>>>> "SL" == SL Baur <steve(a)xemacs.org> writes: SL> I get a ton of GIF errors referencing the URL: SL> http://www.sinica.edu.tw/ftms-bin/ftmsw3 SL> (7) (error/warning) Error in process sentinel: SL> (image-conversion-error First image in GIF file is not full SL> size [gif :data GIF87a... This is an artifact of the way we deal with animated (or multiple image) files. I agree that putting up an error is rather lame, so what would you have me do? Just display the first frame floating in the full frame size, or just clip to the first frame size? -- Jareth Hein | jareth(a)camelot.co.jp | ハインジェラス Toolsmith & Program lead | http://www.camelot.co.jp | 開発部チーフ Camelot Software, Ltd. | |（株）キャメロット "It's a sad sign of the times when 'political machine' is redefined to include 'main-line battle tank'" - Ambassador Grossblunder

1 participants
0 comments

Re: decode-coding-region and encode-coding-region 25 years, 8 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > I think that if you somehow manage to create an extent that ends up > with endpoints inside a *-coding-region, you've screwed up somehow > anyway so an approximation should be fine. Maybe. Generally, I want to fix the case where Gnus properties get screwed merely because it encodes/decodes the region. > The real problem (and what I was really asking, now that I've slept > on it) is "what do you do when the text properties you have applied > don't make sense?" For example, Japanese has no italic or bold > (...) That's not my care, really. I merely make sure that the extents are preserved -- how the stuff stored in the extents will be handled is up to the redisplay code. > It seems to me that you probably want to split such extents, > preserve the meaning outside of the *-coding-region, and do > something (probably at user option) inside the *-coding-region. I will definitely not code something like that. What I want is conceptually very simple. I don't think I will kludge around Mule limitations more than absolutely necessary. I hope that by now it is at least clear *what* exactly I'd like decode/encode-coding-region to do. If it's not, then I'm seriously incapable of communiating my ideas.

2 participants
1 comments

Patches Not Yet Applied to 21.2 25 years, 8 months

Vin Shelton

With a scheduled Friday beta, I decided to review my list of outstanding XEmacs patches. I have not actually tested any of these patches, I merely successfully applied these patches to my 21.2 and xemacs-packages CVS trees using patch's --dry-run option, and they applied OK. Apologies if any of these patches have already been rejected, but I've noticed some people lately complaining about dropped patches, and I thought I might be able to help. If anyone needs any of these patches, drop me a line and I'll send 'em. Message-ID: <vgvemwhnv80.fsf(a)ms.com> Subject: Re: More C mode syntactic yuckage Message-ID: <13844.2626.312267.69833(a)lasker.worley.com> Subject: tl-list.el should not do (defconst :test ...) Message-ID: <qyjn26nr24u.fsf(a)metheny.enst.fr> Subject: [PATCH] balloon-help-MINOR-mode Message-ID: <13876.35228.330418.385565(a)tanko.sk.tsukuba.ac.jp> Subject: [patch] make reset-face a no-op for 'default face Message-Id: <199810280256.CAA24714(a)moomin.cs.ie.niigata-u.ac.jp> Subject: patch for fileio.c Message-ID: <kigg1ba2z4r.fsf(a)jagor.srce.hr> Subject: Setting keywords in cl-macs Message-ID: <uyaosacn5.fsf(a)ecf.teradyne.com> Subject: [PATCH] Adding features to hideif.el Message-Id: <199812011302.OAA07074(a)ull.tnt.uni-hannover.de> Subject: Patch for etags.el Message-ID: <qyjiufvfxth.fsf(a)metheny.enst.fr> Subject: [CORE DUMP => PATCH] related to menu accelerators Message-ID: <kig3e6ykvdh.fsf(a)jagor.srce.hr> Subject: try-oblique-before-italic-fonts Message-ID: <qyjogplb6bx.fsf(a)metheny.enst.fr> Subject: [PATCH] new splash buffer Message-ID: <kigk906i8fd.fsf(a)jagor.srce.hr> Subject: Provide `base64' Message-ID: <kigg1atzsx4.fsf(a)jagor.srce.hr> Subject: base64 some more Message-ID: <u1zma3042.fsf(a)ecf.teradyne.com> Subject: gud.el to handle paths including drive letter for Windows Message-ID: <kig3e6mk5nx.fsf(a)jagor.srce.hr> Subject: Followup to "various" patch: incorrect use of wrong_type_argument() Message-ID: <kig4sqynyqi.fsf(a)jagor.srce.hr> Subject: `make-annotation' fix Message-ID: <16083.914190825(a)rtp.ericsson.se> Subject: vc-cc infinite loop fix Message-ID: <y9lpv8vus9m.fsf(a)brabantio.informatik.uni-tuebingen.de> Subject: 21.0: INSTALL correction Message-ID: <13969.2012.132074.419585(a)onyx.nowhere.net> Subject: Font menu patch for 21.x Message-ID: <y9lpv8s3h2i.fsf(a)brabantio.informatik.uni-tuebingen.de> Subject: scheme.el syntax table fix Message-Id: <199901071952.UAA10001＠bolzano> Subject: [21.0] Make Mailcrypt use New style servers and pgp.net Message-ID: <13979.23662.426373.647190(a)amenardo.corpemea.baynetworks.com> Subject: extent-data cleanup for bbdb Message-ID: <qyjpv8c247c.fsf(a)metheny.enst.fr> Subject: [PATCH] splash buffer Message-ID: <14006.23613.500000.640080＠SLOTH> Subject: Patch to make highligh-headers display X-Face under NT Message-Id: <000601be4eb1$276bb2a0$3e766482(a)h225.ericsson.se> Subject: Patch to f90.el Message-ID: <hhu2wxtvcq.fsf(a)arioch.oche.de> Subject: Bug in file-regular-p Message-ID: <14027.32373.801182.620886(a)mulelab.etl.go.jp> Subject: YAP Message-ID: <14027.40120.264091.932366(a)mulelab.etl.go.jp> Subject: YAP Message-ID: <byd832wij4.fsf(a)bolzano.math.ethz.ch> Subject: [21.0] emacsbug.el should be in base tarball and use bugs(a)xemacs.org Message-ID: <14045.48269.345000.869502＠SLOTH> Subject: X-Face fix for highlight-headers Message-ID: <36E2AB69.1C35770C(a)tardis.ed.ac.uk> Subject: Fix non-MULE compilation failure on 21.2 Message-ID: <14051.18431.249794.265732(a)mulelab.etl.go.jp> Subject: Re: Fix non-MULE compilation failure on 21.2 Message-Id: <3.0.5.32.19990308162440.0097ce40(a)london.beasys.com> Subject: fix custom loading of package stuff Message-ID: <14051.38525.919591.427360(a)mulelab.etl.go.jp> Subject: Make "\x4e03" and ?\x4e03 stop crashing Message-ID: <14051.38891.117481.320912(a)mulelab.etl.go.jp> Subject: Add mule tests - a start. Message-ID: <14051.41035.812455.661971(a)mulelab.etl.go.jp> Subject: mule-wnnfns.c: warning suppression Message-ID: <14051.41260.441817.904620(a)mulelab.etl.go.jp> Subject: decosf4-0.h Message-ID: <14051.41437.362662.571635(a)mulelab.etl.go.jp> Subject: startup.el Message-ID: <14051.46807.322391.575103(a)mulelab.etl.go.jp> Subject: abbreviate-file-name doc fixes Message-ID: <14051.53989.35699.731981(a)mulelab.etl.go.jp> Subject: Fix up latin1 coding system doc strings Message-Id: <3.0.5.32.19990308162440.0097ce40(a)london.beasys.com> Subject: fix custom loading of package stuff Message-ID: <14051.64574.779251.344758(a)buffalo.fnal.gov> Subject: Spelling fix for where-was-i-db.el Message-ID: <14052.14254.407140.892641(a)scooter.sendmail.com> Subject: Properly detecting LDAP Message-ID: <14054.17976.75905.496337(a)tanko.sk.tsukuba.ac.jp> Subject: Improve doctrings in UCS-4 functions Message-ID: <byk8wpuq8z.fsf(a)bolzano.math.ethz.ch> Subject: [21.0, repost with more Rationale] Mix X resources with Custom I hope this is useful to someone. vin

1 participants
0 comments

Re: Package update problem 25 years, 8 months

SL Baur

Ian MacKinnon <IMacKinnon(a)TELIA.CO.UK> writes in xemacs-beta(a)xemacs.org: > gnus-1.39-pkg.tar.gz eval as below gives 0f412b7e791616213c70df1ab5d4aca8 > while package-get-base gives 5413e7508693bfcb16c5a4a0e0bce7c7 The latter is correct. Does it make any difference if you do: (let ((buffer-file-coding-system-for-read 'binary)) (md5 (with-temp-buffer (insert-file-contents "gnus-1.39-pkg.tar.gz") (buffer-string))))

1 participants
0 comments

Build failure: 21.2 Clio on Solaris 2.6 25 years, 8 months

Oscar Figueiredo

/usr/ccs/bin/ld does not grok the -Bexport switch on Solaris 2.6 and the build fails when trying to link temacs. Full report on xemacs-build-reports Oscar

2 participants
1 comments

Re: patch: Emacs fix for footnote.el.0.19 25 years, 8 months

SL Baur

I have applied this patch, thanks. Jari Aalto+mail emacs <jari.aalto(a)poboxes.com> writes in xemacs-beta(a)xemacs.org: > Hi, > I saw reference to this cool package in Gnus group and immediately > grabbed it from ftp://ftp.xemacs.org/pub/xemacs/packages/. > There was small error for Emacs, otherwise works fine. > jari > [2 footnote.el.0.19.diff <application/octet-stream>]

1 participants
0 comments

21.0-b65 failed under WinNT 4.0sp4 25 years, 8 months

Damon Lipparelli

Building with the attached batch file, the link fails with the following: link.exe ＠C:\TEMP\nma00294. file-coding.obj : error LNK2005: _lrecord_coding_system already defined in alloc.obj ..\src\temacs.exe : fatal error LNK1169: one or more multiply defined symbols found NMAKE : fatal error U1077: 'link.exe' : return code '0x491' -lipp <<build-nodebug-xemacs.bat>>

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