November 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: BUG REPORT: etags searching in lisp mode 25 years, 4 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > Exact searching for symbols in lisp mode seems to be messed up. > > To reproduce, make a TAGS table for XEmacs using `make TAGS', > do xemacs -q > eval > (setq tags-always-exact t) > visit the file .../lisp/etags.el > and do M-x find-tag RET find-tag RET > ==> No entries matching find-tag I am unable to repeat this bug. For me, `M-. find-tag RET' correctly finds `find-tag'. > Another bug: If I try > M-x find-tag RET list* RET > it will find the tag for `list', not `list*'. That's because the expression you type in is actually a regexp (tags-always-exact is something else, and it's almost totally obsolete now.) `M-. list\* RET' will correctly find one definition of `list*' (and a subsequent `M-,' will find the other one.) > XEmacs should first look for an exact string match for the symbol > surrounded by the ^? and ^A delimiters before trying a pattern > match. I think I prefer it to be consistent. Perhaps there should be a switch to turn off the regexp behaviour. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- You know it's going to be a bad day when your twin brother forgot your birthday.

3 participants
2 comments

BUG REPORT: 21.2-b4 movemail changes broken on Solaris 25 years, 4 months

Martin Buchholz

In 21.2-b4, movemail.c uses the function re_match() (and its friends) if XEmacs is configured --with-pop. The code expects to find a prototype for this function in regex.h. But on Solaris, there is no re_match function, although the header regex.h exists. And no, it's not in regexp.h, regexpr.h, or re_comp.h either... I don't understand this code, but I suggest using only the standardized regex functions. If you insist on using re_match, then you must add a check to configure.in and disable with-pop if re_match and friends are not found. The XOPEN blurb on regex.h follows: - http://www.opengroup.org/pubs/catalog/web.htm NAME regex.h - regular-expression-matching types SYNOPSIS #include <regex.h> DESCRIPTION The <regex.h> header defines the structures and symbolic constants used by the regcomp(), regexec(), regerror() and regfree() functions. The structure type regex_t contains at least the following member: size_t re_nsub number of parenthesised subexpressions The type regoff_t is defined as a signed arithmetic type that can hold the largest value that can be stored in either a type off_t or type ssize_t. The structure type regmatch_t contains at least the following members: regoff_t rm_so byte offset from start of string to start of substring regoff_t rm_eo byte offset from start of string of the first character after the end of substring Values for the cflags parameter to the regcomp() function: REG_EXTENDED Use Extended Regular Expressions. REG_ICASE Ignore case in match. REG_NOSUB Report only success or fail in regexec(). REG_NEWLINE Change the handling of newline. Values for the eflags parameter to the regexec() function: REG_NOTBOL The circumflex character (^), when taken as a special character, will not match the beginning of string. REG_NOTEOL The dollar sign ($), when taken as a special character, will not match the end of string. The following constants are defined as error return values: REG_NOMATCH regexec() failed to match. REG_BADPAT Invalid regular expression. REG_ECOLLATE Invalid collating element referenced. REG_ECTYPE Invalid character class type referenced. REG_EESCAPE Trailing \ in pattern. REG_ESUBREG Number in \digit invalid or in error. REG_EBRACK [ ] imbalance. REG_EPAREN  or ( ) imbalance. REG_EBRACE \{ \} imbalance. REG_BADBR Content of \{ \} invalid: not a number, number too large, more than two numbers, first larger than second. REG_ERANGE Invalid endpoint in range expression. REG_ESPACE Out of memory. REG_BADRPT ?, * or + not preceded by valid regular expression. REG_ENOSYS The implementation does not support the function. The following are declared as functions and may also be declared as macros. Function prototypes must be provided for use with an ISO C compiler. int regcomp(regex_t *, const char *, int); int regexec(const regex_t *, const char *, size_t, regmatch_t[], int); size_t regerror(int, const regex_t *, char *, size_t); void regfree(regex_t *); The implementation may define additional macros or constants using names beginning with REG_. APPLICATION USAGE None. FUTURE DIRECTIONS None. SEE ALSO

1 participants
0 comments

Re: New XEmacsen at long last (was Re: Who broke the (athena) scrollbar thumb?) 25 years, 4 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > > Im also missing the "reset-face default fix/face-set-spec" fix. Is > > that still in the que? > > I have no idea from your description. It was not a patch by me. I though Stephen made one. The problem is that face-spec-set calls reset-face for the 'default font. This screws up your font settings big time if you are only using Custom to set your font. It is probably also the cause of the bad customize MULE interactions. It is a showstopper if ever I saw one. Jan

3 participants
2 comments

[Failure] XEmacs 21.2-b4 "Aglaophonos", i386-pc-win32 25 years, 4 months

Adrian Aichner

This is my first shot at building any 21.2 beta natively for WidowedNT4sp3 using MSDS C++ 5.0. dired.c fails to cooperate. Will look into this now. Adrian > XEmacs Build Report as generated > by build-report-version $Revision: 1.51 $ follows: > Contents of c:\export\home\tmp\xemacs-20\nt\Installation: > (Output from most recent run of ./configure) OS: Windows_NT XEmacs 21.2-b4 \"Aglaophonos\" configured for `i386-pc-win32'. Where should the build process find the source code? c:\\export\\home\\tmp\\xemacs-20\\nt What compiler should XEmacs be built with? ＠cl -nologo What window system should XEmacs use? MS Windows > Contents of c:\export\home\tmp\xemacs-20\nt\xemacs-20-make-all-r21-2b4.err > keeping lines matching > "^--\[\[\|\]\]$\|^$cd\|n?make$\s-\|errors?\|warnings?\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compil$ing\s-+in\|ation$\|not\s-+found\|^While\s-+compiling.*$ \s-+.+$*\|^Note:" > and then deleting lines matching > "confl.*with.*auto-inlining" cd c:\export\home\tmp\xemacs-20\nt\ nmake -f xemacs.mak PACKAGEPATH="c:\\Program Files\\XEmacs\\xemacs-packages" HAVE_MSW=1 HAVE_NATIVE_SOUND=1 HAVE_XPM=1 XPM_DIR="c:\export\home\tmp\xpm-3.4k" HAVE_PNG=1 PNG_DIR="c:\export\home\tmp\libpng-1.0.2" HAVE_TIFF=1 TIFF_DIR="c:\export\home\tmp\tiff-v3.4" HAVE_JPEG=1 JPEG_DIR="c:\export\home\tmp\jpeg-6b" ZLIB_DIR="c:\export\home\tmp\zlib" DEBUG_XEMACS=0 all Compilation started at Sun Nov 29 13:23:41 1998 Compiling in support for native GUI. Compiling in support for XPM images. Compiling in support for GIF images. Compiling in support for PNG images. Compiling in support for TIFF images. Compiling in support for JPEG images. Compiling in support for toolbars. Compiling in support for dialogs. Compiling in support for native sounds. Compiling in fast dired implementation. copy puresize-adjust.h ..\src ..\nt\runemacs.c(185) : warning C4101: 'sec_desc' : unreferenced local variable ..\src\glyphs-msw.c(1589) : warning C4146: unary minus operator applied to unsigned type, result still unsigned c:\program files\devstudio\vc\include\direct.h(158) : warning C4030: first formal parameter list longer than the second list ..\src\gif_io.c(118) : warning C4013: 'close' undefined; assuming extern returning int ..\src\data.c(778) : warning C4244: '=' : conversion from 'unsigned long ' to 'unsigned char ', possible loss of data ..\src\dired.c(964) : error C2065: 'user_cache' : undeclared identifier ..\src\dired.c(964) : warning C4047: '=' : 'int ' differs in levels of indirection from 'void *' ..\src\dired.c(965) : error C2065: 'user_cache_len' : undeclared identifier ..\src\dired.c(966) : error C2065: 'user_cache_max' : undeclared identifier NMAKE : fatal error U1077: 'cl' : return code '0x2' Compilation exited abnormally with code 2 at Sun Nov 29 13:27:59 -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: package buglettes 25 years, 4 months

Jan Vroonhof

Andy Piper <andyp(a)parallax.co.uk> writes: > By default package-get now goes to the local disk to install packages. This > is ok (alhough I'm not convinced that the local disk is any more useful a > default than xemacs.org) It needs to have A location to get package-get-index from. however to go somewhere else I assume I have to do > Manage Packages -> add download site -> some site. If I select xemacs.org, > package updated correctly now gets stuff from xemacs.org but > this is not reflected in the menu list (i.e. I would expect a tick by > xemacs.org on the menu to indicate that I had selected it). That would be nice yes. I have no time now but it should be trivial to make these entries button style. > Also are the various options one selects (not using PGP, download site) > saved somehow? They can be saved using M-x customize-group RET package-get RET > Also IMHO having no default download site would be better than the local > disk. Currently if no download site is selected and you don't have a > package in /tmp its not obvious what's going wrong. I would have thought an > error message along the lines of "please select a download site" with local > disk (or /tmp) as one of the options would be more helpful. Note that by default package-get-remote is nil. Probably the package fetching code (but not the package-get-index code) should complain if it still is. Jan

1 participants
0 comments

Is anyone having luck with cvs.xemacs.org right now? 25 years, 4 months

SL Baur

I'm trying to do a fresh xemacs-packages checkout and I'm either getting `cvs [server aborted]: out of memory; can not allocate 2808757 bytes' while checking out SKK, or it's puking all over my disk. Tiny sample: cvs checkout: warning: unrecognized response `＠small"x' from cvs server cvs checkout: warning: unrecognized response `mple' from cvs server cvs checkout: warning: unrecognized response `M-x view-pr' from cvs server cvs checkout: warning: unrecognized response `＠end smallex' from cvs server cvs checkout: warning: unrecognized response `mple' from cvs server cvs checkout: warning: unrecognized response `' from cvs server cvs checkout: warning: unrecognized response `You arerprompqedrto eNter arP-oblem Reportridsn)ificetion Number' from cvs server Sigh.

1 participants
0 comments

wnn6 on Pyrenean-pre8 25 years, 4 months

Tetsuya HOYANO

Automatic detection of wnn that installed under `/usr/local/include/wnn' is gone and build with `--with-wnn6' failed as follows. Sorry for only reporting... --HOYANO gcc -c -g -Wall -mpentiumpro -march=pentiumpro -Demacs -I. -DHAVE_CONFIG_H -I/usr/X11/include mule-wnnfns.c mule-wnnfns.c:273: wnn/commonhd.h: No such file or directory mule-wnnfns.c:275: wnn/jllib.h: No such file or directory mule-wnnfns.c:276: wnn/cplib.h: No such file or directory make[1]: *** [mule-wnnfns.o] Error 1 make[1]: Leaving directory `/home2/beta/xemacs-20/src' make: *** [src] Error 2

2 participants
2 comments

Re: Custom vs. specifier terminology in lisp/faces.el 25 years, 4 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > Per> I wrote the face specification interface to have something > Per> simple I could understand that would work the same on both > Per> Emacs and XEmacs, and hoped someone someday would write a > Per> function to translate the simple face specifications into > Per> XEmacs specifiers. Much the same idea as easymenu is based > Per> on. I believe Hrvoje Niksic tried, but found that the XEmacs > Per> specifiers missed some (tags?) necessary. > > OK, I'll look at this. Missing tags shouldn't be a problem, Custom > can define its own. Which is exactly the problem I encountered -- the custom [note the pun] tagset functions get a DEVICE argument, whereas Custom would need a FRAME argument. This was the killer problem against porting Custom to use specifiers. I also couldn't fathom a way to extend custom tagsets without breaking backward compatibility (and NO, we can't know that there is no code using that stuff.) But read on. [Imagine Hrvoje with a lamp lit above his head] A way to fix it in a backward-compatible way has popped into my head! Just add another optional argument to `define-specifier-tag' that determines how PREDICATE will be called: (define-specifier-tag TAG &optional PREDICATE HOW-TO-CALL) Documentation: Define a new specifier tag. If PREDICATE is specified, it should be a function of one argument (by default a device) that specifies whether the tag matches that particular device. If PREDICATE is omitted, the tag matches all devices. With HOW-TO-CALL you can specify the argument that will be provided to PREDICATE; legal values are `device' for a device argument, `frame' for a frame argument, and `locale' for a generalized locale argument (window, buffer, frame, or device.) For backward compatibility, nil is the same as `device'. You can redefine an existing user-defined specifier tag. However, you cannot redefine the built-in specifier tags (the device types and classes) or the symbols nil, t, 'all, or 'global. Custom would set up its specifier tag for the background-mode property of the locale, or frame (but NOT device!) Note that only the interface light-bulb is lit -- implementation might still be hard, especially if we did it right. In this case, "do it right" means that a statement like automagically changes face instances in the selected window: (set-face-background 'default "black" (selected-window)) > Possibly there's something missing in the semantics of specifiers, > or maybe Hrvoje just didn't like the apparent bloat. See above, and sorry for the time it took me to respond. RL is a bitch. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- aibohphobia (ay' bo fo beeya): n. The fear of palindromes.

1 participants
0 comments

Re: gnus-setup breaks file-coding 25 years, 4 months

Adrian Aichner

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> Gnus v5.6.43 XEmacs 21.0 "Pyrenean-pre7" [Lucid] Andy> (i586-pc-cygwin32) of Thu Nov 26 1998 on ARMAGEDON 200 Andy> red.parallax.co.uk NNTPcache server V1.0.7.1 Oct 31 1997 Andy> ready (posting ok). Andy> I have tracked down my file-coding problems to Andy> gnus-setup. If I load up a msdos style file in a vanillla To add to my previous assessment: Setting gnus-use-tm nil will allow you to (require 'gnus-setup) with no harm. You won't get "Tools for MIME" though. Adrian PS: My incoming mails are still waiting for our european Locus Notes server to come back to life. Andy> xemacs 21.0 built with file coding (mainly applicable under Andy> windows) I get the required recognition by the "Noconv:T" on Andy> the left of the modeline. However, if I load gnus-setup Andy> first the file is not recognised (I see "Noconv") and M-x Andy> toggle-buffer-file-coding-type has no effect. Some Andy> conversion is obviously done because I don't see ^M's but it Andy> is mostly broken. I would hazard a guess that this is broken Andy> under mule also. Andy> andy Andy> ------------------ Environment follows ------------------ Andy> (setq gnus-nntp-server "news") (setq Andy> gnus-secondary-select-methods '((nnfolder "private" Andy> (nnfolder-directory "~/mail/")))) (setq gnus-local-domain Andy> "parallax.co.uk") (setq gnus-local-organization "Parallax Andy> Solutions Ltd., Coventry, England.") (setq gnus-load-hook Andy> '(tm-setup/load-gnus)) (setq gnus-show-mime t) (setq Andy> gnus-summary-mode-hook Andy> '(gnus-xmas-switch-horizontal-scrollbar-off Andy> gnus-xmas-setup-summary-toolbar gnus-xmas-summary-menu-add Andy> mc-install-read-mode)) (setq gnus-parse-headers-hook Andy> '(gnus-set-summary-default-charset gnus-decode-rfc1522)) Andy> (setq gnus-group-mode-hook '(gnus-xmas-setup-group-toolbar Andy> gnus-xmas-group-menu-add)) (setq gnus-exit-gnus-hook Andy> '(#<compiled-function nil "...(18)" [frame-live-p Andy> toolbar-news-frame frame-list delete-frame nil] 2>)) (setq Andy> gnus-article-x-face-command Andy> 'gnus-xmas-article-display-xface) (setq Andy> gnus-show-mime-method 'gnus-article-preview-mime-message) Andy> (setq gnus-decode-encoded-word-method Andy> 'gnus-article-decode-encoded-word) (setq Andy> gnus-article-mode-hook '(gnus-xmas-article-menu-add Andy> turn-off-scroll-in-place)) (setq gnus-read-active-file nil) Andy> (setq gnus-save-killed-list nil) (setq gnus-startup-hook Andy> '(tm-gnus/bbdb-setup)) (setq gnus-asynchronous nil) ;; Andy> (makeunbound 'gnus-use-article-prefetch) ;; (makeunbound Andy> 'gnus-prefetched-article-deletion-strategy) ;; (makeunbound Andy> 'gnus-use-header-prefetch) ;; (makeunbound Andy> 'gnus-async-prefetch-article-p) ;; (makeunbound Andy> 'gnus-global-score-files) ;; (makeunbound Andy> 'gnus-score-file-single-match-alist) ;; (makeunbound Andy> 'gnus-score-file-multiple-match-alist) ;; (makeunbound Andy> 'gnus-score-file-suffix) ;; (makeunbound Andy> 'gnus-adaptive-file-suffix) ;; (makeunbound Andy> 'gnus-score-find-score-files-function) ;; (makeunbound Andy> 'gnus-score-interactive-default-score) ;; (makeunbound Andy> 'gnus-score-expiry-days) ;; (makeunbound Andy> 'gnus-update-score-entry-dates) ;; (makeunbound Andy> 'gnus-orphan-score) ;; (makeunbound 'gnus-decay-scores) ;; Andy> (makeunbound 'gnus-decay-score-function) ;; (makeunbound Andy> 'gnus-score-decay-constant) ;; (makeunbound Andy> 'gnus-score-decay-scale) ;; (makeunbound Andy> 'gnus-home-score-file) ;; (makeunbound Andy> 'gnus-home-adapt-file) ;; (makeunbound Andy> 'gnus-default-adaptive-score-alist) ;; (makeunbound Andy> 'gnus-ignored-adaptive-words) ;; (makeunbound Andy> 'gnus-default-ignored-adaptive-words) ;; (makeunbound Andy> 'gnus-default-adaptive-word-score-alist) ;; (makeunbound Andy> 'gnus-adaptive-word-minimum) ;; (makeunbound Andy> 'gnus-adaptive-word-no-group-words) ;; (makeunbound Andy> 'gnus-score-mimic-keymap) ;; (makeunbound Andy> 'gnus-score-exact-adapt-limit) ;; (makeunbound Andy> 'gnus-score-uncacheable-files) ;; (makeunbound Andy> 'gnus-score-default-header) ;; (makeunbound Andy> 'gnus-score-default-type) ;; (makeunbound Andy> 'gnus-score-default-fold) ;; (makeunbound Andy> 'gnus-score-default-duration) ;; (makeunbound Andy> 'gnus-score-after-write-file-function) ;; (makeunbound Andy> 'gnus-score-thread-simplify) ;; (makeunbound Andy> 'gnus-topic-mode) (setq gnus-topic-mode-hook Andy> '(gnus-xmas-topic-menu-add)) ;; (makeunbound Andy> 'gnus-topic-line-format) ;; (makeunbound Andy> 'gnus-topic-indent-level) ;; (makeunbound Andy> 'gnus-topic-display-empty-topics) (setq nnmail-split-methods Andy> '(("list.xemacs-beta" "^..:.*xemacs-beta") Andy> ("list.xemacs-patches" "^..:.*xemacs-patches") Andy> ("list.xemacs-nt" "^..:.*xemacs-nt") ("list.ejb-interest" Andy> "^..:.*\$EJB-\\|ejb-\$") ("other" ""))) (setq Andy> nnmail-spool-file "po:andyp") (setq nnmail-movemail-args Andy> '("-x" "-r" "^..:.*\$aichner\\|xemacs-\\|EJB-\\|ejb-\$")) Andy> (setq nnmail-tmp-directory "~/mail/") (setq Andy> message-user-organization t) (setq Andy> message-forward-start-separator " -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: Custom vs. specifier terminology in lisp/faces.el 25 years, 4 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > Many of the face functions associated with Custom (some of which > have leaked into other libraries, such as lisp/faces.el) use > terminology different from that documented in Info | Lispref | > Specifiers. For example, some functions (eg `face-spec-set') > specialize the specifier concept of "locale" to "frame" (in the > sense that the argument which represents the specifier's locale is > called "frame"; I don't think the semantics are altered at all). In > other cases the representation of objects is changed. Eg, > specifiers characterize the display with a tag-set [simple list] > like `(x color)' while Custom uses alists like `((type x) (class > color))'. Unlike Per, I think it would be just fine to make the internal Custom functions specifier-friendly. The interface should remain unchanged, of course. > (1) Why does Custom do this with faces? Because I found it very very very hard to do it otherwise. > (2) Can the interface of a function like `faces-spec-set' in > lisp/faces.el be changed? (It's one of the ones moved from > cus-face.el.) I would like it to use the specifier interface (some > combination of FACE LOCALE TAG-SET EXACT-P HOW-TO-ADD) but I suspect > that that would cause problems in Custom. Would it be a problem to > add a (partially redundant) &optional tag-set argument? It would probably not be a problem, as long as you make sure that old interface works for backward compatibility. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- HOW YOU CAN TELL THAT IT'S GOING TO BE A ROTTEN DAY: #15 Your pet rock snaps at you.

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