September 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: PHP3 mode anyone?? 24 years, 8 months

Lars Magne Ingebrigtsen

Nils Bokermann <bokerman(a)uni-bielefeld.de> writes: > Is there any php3 mode for XEmacs?? Or is someone working on it?? I haven't found one, but I'd love to have one. I'm using C-mode for editing PHP code, which kinda sorta works, but there are lots of glitches. -- (domestic pets only, the antidote for overdose, milk.) larsi(a)gnus.org * Lars Magne Ingebrigtsen

2 participants
1 comments

Re: PHP3 mode anyone?? 24 years, 8 months

Robin S. Socha

* Lars Magne Ingebrigtsen <larsi(a)gnus.org> writes: > Nils Bokermann <bokerman(a)uni-bielefeld.de> writes: >> Is there any php3 mode for XEmacs?? Or is someone working on it?? > I haven't found one, but I'd love to have one. I'm using C-mode for > editing PHP code, which kinda sorta works, but there are lots of > glitches. ;;; Copyright (C) 1997 Kazunori Nishi ;;; kazunori(a)kazu.nori.org ;;; php-mode.el --- major mode for editing php (and phtml) code Someone sent me the Englisch URL, but I lost it. Bummer. Anyone here speak Japanese? Ceterum censeo that RXML is much better than PHP. Duh. <http://www.roxen.com/>. Ummm... *mangrep* <clicketyclick> Hah! Luis Calero Munoz <lcalero(a)gsyc.inf.uc3m.es> said: <http://kazu.nori.org/pub/php/english/>. And it *works*. Enjoy. -- Robin S. Socha <http://socha.net/XEmacs/>

2 participants
1 comments

Fixup layout border text and bug fixes 24 years, 8 months

Andy Piper

This allows you to put text in the border of a layout. It also should fix the pdump problems. It also is more helpful about formats widget hierarchy definitions will be accepted in. I will apply this to cvs. andy 1999-09-07 Andy Piper <andy(a)xemacs.org> * gutter-items.el (progress-gauge-glyph): renamed from progress-glyph. (progress-text-glyph): new variable. (progress-layout-glyph): use layouts and text glyphs. (progress-area-buffer): removed. (progress-text-and-extent): new variable. (progress-displayed-p): dynamically create gutter area buffer. (clear-progress): ditto. (raw-append-progress): ditto. (append-progress): use new glyph names. (raw-append-progress): only create the extent when needed. set properties more optimally. (progress): remove args. 1999-09-02 Andy Piper <andy(a)xemacs.org> * redisplay-output.c (redisplay_output_layout): call output routines with clear_clip false. output layout borders with text correctly. * redisplay-msw.c (mswindows_output_blank): call output routines with clear_clip true. (mswindows_output_string): ditto. (mswindows_output_display_block): ditto. * redisplay-x.c (x_output_display_block): call output routines with clear_clip true. * redisplay.h: fix output routines for clear_clip parameter. * redisplay-output.c (redisplay_output_layout): cope with glyphs in the border. * glyphs-widget.c (layout_instantiate): deal with border glyphs. (check_valid_glyph_or_instantiator): renamed from check_valid_glyph_or_image. (check_valid_border): allow glyphs or their instantiators. (check_valid_glyph_or_instantiator_list): renamed from check_valid_glyph_or_image_list, (glyph_instantiator_to_glyph): new function. make sure a glyph is a glyph and not an instantiator. (substitute_keyword_value): new function. replace a keyword value with a new one. -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

PHP3 mode anyone?? 24 years, 8 months

Nils Bokermann

Hi! Is there any php3 mode for XEmacs?? Or is someone working on it?? If not, I will have to begin by myself... Bye, Nils -- Nils Bokermann Phone: +49 521 88074398

1 participants
0 comments

Re: Building 21.1 or 21.2 with latest gcc snapshots 24 years, 8 months

Jan Vroonhof

Vin Shelton <acs(a)xemacs.org> writes: > I recompiled ralloc.c with -fno-strict-aliasing, and voila! I can > build and run an XEmacs. Perhaps someone who understands the aliasing > issues better than I do can track this down, he or she cares to. I am not sure, but I think this is suspect: #define SET_FUN_PTR(fun_ptr, fun_val) \ (*((void **) (&fun_ptr)) = ((void *) (fun_val))) void init_ralloc (void) { if (r_alloc_initialized) return; r_alloc_initialized = 1; SET_FUN_PTR (real_morecore, __morecore); SET_FUN_PTR (__morecore, r_alloc_sbrk); FSF Emacs simply has real_morecore == __morecore I would look at the output of make ralloc.s in both cases. Jan P.S. IMHO this whole -fstrict-aliasing issue (for C) is a unfortunate mistake by the GCC people. In particular the "portable code won't break because other compilers have been doing this for ages" argument seems invalid. Of the 4 large C programs I use at home (linux kernel, glibc, XEmacs, X) 3 have (had) aliasing problems known to me. I am just waiting for the aliasing bugs in X to show up.

1 participants
0 comments

Re: Outstanding 21.1.x issues 24 years, 8 months

Michael Sperber

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> SL Baur <steve(a)xemacs.org> writes: >> I don't like this at all. If it isn't dumped with the binary, it >> doesn't belong in the XEmacs core. Moreover, at least info.el is in the core, but not dumped. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Outstanding 21.1.x issues 24 years, 8 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > I don't like this at all. If it isn't dumped with the binary, it > doesn't belong in the XEmacs core. I think this is the wrong criterion, as it needlessly forces things to be dumped that are used very infrequently. Or do suggest abandoning the other properties of the core, i.e. a minimal functional editor that can bootstrap the packages? I for my part would love to see a very light weight http client in the core so that XEmacs can fetch the packages itself without relying on external programs thus eliminating loads of problems (including most of the W32 issues). Jan

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] More Mule Screwage in packages: jka-compr and lookup 24 years, 8 months

Jan Vroonhof

Vin Shelton <acs(a)xemacs.org> writes: > Why hasn't this been applied to jka-compr? Should I apply it? I > can't seem to run jka-compr without it. I haven't applied them yet as I don't have a package tree checked-out home. I didn't have the space before and haven't got around to doing it now. (It doesn't help that for me CVS over ssh seems to be about an order of magnitude slower). I would love to see a jka-compr package with this patch (and a calendar package with the string-width vs lenght patch). Jan

1 participants
0 comments

[gnu.emacs.sources] Prolog mode 24 years, 8 months

Holger Schauer

Hi ! Has somebody already tested this ? Otherwise I'll do ... And then there's a new ilisp 5.9 available from ilisp.cons.org, just announced by Marco Antoniotti on gnu.emacs.sources as well. Holger

1 participants
0 comments

Re: Outstanding 21.1.x issues 24 years, 8 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: > "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: Hrvoje> We can remove x?m-button.el from xemacs-base. >> >> Not immediately. [... good explanation snipped ...] > Then our "shadow" checking should know about the "allowed" shadows, > although I don't like that course of action. I don't like this at all. If it isn't dumped with the binary, it doesn't belong in the XEmacs core.

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