September 2000 - XEmacs-Beta - XEmacs Mailing List Archives

ASCII art in Texinfo? 23 years, 7 months

Stephen J. Turnbull

I've been accumulating notes on the Lucid widget library, and thought I'd put some of them into Texinfo format. There being complex and interlocking graphs all over the place, I think some figures of widget hierarchies and the like would useful. Is there a standard for doing this in Texinfo? ASCII art in ＠example environments would be the easiest way to go, I guess? In XEmacs, we ought to be able to embed PNGs in Info docs, dammit! -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

Re: working on getting XEmacs/GTK to 21.2... 23 years, 7 months

William M. Perry

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "-BP" == William M Perry <wmperry(a)aventail.com> writes: > > -BP> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > > >> Also, until GTK is used for Custom, I think it's going to look > >> very very half-assed. > > -BP> Why is that not the case for X and Motif then? Or Windows? > > Who said it wasn't? :^) But we're used to it in those cases. Also, we > _are_ using X at least in Custom; Custom buffers under X look better than > they do on a TTY, just because of the cheesy graphic widgets. Are we actually using native widgets in custom now? I haven't had a chance to play with the latest stuff working on the GTK stuff. I'd actually like to see a true GUI wrapped around custom. Either using the native widget stuff or the FFI GTK bindings. But that's a whole nother story. :) -bp

1 participants
0 comments

Re: One more time, why can't xemacs-packages be a sibling of xemacs? 23 years, 7 months

Michael Sperber

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: Stephen> I think that's bad policy (people building from source should Stephen> be able to handle hierarchical directory structures and the Stephen> difference between installed applications and Stephen> running-in-place), That's what I thought, too, especially about Ben. Stephen> but I'm open to counterargument. I wish Ben would provide a convincing one, but he's basically been silent on this since I put in the change. After all, he got what he wanted ... -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

PSGML's syntax table for HTML inappropriate? 23 years, 7 months

Stephen J. Turnbull

I'm trying to migrate my HTML to XHTML. Unfortunately, PSGML barfs on the required "xml:lang" attribute because of the colon. The HTML 4.0 spec seems to indicate that (for HTML) the colon, among other characters, should be considered a name constituent. Changing the syntax type of colon to "symbol constituent" in the PSGML parser's syntax table leads to reasonable behavior for my X?HTML documents, but I do not understand ISO 8879 or PSGML well enough to say whether this is really a correct solution. Nor can I say how to implement it given that (AFAIK) the "correct" syntax table would vary according to the SGML instance. This arose in XEmacs PSGML package 1.18, psgml-version 1.0.1. Thanks for your attention to this issue. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

Re: One more time, why can't xemacs-packages be a sibling of xemacs? 23 years, 7 months

Michael Sperber

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>> "dv" == Didier Verna <didier(a)xemacs.org> writes: dv> Obviously, XEmacs took my package source directory for what it dv> is not. After renaming it to XEmacs-Packages (note the dv> uppercase) and reinstalling in order to update the symlinks, dv> everything went fine again. >>>>> "ms" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: ms> Ben yelled at me sufficiently to implement this. It's an ms> intentional feature, and it only happens with an in-place ms> XEmacs. Stephen> This, er, doesn't seem to be documented anywhere. info xemacs Stephen> 'startup paths' says "If you run in-place, these [hierarchies] are Stephen> direct subdirectories of the build directory." Correct, I haven't gotten around to that, mainly because I expected there'd be dust in its wake that would need settling. The proof is here. Stephen> What is it that Ben wanted? Actually, I am not sure anymore. Stephen> Is this just so that Windows users can put their installed package Stephen> hierarchy in c:\xemacs-packages and their sources in Stephen> c:\xemacs or something like that? That's how I read him originally. dv> To me, running in place would mean the ability to find the dv> packages in my compiled cvs source tree withtout having to dv> install them (whether by symlinks or not). But that's not that dv> hey ? You're correct. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

buffer tabs widget & dialogs 23 years, 7 months

Stephen J. Turnbull

After spell checking a buffer and inserting a word in the private dictionary, the "save dictionary" dialog pops up. The buffer tabs change color (to indicate they are inactive, I assume). However, they do not return to the original color when the dialog pops down. Furthermore, when a tab is activated, only the two tabs involved (the old current buffer and the new one) return to the indication of active state. Others change as they are activated in turn (or as a new mode changes the whole set of tabs at once). XEmacs 21.2.35, CVS updated to 28 August 04:00 UTC. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

2 participants
1 comments

Re: Unify PTY handling 23 years, 7 months

Andreas Jaeger

