July 1998 - XEmacs-Beta - XEmacs Mailing List Archives

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

Neal D. Becker

Where can I find find-file.el? TIA.

1 participants
0 comments

William M. Perry

Andy Piper <andyp(a)parallax.co.uk> writes: > >In case anyone is interested I have successfully downloaded my mail from > >a exchange-based pop server using movemail and split and read the mail > >as news using the nnfolder backend of gnus. > > > >All out-of-the-box 21.0b50 under WindowsNT/cygwin32. > > > >Still haven't decided how I'm going split the mail between gnus and > >A.N.Other since I can't get procmail to work. Has anybody thought of writing a MAPI back-ended movemail for use under windows? -Bill P.

2 participants
1 comments

Mail Info 26 years

Andy Piper

>In case anyone is interested I have successfully downloaded my mail from >a >exchange-based pop server using movemail and split and read the mail as >news using the nnfolder backend of gnus. > >All out-of-the-box 21.0b50 under WindowsNT/cygwin32. > >Still haven't decided how I'm going split the mail between gnus and >A.N.Other since I can't get procmail to work. > >andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

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

Colin Rafferty

SL Baur writes: > I'm amenable to adding find-file.el to XEmacs. Has anyone used it > before? I use it all the time. It really improved my editing experience (not quite as much as M-/, but it's really useful). Basically when I'm in a .c file and hit C-c C-o, I get switched into its corresponding .h file (and vice-versa). Also, if the line I am on looks like "#include ...", it switches to that file. I can give it a list of directories where to look for .h files. It is almost indispensible on large multi-library projects. > Which package should it go into? I wouldn't know, since I don't do packages. -- Colin

1 participants
0 comments

Re: Packages-Info ... 26 years

Holger Schauer

