September 1999 - XEmacs-Beta - XEmacs Mailing List Archives

[BTS] SIGPIPE under FreeBSD 26 years

Gunnar Evermann

I thought all SIGPIPE related problems were resolved?

1 participants
0 comments

merge describe-variable and customize-variable? 26 years

Gunnar Evermann

from the BTS:

1 participants
0 comments

Re: Off-Topic: Lisp-based WM! 26 years

Greg J. Badros

Erik Arneson <erik(a)starseed.com> writes: > I just started using this pretty neat window manager called 'sawmill'. > It's configurable via an emacs-lisp-like programming language, and I > figured some of you guys might get a kick out of looking at it. > > Here's the URL: > > <URL:http://www.dcs.warwick.ac.uk/~john/sw/sawmill/index.html> FWIW, Scwm, the Scheme Constraints Window Manager, has been around for a couple of years-- it is Guile/Scheme based and more mature than Sawmill (but John's doing great work with Sawmill, and it does have its strengths, for sure). We just made release 0.99.2 of Scwm and its really very powerful including, e.g., a fancy constraint solver (my PhD research), a voice recognition interface, GUI configurability (similar to customize-- we use guile-gtk), and tons more. Greg J. Badros gjb(a)cs.washington.edu Seattle, WA USA http://www.cs.washington.edu/homes/gjb

2 participants
1 comments

Re: More C++ compilability 26 years

Kazuyuki IENAGA

Martin Buchholz <martin(a)xemacs.org> writes: > With these changes, XEmacs will once again compile with a C++ > compiler. > > Andy: please review my changes to glyphs-x.c and gutter.[ch] > Kazz: please review my changes to input-method-xlib.c I've found no problem peculiarly. It's improved in variable's treatment. I've just applied Martin's patch to input-method-xlib.c and saw the behavior (I found it still produces crash in XIM) wasn't changed. > * input-method-xlib.c (XIM_init_frame): > - Xlib functions should use XPointer, not XtPointer. > * input-method-xlib.c (XIM_delete_frame): > - Xlib functions should use XPointer, not XtPointer. > * input-method-xlib.c (IMDestroyCallback): > - Simplify. > - XFRAME (obj) can never be NULL, so don't test for it. > * gutter.h:

1 participants
0 comments

Re: CVS question 26 years

Hrvoje Niksic

Darryl Okahata <darrylo(a)sr.hp.com> writes: > Hrvoje Niksic <hniksic(a)srce.hr> wrote: > > > > I previously grabbed the tag "release-21-2". Now when I do cvs > > > update, am I getting the latest (HEAD)? > > > > When you update, you get the HEAD of the 21.2 branch. So a simple > > `cvs update' will do the right thing. At least that's how it works > > for me. > > No, tags are "sticky", which means that a subsequent "cvs update" > will still use the previously-specified tag. That's exactly what I said, isn't it? Or are you answering nbecker directly?

2 participants
1 comments

RE: CVS question 26 years

Damon Lipparelli

But "release-21-2" is a branch. Hrvoje is right; once you've checked out the "release-21-2" branch, a "cvs update" in the checked out directory will get you the latest bits in the "release-21-2" branch. -lipp -----Original Message----- From: Darryl Okahata [mailto:darrylo＠sr.hp.com] Sent: Wednesday, September 22, 1999 3:09 PM To: XEmacs Beta List Subject: Re: CVS question Hrvoje Niksic <hniksic(a)srce.hr> wrote: > > I previously grabbed the tag "release-21-2". Now when I do cvs > > update, am I getting the latest (HEAD)? > > When you update, you get the HEAD of the 21.2 branch. So a simple > `cvs update' will do the right thing. At least that's how it works > for me. No, tags are "sticky", which means that a subsequent "cvs update" will still use the previously-specified tag. To override this, you have to specify a new/different tag, or you have to use the "-A" option (e.g., "cvs update -A"), to reset your sources to the main trunk. -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

1 participants
0 comments

Re: CVS question 26 years

Hrvoje Niksic

nbecker(a)fred.net writes: > I previously grabbed the tag "release-21-2". Now when I do cvs > update, am I getting the latest (HEAD)? When you update, you get the HEAD of the 21.2 branch. So a simple `cvs update' will do the right thing. At least that's how it works for me.

2 participants
1 comments

Off-Topic: Lisp-based WM! 26 years

Erik Arneson

I just started using this pretty neat window manager called 'sawmill'. It's configurable via an emacs-lisp-like programming language, and I figured some of you guys might get a kick out of looking at it. Here's the URL: <URL:http://www.dcs.warwick.ac.uk/~john/sw/sawmill/index.html> -- # Erik Arneson erik(a)starseed.com Webring Software Engineer # # Yahoo! Inc. PGP ID: 2048/84413E19 (541) 482-3000x114 # # "There's such a fine line between stupid and clever." Spinal Tap #

1 participants
0 comments

Re: xlwtabs.c: Fix C++ compilability. 26 years

Edward A. Falk

> This is the last change for lwlib to be compilable under C++. OK, I've made the changes. The new version is at http://www.best.com/~falconer/Widgets/Tabs.tar.gz I've also added some nice keyboard functionality, but I don't think that will help you under Motif. I'm in the process of making Tabs more compatible with Motif, but I haven't yet figured out how to make a Manager widget receive keyboard input. -ed falk

1 participants
0 comments

Re: merge upstream crypt changes 26 years

Darryl Okahata

In xemacs-patches, James LewisMoss <dres(a)ioa.com> wrote: > I don't know if there is a reason this has been avoided, but after > checking the upstream crypt there are many changes that might be > useful. This patch merges those changes (specifically mac > encoding/decoding and mailcrypt support). The only part that I had a Just FYI, crypt.el is broken with respect to file-coding (which, BTW, also handles mac encoding/decoding). I've got patches that'll make crypt.el work with file-coding (but I haven't done any mac encoding/decoding testing), but I'll wait until the dust settles before submitting them (I think mine and James's will conflict slightly). [ Also, file-coding breaks hexl-mode. Sigh. I've got tentative patches for this, too, and perhaps I'll get around to submitting them, someday. ] -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

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