>>>>> Martin Buchholz writes: > I'm going to do some work on pty allocation, with the hope of doing > things more sensibly and removing warnings. > getpt() will be used where available. > Unix98 functions will be used where available. > Ideas (but little code) will be taken from Don Libes' expect. > If my new allocation function fails, I plan to fallback to the old > crufty one. Glad to hear! If you need testers on Linux, just shout. Thanks, Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de http://www.suse.de/~aj

1 participants
0 comments

Unify PTY handling 23 years, 7 months

Andreas Jaeger

Compiling on Linux/i686 I get these warnings: In file included from /usr/src/cvs/release-21-2/src/callproc.c:31: /usr/src/cvs/release-21-2/src/process.h:143: warning: `PTY_ITERATION' redefined s/linux.h:216: warning: this is the location of the previous definition /usr/src/cvs/release-21-2/src/process.h:146: warning: `PTY_OPEN' redefined s/linux.h:228: warning: this is the location of the previous definition /usr/src/cvs/release-21-2/src/process.h:148: warning: `PTY_TTY_NAME_SPRINTF' redefined s/linux.h:253: warning: this is the location of the previous definition process.h has: #ifdef HAVE_GETPT #define PTY_ITERATION #define PTY_OPEN \ if ((fd = getpt()) < 0 || grantpt (fd) < 0 || unlockpt (fd) < 0) \ return -1; #define PTY_NAME_SPRINTF #define PTY_TTY_NAME_SPRINTF strcpy (pty_name, ptsname (fd)); #endif Compare this with linux.h: #define PTY_ITERATION for (i = 0; i < 1; i++) /* no iteration at all */ #define PTY_OPEN \ do { \ fd = getpt(); \ if (fcntl (fd, F_SETFL, O_NDELAY) == -1) \ fatal ("could not set master PTY to non-block mode"); \ } while (0) #define PTY_TTY_NAME_SPRINTF \ { \ char *ptsname(), *ptyname; \ \ EMACS_BLOCK_SIGNAL (SIGCHLD); \ if (grantpt(fd) == -1) \ fatal("could not grant slave pty"); \ if (unlockpt(fd) == -1) \ fatal("could not unlock slave pty"); \ if (!(ptyname = ptsname(fd))) \ fatal ("could not enable slave pty"); \ strncpy(pty_name, ptyname, sizeof(pty_name)); \ pty_name[sizeof(pty_name) - 1] = 0; \ EMACS_UNBLOCK_SIGNAL (SIGCHLD); \ } IMO we should unify this. Could some folks please try the appended patch? It works for me on Linux 2.4.0.../glibc 2.1.3/i686 but I'd like to give it some more testing before it gets applied. Andreas 2000-09-20 Andreas Jaeger <aj(a)suse.de> * src/s/linux.h: Move PTY handling to process.h * src/process.h: Unify PTY handling with version from s/linux.h. Index: src/process.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/process.h,v retrieving revision 1.8.2.10 diff -u -r1.8.2.10 process.h --- src/process.h 2000/06/12 04:18:21 1.8.2.10 +++ src/process.h 2000/09/20 08:00:01 ＠＠ -139,13 +139,43 ＠＠ #endif /* emacs */ -#ifdef HAVE_GETPT +#if defined(HAVE_GRANTPT) && defined(HAVE_UNLOCKPT) && defined(HAVE_PTSNAME) +/* No iteration at all: */ #define PTY_ITERATION -#define PTY_OPEN \ - if ((fd = getpt()) < 0 || grantpt (fd) < 0 || unlockpt (fd) < 0) \ - return -1; + +#ifdef HAVE_GETPT +/* Use getpt() if it's available. */ + +#define PTY_OPEN \ + do { \ + fd = getpt(); \ + if (fcntl (fd, F_SETFL, O_NDELAY) == -1) \ + fatal ("could not set master PTY to non-block mode"); \ + } while (0) + #define PTY_NAME_SPRINTF -#define PTY_TTY_NAME_SPRINTF strcpy (pty_name, ptsname (fd)); + +#else +/* the master PTY device */ +#define PTY_NAME_SPRINTF strcpy (pty_name, "/dev/ptmx"); +#endif + +#define PTY_TTY_NAME_SPRINTF \ + { \ + char *ptsname(), *ptyname; \ + \ + EMACS_BLOCK_SIGNAL (SIGCHLD); \ + if (grantpt(fd) == -1) \ + fatal("could not grant slave pty"); \ + if (unlockpt(fd) == -1) \ + fatal("could not unlock slave pty"); \ + if (!(ptyname = ptsname(fd))) \ + fatal ("could not enable slave pty"); \ + strncpy(pty_name, ptyname, sizeof(pty_name)); \ + pty_name[sizeof(pty_name) - 1] = 0; \ + EMACS_UNBLOCK_SIGNAL (SIGCHLD); \ + } + #endif #endif /* INCLUDED_process_h_ */ Index: src/s/linux.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/s/linux.h,v retrieving revision 1.11.2.4 diff -u -r1.11.2.4 linux.h --- src/s/linux.h 2000/09/14 06:31:09 1.11.2.4 +++ src/s/linux.h 2000/09/20 08:00:01 ＠＠ -208,48 +208,3 ＠＠ /* XEmacs: removed setpgrp() definition because we use setpgid() when it's available, and autodetect it. */ -#if defined(HAVE_GRANTPT) && defined(HAVE_UNLOCKPT) && defined(HAVE_PTSNAME) -/* UNIX98 PTYs are available. - Added by Florian Weimer <Florian.Weimer(a)RUS.Uni-Stuttgart.DE>, - RUS-CERT, University of Stuttgart. Based on Emacs code for DGUX. */ - -#define PTY_ITERATION for (i = 0; i < 1; i++) -/* no iteration at all */ - -/* Use getpt() if it's available, because it provides Unix98 PTY - emulation for kernels which doesn't support it natively. */ - -#ifdef HAVE_GETPT -#define PTY_OPEN \ - do { \ - fd = getpt(); \ - if (fcntl (fd, F_SETFL, O_NDELAY) == -1) \ - fatal ("could not set master PTY to non-block mode"); \ - } while (0) - -#else -/* the master PTY device */ -#define PTY_NAME_SPRINTF strcpy (pty_name, "/dev/ptmx"); -#endif - -/* This sets the name of the slave side of the PTY. grantpt(3) and - unlockpt(3) may fork a subprocess, so keep sigchld_handler() from - intercepting that death. */ - -#define PTY_TTY_NAME_SPRINTF \ - { \ - char *ptsname(), *ptyname; \ - \ - EMACS_BLOCK_SIGNAL (SIGCHLD); \ - if (grantpt(fd) == -1) \ - fatal("could not grant slave pty"); \ - if (unlockpt(fd) == -1) \ - fatal("could not unlock slave pty"); \ - if (!(ptyname = ptsname(fd))) \ - fatal ("could not enable slave pty"); \ - strncpy(pty_name, ptyname, sizeof(pty_name)); \ - pty_name[sizeof(pty_name) - 1] = 0; \ - EMACS_UNBLOCK_SIGNAL (SIGCHLD); \ - } - -#endif -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de http://www.suse.de/~aj

