August 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Where do you want to go tomorrow? 26 years, 3 months

Karl M. Hegbloom

1 participants
0 comments

[bug] background color setting 26 years, 3 months

Karl M. Hegbloom

1 participants
0 comments

Re: User Poll: Do you have access to PNG libraries? 26 years, 3 months

Oliver Graf

Mike Scheidler <c23mts(a)eng.delcoelect.com> writes: > >> Why is XPM superiour to PNG? Cause it's plain text? > Glynn> > Glynn> That's an advantage (IMHO), but the main issue for me is symbolic > Glynn> colour names. > > I second Glynn's comments. The XPM format is great for things like toolbar > icons because of the configurability that symbolic color names offer. I > don't know much about the PNG format, but unless it has similar symbolic > color capabilities, it would be a net loss, IMHO. It can have. Cause PNG is the ability to add private tags, we could use this feature to add symbolic names to a palette. This will *not* break the png for 'standart' PNG libs/viewers/converters, but XEmacs (who will know those tags) can use them to change the colors. If you (and the others) are interested in such an addition, here is a short example how it will look like (I can also code this example, but first tell me if you and the others will accept such an addition): Each png image will have a standart PLTE (Palette; critical, public, unsafe to copy) chunk. This will define the colors of the png image. In addition there will be a syMN (Symbolic Names; uncritical, private, unsafe to copy) chunk which lists color names mapped to pallette indicies. If the docoder (XEmacs in our case) 'knows' syMn, he will try to change the symbolic colors. In the case the chunk is not known, a viewer will ignore it without a warning, but an editor which does not know it, will complain and don't copy it, cause the image may change if the palette is changed. A simple converter can do the job converting XPM to PNG and preserve the symbolic names, but it is also an easy task to write an 'Palette Symbolic Name Editor' which will give the 'programmer/painter' the ability to edit the symbolic names of the palette (this is no workaround, cause currently there is no drawing program which will let you edit such sym names -- you always have to use an editor to do the job). So we will have sym names and the advantage of having small image files in one format: PNG. Regards, Oliver.

1 participants
0 comments

Latest PNG (1.0.2) is OK 26 years, 3 months

Amir J. Katz

Just rebuilt xemacs 21.0-b50 on SunOS 4.1.4 with latest PNG/ZLIB (1.0.2/1.1.3, respectively). Looks cool. FYI. -- /* Amir J. Katz mailto:amir＠nuke-spam.com */ /* [For e-mail, replace 'nuke-spam' with 'ndsoft'] */ /* EagleEye Control Software, LTD. http://www.ndsoft.com */ /* 'Is "tired old cliche" one?' (Steven Wright) */

1 participants
0 comments

Two silly XEmacs questions 26 years, 3 months

Amir J. Katz

1. Wanting to always be on XEmacs' bleeding edge, which version whould I be using now, 21.0-b50, or 21.2-b1? 2. When a new version of a package is released, is it enough to unpack it, then do this: rm lib-src/DOC gmake Or should something else be done? Thanks. -- /* Amir J. Katz mailto:amir＠nuke-spam.com */ /* [For e-mail, replace 'nuke-spam' with 'ndsoft'] */ /* EagleEye Control Software, LTD. http://www.ndsoft.com */ /* 'Is "tired old cliche" one?' (Steven Wright) */

1 participants
0 comments

Re: [crash] Corsican-pre4, 24 bpp color 26 years, 3 months

SL Baur

Karl M Hegbloom <karlheg(a)inetarena.com> writes in xemacs-beta(a)xemacs.org: >>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> What version of libpng? Have you tried it with 1.0.2 and zlib sb> 1.1.2 (patched) or zlib 1.1.3? > libpng.so.2.0, from the libpng2 debian package versioned 1.0.1-0.2 > libz.so.1.1.2 from zlib1g 1:1.1.2-0.1 > Looks like I'm a version behind yous. Are the changes something that > might fix this crash? Yup. I experienced corrupted images with 1.0.1 that were cured by upgrading to 1.0.2. Didn't you see my messages and Jareth's messages about this? > Are the newer versions out there? Yes. I got my copies from ftp.uu.net. > I will look for a newer deb of it, and can report a bug against the > package, saying that "a new upstream version has been released, > please update your package". sb> What version of EGCS? There have been some problems with the sb> latest snapshots. Does the same thing happen if you turn off sb> file-coding? I haven't tried it straight no-Mule or no-Mule sb> with file coding, and I build with EGCS/PGCC 1.0.3. > egcc 2.90.29-0.6, from source version 1.0.3a-0.6 That should be O.K. > I have not tried to turn off file coding, yet. If that cures it, > I'll post. That's still something to try *before* you update libpng if possible. > First I have to try and get pcmcia-cs working on the darn laptop so I > can net to my desktop workstation, and thus through to the Internet. > I've been sneakernetting the crash typescripts on a floppy. Grrr. Good luck!

