July 1998 - XEmacs-Beta - XEmacs Mailing List Archives

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

SL Baur

Andy Piper <andyp(a)parallax.co.uk> writes in xemacs-beta(a)xemacs.org: > At 17:19 30/07/98 -0700, SL Baur wrote: >> At this point in time, "internal Xpm images" are the photos in >> etc/photos. I'm also thinking of the toolbar icons, unless there's an >> immediate problem with it. > The big advantage of xpm is that you can compose images on the fly. I don't > see how we could ever do this in PNG. ? > I certainly hope we're not thinking of ditching xpm. Nope. So long as Nothing Bad Happens, like what happened with GIF, we'll always have XPM support available. I'm only hoping to push the lion's share of the graphics duties to PNG. It's Free, it's portable, it's efficient and it easily deals with modern hardware. Other things being equal we should use it everywhere we can. We still have need for XPM and symbolic names, I'm not proposing to make that go away without an equivalent.

2 participants
1 comments

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

A.J. Rossini

Mike Scheidler <c23mts(a)eng.delcoelect.com> writes: > "Glynn" == Glynn Clements <glynn(a)sensei.co.uk> writes: > Glynn> Xpm images is also straightforward (via xpm-color-symbols), provided > Glynn> that they have symbolic colours defined. > 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. > > Currently, the XEmacs toolbar makes some use of symbolic colors, but a lot > more could be done in this area. Is XPM support and the symbolic names necessarily true for Microsoft Windows OS's, as well? -- A.J. Rossini Rsrch Asst. Professor Senior Biostatistician Biostatistics, University of Washington Epimetrics Corporation Center for AIDS Research 2101 9th Ave. arossini(a)biostat.washington.edu rossini(a)epimetrics.com

2 participants
1 comments

Re: Packages-Info ... 26 years, 4 months

Michael Sperber

>>>>> "Holger" == Holger Schauer <schauer(a)coling.uni-freiburg.de> writes: >>>>> "MS" == Michael Sperber schrieb am 30 Jul 1998 19:17:51 +0200: Holger> Comments on your comments/additions. MS> Note I've already integrated this stuff, with numerous changes of MS> my own, into the Texinfo docs. Please refer to that. Holger> But where did you integrate it ? Did you spread it all around the Holger> various info files ? At least, as of Benadir, under "XEmacs:Packages" Benadir doesn't have the changes. You need Corsican. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Packages-Info ... 26 years, 4 months

Holger Schauer

>>>>"MS" == Michael Sperber schrieb am 30 Jul 1998 19:17:51 +0200: Holger> Comments on your comments/additions. MS> Note I've already integrated this stuff, with numerous changes of MS> my own, into the Texinfo docs. Please refer to that. But where did you integrate it ? Did you spread it all around the various info files ? At least, as of Benadir, under "XEmacs:Packages" I only find a very tight "Introduction" in which I cannot find any of the points discussed in the article referred to above. A grep on the info dir revelaed an entry discussing directories in xemacs-info-3, but that's all I could find. A related question: how should a new user learn about packages (and which to download first) when all documentation is hidden in the info-files ? I thought we were talking about a starter-up document. Holger -- --- http://www.coling.uni-freiburg.de/~schauer --- "Drucker? Wer braucht denn - als _Schueler_ - Geraetschaften zum automatischen Beschriften toter Baeume?" -- Holger Lubitz in de.comp.os.linux.misc

1 participants
0 comments

Re: xemacs-21.0-b50: package-get 26 years, 4 months

SL Baur

Michael Kifer <kifer(a)cs.sunysb.edu> writes in xemacs-beta(a)xemacs.org: > Steve, are you sure? Yes. > This is what I had before, and this gave me the error. > I changed () to nil and the error was gone. $ grep 'requires ()' package-get-base.el | wc -l 15 If this one is wrong, why aren't the other 14 instances causing problems as well? > (I still get the error that efs-ftp-path is undefined when I try package-get. > But this is a different bug report.) O.K. That symbol is properly autoloaded in EFS, so perhaps a stronger check needs to be made for EFS availability.

1 participants
0 comments

Re: smart save-buffer 26 years, 4 months

Colin Rafferty

