September 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Jan Vroonhof

nbecker(a)fred.net writes: > I've been using this patch for unix98 ptys. Would you guys like to > include this? Do you think it needs to be modified before it will be > accepted? I think the test probably should autoconf based, but currently all the others don't seem to do that either. Maybe Martin can give his view. > else > glibc should emulate with old pty behaviour > // or so I'm told Yes. However, wasn't there a security problem with that emulation? Has that bin fixed in newer glibc's? > *** process.h 1998/04/11 05:37:05 1.8 > --- process.h 1999/09/20 13:29:18 > *************** > *** 134,137 **** > --- 134,149 ---- > > #endif /* emacs */ > > + #if defined (__GLIBC__) && (__GLIBC__ >= 2) && (__GLIBC_MINOR__ >= 1) > + # define HAVE_GETPT > + #endif If not autoconf bases then this should be in the s&m files, not in a general include file. Jan

2 participants
1 comments

Re: frame-title-format 26 years

Didier Verna

Vin Shelton <acs(a)xemacs.org> wrote: > I'm trying to figure out how to give my different frames different > names. In particular, I want to create a gnus-only frame and give it > a title of "gnus". I want to keep my other frame titles as they are, > which is roughly: "XEmacs＠zion [21.1] %b". First I was surprised that > the frame title doesn't seem to be a frame property. Then I was > surprised that I couldn't make frame-title-format a function. I seem > to be thwarted; I could make frame-title-format buffer-local, but > that's not what I want, either. Suggestions? Perhaps you could set the frame name, which is a frame property, and use it in frame-title-format. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: Installation HOWTO 26 years

Dan Harkless

Vin Shelton <acs(a)xemacs.org> writes: > John, > Thanks for doing this. It will be a big help. Other than > suggesting 'zcat < xemacs-21.1.*.tar.gz' | tar xf -', Since you can't depend on someone's path not pointing to a vendor zcat, which won't understand .gz files, it's better to suggest "gzip -c" instead of "zcat". Also, the "<" is superfluous. > I can't offhand > see much else that needs improving. I think you drew the proper line > on the $prefix issue - this set of instructions will get the job > done. If people want to relocate the packages, they'll have to do > some research. ----------------------------------------------------------------------- Dan Harkless | To prevent SPAM contamination, please dan-xemacs(a)dilvish.speed.net | do not post this private email address SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.

2 participants
1 comments

Re: Huge auto-fill-mode bug intro'd in 20.0 still not fixed in 21.2.19 26 years

Hrvoje Niksic