1 participants
0 comments

Re: [crash] Corsican-pre4, 24 bpp color 26 years, 3 months

Karl M. Hegbloom

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> What version of libpng? Have you tried it with 1.0.2 and zlib sb> 1.1.2 (patched) or zlib 1.1.3? libpng.so.2.0, from the libpng2 debian package versioned 1.0.1-0.2 libz.so.1.1.2 from zlib1g 1:1.1.2-0.1 Looks like I'm a version behind yous. Are the changes something that might fix this crash? Are the newer versions out there? I will look for a newer deb of it, and can report a bug against the package, saying that "a new upstream version has been released, please update your package". sb> What version of EGCS? There have been some problems with the sb> latest snapshots. Does the same thing happen if you turn off sb> file-coding? I haven't tried it straight no-Mule or no-Mule sb> with file coding, and I build with EGCS/PGCC 1.0.3. egcc 2.90.29-0.6, from source version 1.0.3a-0.6 I have not tried to turn off file coding, yet. If that cures it, I'll post. First I have to try and get pcmcia-cs working on the darn laptop so I can net to my desktop workstation, and thus through to the Internet. I've been sneakernetting the crash typescripts on a floppy. Grrr.

1 participants
0 comments

[crash] Corsican-pre4 26 years, 3 months

Karl M. Hegbloom

Using customize again. I was setting the man page backing glyph (for the modified version of the man.el from FSF Emacs that I use) because it's a "png", and has vertical stripes through it. (24bit display).

1 participants
0 comments

vacation 26 years, 3 months

Michael Harnois

I'm on vacation for three weeks starting tomorrow. I'll be ready to build 22.1 when I get back ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mharnois(a)sbt.net aa0bt(a)aa0bt.ampr.org "The deadliest bullshit is odorless and transparent." -- William Gibson

1 participants
0 comments

Re: [crash] Corsican-pre4, 24 bpp color 26 years, 3 months

SL Baur

I normally run in 24 bit color and haven't had any further problems since Jareth's last patch. Karl M Hegbloom <karlheg(a)inetarena.com> writes in xemacs-beta(a)xemacs.org: > The "Installation" file is at the end, after the `gdb' typescript. > This happens consistently on my laptop, which has a 24bpp 800x600 > display. > `gdb xemacs' > `set args -geometry 80x35' > `run' I've tried starting it this way and doing the procedure below and it worked normally. > [ Options | Customize | Face... ] default, STATE, show all, INS, type > X, class color, bg dark, ... somewhere in here it will crash when I > click a button. The graphical buttons (Set, Save, ...) have vertical > stripes through them. It looks like it's not working right for 24bit > color. Here's a picture: > [2 striped-buttons.png <image/png>] What version of libpng? Have you tried it with 1.0.2 and zlib 1.1.2 (patched) or zlib 1.1.3? What version of EGCS? There have been some problems with the latest snapshots. Does the same thing happen if you turn off file-coding? I haven't tried it straight no-Mule or no-Mule with file coding, and I build with EGCS/PGCC 1.0.3. > ./configure '--compiler=egcc' '--cflags=-mpentium -O3 -g' '--with-gnu-make' '--gung-ho' '--with-menubars=lucid' '--with-scrollbars=lucid' '--with-dialogs=athena3d' '--with-sound=both' '--with-gpm=no' '--with-site-lisp=yes' '--package-path=~/.xemacs/::/usr/local/share/xemacs/' '--infopath=/usr/info:/usr/local/info:~/.xemacs/info' '--debug=no' '--error-checking=none' '--with-file-coding' > What compiler should XEmacs be built with? egcc -mpentium -O3 -g > Compiling in File coding support.

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 August 1998