3 participants
3 comments

21.1 crash in eval.c: 1877 (abort) 23 years, 7 months

Stephen J. Turnbull

This has happened twice now, in the following fashion: after several days of a session, mostly using VM, I click on the get mail button for some folder. The .crashbox gets filled, and then XEmacs crashes. No lisp backtrace, no C backtrace (that may be my fault; the first time I didn't have core dumps enabled, the second I may have run out of space for the core file). It aborts in eval.c at line 1877, which is a check for in redisplay or in GC. I don't notice a GC happening, but it goes down really fast so I may have missed it. Probably last CVS update was Aug 23. uname -a: Linux turnbull 2.2.14 #1 Mon Apr 3 17:04:34 JST 2000 i586 unknown /coda/Projects/XEmacs/21.1-HEAD/configure '--srcdir' '/coda/Projects/XEmacs/21.1-HEAD' '--with-mule' '--with-xim=xlib' '--with-xfs' '--prefix=/playpen/gnu' '--exec-prefix=/playpen/gnu/plat' XEmacs 21.1.12 "Channel Islands" configured for `i586-pc-linux'. Where should the build process find the source code? /coda/Projects/XEmacs/21.1-HEAD What installation prefix should install use? /playpen/gnu What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

Re: More on find-file dialogue failure 23 years, 7 months

Michael Sperber

>>>>> "dv" == Didier Verna <didier(a)xemacs.org> writes: dv> Obviously, XEmacs took my package source directory for what it is dv> not. After renaming it to XEmacs-Packages (note the uppercase) and dv> reinstalling in order to update the symlinks, everything went fine again. Ben yelled at me sufficiently to implement this. It's an intentional feature, and it only happens with an in-place XEmacs. dv> To me, running in place would mean the ability to find the dv> packages in dv> my compiled cvs source tree withtout having to install them (whether by dv> symlinks or not). But that's not that hey ? Yes, that's what it is. As opposed to a regular package hierarchy available to an in-place core. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

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