"Dan Harkless" <dan-xemacs(a)dilvish.speed.net> writes: > People working in Japanese would just need to be sure to set that > variable (if there weren't some automatic way of turning it on while > working in Japanese buffers). At least part of the problem is that there is (or should be) no such thing as a "Japanese buffer". Any buffer can contain any character. XEmacs does not yet know anything about specific languages, either.

3 participants
4 comments

Re: Installation HOWTO 26 years

john s jacobs anderson

>>>>> "JV" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: JV> john s jacobs anderson <jacobs(a)azstarnet.com> writes: >> also, *BSD/Solaris/other non-RedHat platforms: where do these >> instructions break on your setup? JV> [Personally the most difficult part here would be to make sure JV> you have all the additional libraries and making sure XEmacs JV> will find them] ugh. that falls into the 'information i thankfully do not have to know' category. does someone at least have a list? does that list differ from <URL:http://www.xemacs.org/Download/optLibs.html> in any substantial way? i guess the instructions should point to that page in any case. >> 1. [Get ] xemacs-21.1.*.tar.gz, xemacs-21.1.*-elc.tar.gz, >> xemacs-21.1.*-info.tar.gz JV> Why don't just put xemacs-21.1.*.tar.gz? The rest will build JV> automatically. because the last time i did this, they didn't. i'll try again tonight and see if they get generated. >> 2.Expand the above files into the directory used for compiling, >> e.g. tar zxvf xemacs-*.tar.gz -C /usr/src/. JV> This assumes GNU tar. opps. what's the piped version again? >> 10.From the menubar, choose Options -> Manage Packages -> >> Update Installed Packages. This will download the most recent >> package index (PGP errors may occur and can be ignored) and >> list the packages available for install. Instructions and key >> bindings for this buffer are at the bottom; use the scroll bar >> to view them. JV> If you have a scrollbar, you most likely also have a (popup) JV> menu where all the bindings are listed. Additionally C-h m JV> works just like in any other mode. 6 of one, half dozen of other on the popup vs. scroll. C-h m is a bad idea, as the installer might not have (or want) the know-how to get rid of the split window. i was trying to follow KISS principle as much as possible. >> If in doubt about a particular package, it is generally safe to >> just install it. JV> I think this is wrong (at least using the automated tools), JV> you should never install a mule package. Package-*.el do know JV> how to separate out Mule related packages but unfortunately JV> this only works on a Mule XEmacs (thus if you run both you JV> should use the Mule version to install packages). thanks. which are the mule-specific packages? (and why don't they have 'mule-only' in their description lines?) JV> Generally would like some lines like JV> X. At this point it is good to read README.packages JV> I know people won't read docs but I sure don't want the JV> website to advocate that. I would say it needs at least a link JV> to the true release notes. also a good idea. of course, if people could be bothered to read the provided docs, (a) this page wouldn't be needed and (b) the list/newsgroup posts matching 'xpm.*button' would be much less frequent. thanks for the comments! john. -- ------------------------------------------------------------------------ John S Jacobs Anderson Apprentice Geek jacobs(a)azstarnet.com Journeyman Molecular Biologist <URL:http://www.azstarnet.com/~jacobs/> <- GeneHack:bioinfo*linux*opinion

2 participants
1 comments

frame-title-format 26 years

Vin Shelton

I'm trying to figure out how to give my different frames different names. In particular, I want to create a gnus-only frame and give it a title of "gnus". I want to keep my other frame titles as they are, which is roughly: "XEmacs＠zion [21.1] %b". First I was surprised that the frame title doesn't seem to be a frame property. Then I was surprised that I couldn't make frame-title-format a function. I seem to be thwarted; I could make frame-title-format buffer-local, but that's not what I want, either. Suggestions? TIA, vin

1 participants
0 comments

21.1.7 - needed patch for "mmencode.c" 26 years

Damon Lipparelli

I had to pull the attached patch back from the 21.2 branch to get "mmencode.cc" compiling under native Windows. Otherwise, looks great. -lipp <<mmencode.c.patch1>>

1 participants
0 comments

bzip support in crypt 26 years

Kyle Jones

James LewisMoss writes: > I checked the mailing list and other than a discussion on whether > distributing xemacs as bz2 I didn't find this. Let me know if I > missed anything. Also, for things like this is it better to find an > upstream maintainer for what is in the xemacs cvs xemacs-packages > module or to just submit here? for the moment I'll just submit this > and let someone tell me I'm wrong. crypt++ is maintained by Karl Berry <kb(a)cs.umb.edu>. Off the top of my head I can't think of any reason our version would be different, except perhaps for MULE backs. I'm using that version of crypt ather than the packaged one and it works fine for me.

1 participants
0 comments

Re: Installation HOWTO 26 years

Adrian Aichner

>>>>> "Dan" == Dan Harkless <dan-xemacs(a)dilvish.speed.net> writes: Dan> Vin Shelton <acs(a)xemacs.org> writes: >> John, >> Thanks for doing this. It will be a big help. Other than >> suggesting 'zcat < xemacs-21.1.*.tar.gz' | tar xf -', Dan> Since you can't depend on someone's path not pointing to a Dan> vendor zcat, which won't understand .gz files, it's better to Dan> suggest "gzip -c" instead of "zcat". Also, the "<" is Hi Dan, "gunzip -c" will work, for gzip you'll have to add the decompress switch, so make this "gzip -dc". Adrian Dan> superfluous.

1 participants
0 comments

Re: unix98 pty patch (again) 26 years

Jan Vroonhof

nbecker(a)fred.net writes: > I thought that since this is a glibc feature, not a specific system > feature, that it shouldn't be based on s&m files. glibc is definitely part of the OS so could go into the s&m files, although autoconf would be better. Jan

1 participants
0 comments

2025

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