David Bakhash writes: > I was wondering what people would think of a smarter `save-buffer' > function. I was thinking that, if a file has been auto-saved since > the last time it was edited, then C-s (save-buffer) should maybe save > by renaming the auto-save file to the file itself. This would only work if the buffer has not changed since it has last been auto-saved. If there have been any changes since, then we need to do the real save. Also, if the `write-contents-hooks' makes modifications, then we will lose. And finally, if the auto-save file is on a different partition than the actual file, moving the auto-save file is no cheaper than doing the save itself. This last issue is realistic. I use the `auto-save' package[1], so all my autosave files are on local disk. > That would be faster, right? (especially for our VM folders :-) Unfortunately, not. -- Colin Footnotes: [1] Once people find out about this package, they usually jump to it. The package puts all the autosave files in the same directory. It gives you the function `recover-all-files' for after a crash. Also, if you have a slow network, make the auto-save-directory a local directory.

1 participants
0 comments

Re: xemacs-21.0-b50: package-get 26 years, 4 months

SL Baur

[If you have a CVS tree, `cd lisp; cvs update package-get-base.el'] Kevin Oberman <oberman(a)es.net> writes in xemacs-beta(a)xemacs.org: > Argh! These packages will be the end of me, yet. You're O.K. Kevin. > Can anyone tell me what I should put into the Makefile for wp/tpu to > fix this? Right now it simply contains "REQUIRES =". As you might > guess, it does not require anything. I thought Steve had edited this > line. I don't think I did, but I might have. If I messed it up, sorry! > Should it be "REQUIRES = "()"" or something else? The problem was in the package-info template file package-info.in. `REQUIRES=' is correct for the Makefile. requires (REQUIRES) is correct for the package-info.in file -- the `REQUIRES' token gets substituted with the contents of the right side of the equals sign in the Makefile. When `REQUIRES' is the empty string, it becomes `requires ()' which is interpreted as `require nil'. The current package-get-base file has everything correct: (tpu (standards-version 1.0 version "1.05" author-version "4.2X" date "1998-07-23" build-date "1998-07-28" maintainer "Kevin Oberman <oberman(a)es.net>" distribution normal priority medium category "wp" dump nil description "DEC EDIT/TPU support." filename "tpu-1.05-pkg.tar.gz" md5sum "ea158daa3dd9c98cee4acaff78866f0c" size 57851 provides (tpu) requires () type regular ))

2 participants
1 comments

Re: xemacs-21.0-b50: --with-mule problem 26 years, 4 months

SL Baur

Michael Kifer <kifer(a)cs.sunysb.edu> writes in xemacs-beta(a)xemacs.org: > If I use configure --with-mule but the mule-base package isn't installed, > I get > Error: dumped file mule-charset.elc does not exist > Error: dumped file mule-coding.elc does not exist > Error: dumped file mule-files.elc does not exist > Error: dumped file mule-help.elc does not exist > at the time xemacs gets dumped. > I think configure.in should check in lisp/mule-base exists, if > --with-mule is specified on command line. This way the user will be > notified right away of the problem. Noted. I don't think it should be made an error requiring a rerun of configure though, because an appropriate symbolic link can be made after getting the errors you note above and the build can procede without further recompilation.

1 participants
0 comments

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

SL Baur

A J Rossini <arossini(a)biostat.washington.edu> writes in xemacs-beta(a)xemacs.org: > Is XPM support and the symbolic names necessarily true for Microsoft > Windows OS's, as well? It is as alien a format as PNG is, relatively speaking. Of course on anything but Linux[1], Xpm is an alien format there too. I have yet to figure out how to build Xpm in one-pass on a system without either of: 1. A working xmkmf (it's unbelievable that vendors ship X11 without a functional xmkmf, no wonder Unix graphics gets a bad rap :-() 2. A previously installed Xpm (building sxpm and cxpm puke and die). Building PNG and zlib has gone without a hitch on all the systems I've tried it on. Footnotes: [1] Make that some installations of Linux. I thought PNG was a standard part of every Linux distribution, but I've already gotten a report about one where it is not.

1 participants
0 comments

Re: [comp.emacs.xemacs] Re: from *.h to *.cc and vice versa ? 26 years, 4 months

SL Baur

nbecker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org: > Where can I find find-file.el? TIA. Whereever you get FSF GNU Emacs. $ locate find-file.el /home/xemacs/emacs-19.34/lisp/find-file.el.gz /home/xemacs/emacs-19.34/lisp/find-file.elc.gz /home/xemacs/emacs-20.1/lisp/find-file.el.gz /home/xemacs/emacs-20.1/lisp/find-file.elc.gz /home/xemacs/emacs-20.2/lisp/find-file.el /home/xemacs/emacs-20.2/lisp/find-file.elc /home/xemacs/gnumule-19.34.94.zeta/lisp/find-file.el.gz /home/xemacs/gnumule-19.34.94.zeta/lisp/find-file.elc.gz /usr/local/share/emacs/19.34/lisp/find-file.el /usr/local/share/emacs/19.34/lisp/find-file.elc /usr/local/share/emacs/20.1/lisp/find-file.el /usr/local/share/emacs/20.1/lisp/find-file.elc

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