October 1998 - XEmacs-Beta - XEmacs Mailing List Archives

problems with flyspell mode 26 years, 1 month

Greg Klanderman

I'm not sure what flyspell version this is, as there is unfortunately nothing to indicate the version in the header of flyspell.el. However, I have 3 problems with the one included in the latest XEmacs package. 1. The line (defvar flyspell-mode-map (make-sparse-keymap)) needs an autoload cookie above it. 2. The lines adding the minor mode: (add-minor-mode 'flyspell-mode flyspell-mode-line-string flyspell-mode-map nil flyspell-mode) look like they should be (add-minor-mode 'flyspell-mode flyspell-mode-line-string flyspell-mode-map nil #'flyspell-mode) Note change in last line. 3. I signal the following error the first time it is run (M-x vm-mail): Signaling: (wrong-type-argument number-char-or-marker-p nil) flyspell-check-changed-word-p(59 59) flyspell-post-command-hook() as flyspell-pre-point is nil. I can submit a patch for the first 2, but it may be best to get an update through the author. greg

2 participants
1 comments

Re: [somewhat offtopic] quesion on shell output redirection 26 years, 1 month

Soren Dayton

Olivier Galibert <galibert(a)pobox.com> writes: > On Mon, Oct 19, 1998 at 06:54:53PM -0400, Greg Klanderman wrote: > > Anyway the question is, if I redirect stdout and stderr as follows > > (in /bin/sh): > > > > % some_command > output.txt 2>&1 > > > > am I guaranteed that output to stdout and stderr by the program is > > synchronized? Do the two output streams share the same buffer? > > No. Stdio internal buffers aren't synchronized no matter what you > externally do. and, in any case, I believe that stderr is unbuffered in most implementations and stdout is buffered. So its particularly nasty. Soren

1 participants
0 comments

Re: Link error in 21.2-b2/NT 26 years, 1 month

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > CLASH_DETECTION is only useful in a multiuser environment, or any > situation where multiple XEmacsen can be editing the same file. Moreover clashdetection works by making symlinks which I believe are utterly unavailible under NT. Does anybody know how FSF NT does this? Jan

3 participants
2 comments

Can not add another info directory to infopath 26 years, 1 month

Robert Clifford

I tried to add /var/info to xemacs-21.2-b3 to read its dir, but I could not find a way of adding it, other than to modify setup-paths.el There is a way to add the directory but that way does not read the dir file, so the files don't appear when info is evoked. -- Robert Clifford, ESCC New York City rcliff(a)panix.com "I think I've got the hang of it now .... :w :q :wq :wq! ^d X exit X Q :quitbye CtrlAltDel ~~q :~q logout save/quit :!QUIT ^[zz ^[ZZ ZZZZ ^H ^＠ ^L ^[c ^# ^E ^X ^I ^T ? help helpquit ^D^d ^C ^c help exit ?Quit ?q" (Ed Wright)

1 participants
0 comments

Debian bug tracking system contains patch for GPM C-z hang 26 years, 1 month

Jan Vroonhof

http://www.debian.org/Bugs/db/20/20398.html Unfortunately a patch for libgpm is needed too. However it would be nice if our linux binary packages could have a version with this patch linked in staticly. Jan

1 participants
0 comments

Re: Link error in 21.2-b2/NT 26 years, 1 month

Jan Vroonhof

Glynn Clements <glynn(a)sensei.co.uk> writes: > > Moreover clashdetection works by making symlinks which I believe are > > utterly unavailible under NT. Does anybody know how FSF NT does this? > > The FSF has its own version of NT? :-) .. I mean FSF Emacs on NT of course. Jan

1 participants
0 comments

My incoming email will be terminated tomorrow 26 years, 1 month

SL Baur

Incoming email to me via `steve(a)calag.com' or `steve(a)altair.xemacs.org' will be terminated sometime[1] tomorrow (Monday) US time. The `steve(a)calag.com' address will not be resumed. `steve(a)xemacs.org' is the only address you should use. Please, please do not carbon copy me on messages to any XEmacs list other than the MS windows list. I will be on the other end of a slow line and it won't be appreciated even more than it isn't appreciated now. Thanks. Footnotes: [1] I have oral surgery midday Monday and have to close an office at the same time, sigh.

1 participants
0 comments

Re: Problems using efs under windows98 26 years, 1 month

Andy Piper

Guido.VanHoecke(a)advalvas.be writes: You need to submit windows specific queries and feedback to xemacs-nt(a)xemacs.org > [1 message body text <text/plain; us-ascii (7bit)>] > There are several problems when using efs in "Poitou" (XEmacs > 21.0-b57) (running windows98) > > When starting dired (C-x d /ftp:) to view my home account on unix > (accessible thru host named 'ftp'), I get a message saying: > '*ftp MyName＠ftp* seems not a pty. Kill? (y or n)' > > If I reply 'n', the process continues and I get a listing of my home > directory on unix, which is what I aimed for. > > When I want to kill the dired buffer, and the ftp buffer, Xemacs > complains: 'Cannot send signal to proces'. Xemacs consistantly refuses > to kill the ftp buffer. I believe these are known problems. Some should now be fixed. The frame size wierdness will get fixed in 21.1. andy

1 participants
0 comments

Re: Windows NT help 26 years, 1 month

Andy Piper

Hrvoje Niksic <hniksic(a)srce.hr> writes: > greg(a)alphatech.com (Greg Klanderman) writes: > > > I'd like to submit a patch to fix the breakage in 21.2 on NT due to my > > user-name completion stuff. the *pwent() functions do not exist on > > NT. Andy - do they exist on CYGWIN? Which is the right pre-processor > > test to use? Yes they do. > > > > #ifndef WINDOWSNT, > > #ifndef HAVE_MS_WINDOWS, > > HAVE_MS_WINDOWS should be used is for distinguishing MS Windows as a > window system, sort of like HAVE_X_WINDOWS is used under Unix. > WINDOWSNT will be defined under the native build, but not under > Cygwin. __CYGWIN32__ should be defined under Cygwin only. So use WINDOWSNT. andy

1 participants
0 comments

Re: cvs mirroring 26 years, 1 month

Jan Vroonhof

Darryl Okahata <darrylo(a)sr.hp.com> writes: > I'll take a stab at doing a Linux port of CVSup, as it's pretty nice. > However, I know nothing about Linux, except that there're lots of > different variants, and so I'd like some recommendations on which > distribution to get. I don't want to waste time with installation/setup As everybody seems to pitching in for Redhat let me just say that I recommend Debian. If only for the reason that Debian comes with XEmacs whereas Redhat doesn't[1]. My guess that would be that given the developmental and the prefered focus on quality above user friendliness on install you would be more at home coming from FreeBSD (note that debian install is not really lesss "user-friendly", mostly it just looks less slick). But anyway I agree with the others that really doesn't matter as long as it is libc6 based. Jan [1] There is a user contributed version/

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 October 1998