>>>>"AP" == Andy Piper schrieb am Wed, 15 Jul 1998 19:43:17 +0100: AP> Here are my comments and additions, additions have >>>>New AP> Stuff>>>, comments are just in straight text. Comments on your comments/additions. >>>>>>>>>>>>New stuff>>>>>>>>>>>> AP> Packages are also listed on the options menu under: options-> customize->emacs->packages AP> If you have efs installed and configured packages can be AP> installed completely from the menubar. We need to mention how this can be accomplished with plain M-x <commands>. >> >> Here is an overview which packages should be dumped [1] with >> XEmacs and thus need to be installed before compiling XEmacs, if >> you like to use them. AP> This is misleading (correct me if I'm wrong someone). What you AP> are dumping are basically hooks for the package which make it AP> possible to use the package with little configuration. There's AP> nothing to stop you installing a package manually loading it and AP> then using it. I'm assuming that xemacs binaries will come AP> pre-dumped with these hooks in which case people want have to AP> care. Allright. Should I then delete the passage alltogether ? What about the Mule-setup ? efs ? Is there somethings necessary to get this going and should there be a passage explaining it ? >> <I think we also need a list of suggestions for people that want >> to do several stuff with XEmacs, like reading/sending mail, >> programming, W3 surfing, etc. You get the idea. Yes, I know of >> etc/PACKAGES but that contains no suggestions.> Anybody wanting to comment on this one ? >> *3. Directories =============== >>>>>>>>>>>>>New Stuff>>>>>>>>>>>>>>> AP> xemacs contains functions that will install packages for you in AP> the correct location, meaning that you the user do not have to AP> worry about where they are. For information puposes: I dislike the last sentence. Is it true that all users should start with a naked XEmacs, downloading all packages from within XEmacs later on ? If so, I must admit that I don't like it to be done this way. >> *4. Installing packages and XEmacs >> ================================== If the following stuff intended as an add-on (i.e. >>>New Stuff) ? AP> The easiest and most correct way to install a package is to do: AP> M-x package-admin-add-binary-package <return> AP> input the location of the package tarball and xemacs will do the AP> rest for you. If you have efs installed and configured you can AP> select package from the customize menu, set their state to on and AP> then do: options-> customize->update packages This corresponds to M-x package-get-update-all, doesn't it ? AP> This will automatically retrieve the packages you have selected AP> from the xemacs ftp site and install them into AP> xemacs. Additionally it will update any packages you already have AP> installed to the newest version. Note that if a package is newly AP> installed you will have to restart XEmacs for the change to take AP> effect. AP> Alternatively you can install packages by hand using tar, AP> although this is not recommended since AP> package-admin-add-binary-package may perform additional steps in AP> the future: [snip] AP> The end goal of the efs-based package distribution is for you to AP> be able to: AP> 1. Download and install and xemacs binary. 2. Download and AP> install the efs package 3. Configure efs. 4. Select packages AP> from the options menu and install them automatically. AP> Currently efs has some dependencies which means that you may have AP> to install more than efs to get going. Also as noted earlier you AP> have to currently restart XEmacs once packages have been AP> installed. These dependencies of efs, and Mule probably as well, are the ones that made me talk about "packages that should be dumped with XEmacs" - I see that my passage is incorrect, but I think these packages that need to be installed first-hand should be mentioned in this document. >> *5. Using Packages from Emacs Lisp >> ================================== AP> I don't know what this means. I think you should delete it. The headline may be a bit misleading. I am concerned with using M-x package* functions and setting some of the variables. For example, I tried to use ; 21.X introduces packages. Koblenz is my nearest mirror. (require 'package-get) (setq package-get-remote (pushnew (list "ftp.fh-koblenz.de" (concat "pub/Mirror/ftp.xemacs.org/" "pub/xemacs/beta/xemacs-21.0/" "packages/binary-packages/")) package-get-remote)) So, things like this should be explained here (or somewhere in the info files at last). BTW: In 21.0 \"Zhong Wei\" XEmacs Lucid and the corresponding package-*.els I had trouble updating my packages. For example, for w3 I had 1.06 installed, but the oldest version that could be found on ftp.xemacs.org was 1.07, so package-get-update-all failed complaining that it couldn't find w3-1.06. I'm currently updating to b50 and package-get-base-pre8. Holger -- --- http://www.coling.uni-freiburg.de/~schauer --- "CL enhances the productivity of programmers. Scheme, to me, is manual *work*. It would make an excellent extension language for vi." -- Lars Magne Ingebrigtsen on xemacs-beta

1 participants
0 comments

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

SL Baur

I'm amenable to adding find-file.el to XEmacs. Has anyone used it before? Which package should it go into?

1 participants
0 comments

Re: Problem with PNG 26 years

Jareth Hein

>>>>> "mt" == Marcus Thiessel <thiessel(a)hpbbse.bbn.hp.com> writes: mt> SL Baur writes: >> The attached PNG (pengbrew_160x160.png) works in display or xv, but >> displays oddly in XEmacs (24 bit color depth). I've attached a >> side-by-side screen shot to show what I see. >> mt> I only get a Unknown/Bad PNG image encoding in both cases mt> (libpng-1.0.1.tar.gz). mt> --Marcus I'm not sure why you're getting Unknown/Bad PNG messages (can you send me some info about your install?), but I *HIGHLY* recommend updating to libpng-1.0.2 soonest. You can find it at http://www.cdrom.com/pub/png or on the XEmacs ftp site. -- 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

2 participants
1 comments

sample: unexec 26 years

Ben Wing

This file contains a RealAudio attachment. RealPlayer v4.0 or later is required. A version of this message in GSM WAV format is located at http://www.666.com/audio/mail/19980729-3-gsm-8k.wav -- Ben Wing - If this message is long and typed, someone else typed it for me - If it has a .rm (RealAudio) attachment, see http://www.real.com/products/player/downloadrealplayer.html?wp=dl0498 - If this doesn't work and there's a GSM WAV attachment, see http://xanim.va.pubnix.com/home.html

1 participants
0 comments

Re: [PATCH] Handle transparency and backgrounds properly in PNG files 26 years

Jareth Hein

Didier Verna <verna(a)inf.enst.fr> writes: > jareth(a)camelot.co.jp (P. E. Jareth Hein) writes: > > > After a forced education into the wonders of specifiers and their care > > and feeding in C, > > I know what you mean :-) > > > Now the background for display is the same as the background of the default > > face. > > It works, thanks. Now I have a quizz for you (please select what you > think is the correct answer): > > > Q: What if I have a background pixmap for the default face ? > > A: [ ] a background what ?! > [ ] huh, dunno. > [ ] I don't give a f*cking damn. > [X] Then, remove it. > [ ] No problem, here's a new patch :-) Seriously, that's a rather large and squirmy can of worms. The current instancing mechanism has no idea of where the image will be placed, so while I can place the pixmap behind the image, I have no way of making sure that the tiling of the background image will match where the image will finally get placed. I'll look into fixing it for 21.1, but I think that creating proper alpha support for overlaying glyphs, etc onto other things is about the only way we can get that. That will allow a lot of cool things, but will take quite a bit of work on modifying redisplay and also won't function on colormapped consoles. Passing in the target x,y coords will also fix the problem, but that means each instance of an image is potentally unique and defeats the cache mechanism. I suppose we could extend the glyph structure to contain a bit on whether or not the instance is unique (if is uses the passed in position info, perhaps)... I'll think about it. -- 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

xemacs-21.0-b50: package-get 26 years

Michael Kifer

M-x package-get yields: Loading package-get... generating package customizations... Malformed property list: (standards-version 1.0 version "1.05" author-version "4.2X" date "1998-07-18" build-date "1998-07-19" 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 "ec8dc3e7f57afe9ac4986fea25e1a789" size 57830 provides (tpu) requires type regular), (regular) I applied the patch to package-get-base.el that Steve posted om 7/20. However, it also tries to patch file wp/tpu/package-info.in, but the directory wp/ doesn't exist. What did I fail to download? (I downloaded only xemacs-21.0-b50.tar.gz, xemacs-21.0-b50-info/elc.tar.gz, mule-base-1.20-pkg.tar.gz) --michael

2 participants
2 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