May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [patch] Another numeric arg to `concat' in `folding.el' 26 years, 1 month

Jari Aalto

* 1999-05-16 Mike McEwan <mike(a)lotusland.demon.co.uk> mail.default | | I've discovered another instance in `folding.el' where a numeric | argument is given to `concat'. Patch appears below. Cc'ing the | `maintainers' documented in the source. | | --- xemacs-packages/lisp/text-modes/ChangeLog~ Thu May 13 18:36:58 1999 | +++ xemacs-packages/lisp/text-modes/ChangeLog Sun May 16 18:18:49 1999 | ＠＠ -1,3 +1,7 ＠＠ | +1999-05-16 Mike McEwan <mike(a)lotusland.demon.co.uk> | + | + * folding.el (fold-set-mode-line): Use `number-to-string' in `concat'. | + | 1999-04-22 John H Palmieri <palmieri(a)member.ams.org> | | * xpm-mode.el (xpm-parse-color): | --- xemacs-packages/lisp/text-modes/folding.el~ Thu May 13 18:36:59 1999 | +++ xemacs-packages/lisp/text-modes/folding.el Sun May 16 18:17:00 1999 | ＠＠ -2127,7 +2127,7 ＠＠ | fold-inside-string "1" fold-inside-mode-name) | (concat | fold-inside-string | - (length fold-stack) | + (number-to-string (length fold-stack)) | fold-inside-mode-name) | )))) Hi, Thank you, but this was already in the latest version 2.58 ftp://ftp.csd.uu.se/pub/users/andersl/beta/folding.el (defun folding-set-mode-line () (if (null folding-stack) (kill-local-variable 'folding-mode-string) (make-local-variable 'folding-mode-string) (setq folding-mode-string (if (eq 'folded (car folding-stack)) (concat folding-inside-string "1" folding-inside-mode-name) (concat folding-inside-string (int-to-string (length folding-stack)) folding-inside-mode-name))))) asd

1 participants
0 comments

Re: [Failure] 21.2b14 26 years, 1 month

Neal D. Becker

Let me clarify that. I loaded the packages from the same package directory - but 21.2b13 has been running for weeks now. In the meantime I updated all the packages (using the standard Options/manage packages tool). I have no way to know if 21.2b13 would work with the present packages since it no longer exists (except in linux's imagination).

1 participants
0 comments

Re: Accessing /:path in XEmacs 26 years, 1 month

Jan Vroonhof

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > > In short, I think this is a UI issue not a user level issue. > I meant "not a lisp level issue". Jan

1 participants
0 comments

Re: Accessing /:path in XEmacs 26 years, 1 month

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > I guess the easy start would be to have a filename handler method > > that matches on "/:", strips it of and calls the built-in method for > > everything. > > Is this a serious proposal or a quick hack suggestion? I'd rather do > it right than introduce ugly hacks. I am fairly serious. I think it pretty much covers all bases and where your running into problems with this method you should have been using another method anyway. >From my point of view the biggest argument against it would be if you are of the opinion that file-name-handler-alist should be nil by default (which it isn't anyway). Another disadvantage would be that it relies on the discipline of the people who add there regexps to f-n-h-a to make sure they do not match /:path In short, I think this is a UI issue not a user level issue. Jan

1 participants
0 comments

Re: Accessing /:path in XEmacs 26 years, 1 month

Jan Vroonhof

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Since it's EFS-specific, let EFS install it. It is not is not EFS specific. You might want to disable jha-compress, the few extension based picture mode, or even a new non-EFS based remote file protocol (think rrsh.el) Jan

1 participants
0 comments

21.2.13 bug: -help displays garbage when run in LANG=ja 26 years, 1 month

T. Kurosaka - Sun Professional Services

I've got gargabed help messages when I run xemacs -help in LANG=ja on Solaris 2.6 SPARC. XEmacs probably needs to convert its internal chracter coding system into the particular coding system for the current locale. -kuro $ xemacs -vanilla -help 2>&1 |more XEmacs 21.2 "Demeter" [Lucid] (sparc-sun-solaris2.6, Mule) of Mon May 17 1999 on rio XEmacs B$OBB!"BX B%DBB!<BB%kBB%-BB%CBB%HBB$NBBI8BB=`BB%3BB%^BB%sBB%IBB%*BB%WBB%7BB%gBB%sBB$rBB$9BB$YBB$FBBG'BB<1BB$7BB$^BB$9BB!#B B$=BB$lBB$KBB2CBB$(BB$FBB!"B B0JBB2<BB$NBB%*BB%WBB%7BB%gBB%sBB$rBBG'BB<1BB$7BB!"BB=PBB8=BB=gBB$KBB=hBBM}BB$7BB$^BB$9B:

2 participants
2 comments

Re: probable bug in avoid.el 26 years, 1 month

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > I spent some time looking at it long, long ago when I was synching > XEmacs to FSF 19.34 and most of it didn't work and the FSF version > had no prayer of working in XEmacs. I quickly lost interest in it > because applications have no business moving the mouse pointer on > their own -- it is *strictly* the domain of the user. Except when the user types M-x mouse-avoidance-mode or whatever, he explicitly agrees to XEmacs moving his pointer. He <gasp> wants that! > Maybe. I think we should delete avoid.el from XEmacs and be done > with it. I think fixing it would be a preferable option.

1 participants
0 comments

Re: probable bug in avoid.el 26 years, 1 month

SL Baur

Kyle Jones <kyle_jones(a)wonderworks.com> writes in xemacs-beta(a)xemacs.org: > This is an avoid.el bug report, ubfortunately it's for 20.3. I don't believe much if anything has changed in avoid.el since 20.3. The only mouse avoidance mode guaranteed to work is 'banish and that is only because InfoDock uses it. I spent some time looking at it long, long ago when I was synching XEmacs to FSF 19.34 and most of it didn't work and the FSF version had no prayer of working in XEmacs. I quickly lost interest in it because applications have no business moving the mouse pointer on their own -- it is *strictly* the domain of the user. > Needs to be verified for the current XEmacs version and maybe > fixed. Posted here for tracking and maybe sparking the interest > of a volunteer. Maybe. I think we should delete avoid.el from XEmacs and be done with it. Most of it doesn't work and it is truly ideologically blasphemous. Let it be bundled with InfoDock only. My 2￥ ...

1 participants
0 comments

Re: cvs access for XEmacs 21.2.* 26 years, 1 month

Tor Arntsen

On May 17, 2:37, SL Baur wrote: >I see. Did I give you enough supplementary information, or do you >need more? I think it's enough, however it's 3:40 in the morning so I better look at it tomorrow. I'll let you hear from me then. Time to go home now.. -Tor

1 participants
0 comments

Re: New mailcrypt status -- GNUPG-0.9.6 is broken 26 years, 1 month

SL Baur

[Thanks William and Jan] William M Perry <wmperry(a)aventail.com> writes in xemacs-beta(a)xemacs.org: > Welcome to digital unix - it sucks, and the linker sucks worse. It sucks, but it doesn't suck that badly. X11/CDE/dxjim on it is wildly unstable[1] compared to XFree86, kinput2 and Linux, but stuff only crashes about once a week, so that's not too bad, I suppose. > Ordering is very important on the link line. Try manually editing the > Makefile and stick -lc at the end of the LDFLAGS or whatever macro they > use. I manually deleted the `-lc' and it linked. Now, it just doesn't pass the self checks. :-( $ grep FAIL typescript FAIL: encrypt.test FAIL: encryptp.test FAIL: armencryptp.test FAIL: genkey1024.test Unfortunately, I _only_ have direct access to a DEC Alpha at this time, so I'm not going to be able to personally test mailcrypt until this program gets ported to OSF. If anyone can point me to leads to getting this bloody program running on BSDI, we'll resume PGP signing tarballs. Being able to test things myself can wait. Footnotes: [1] and ugly as sin compared to Windowmaker or Olvwm, but that is a different matter.

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