November 2000 - XEmacs-Beta - XEmacs Mailing List Archives

PCL-CVS 2_9_9 (XEmacs package 1.50) 23 years, 5 months

Mark Purtill

We just installed XEmacs 21.1 p3 on our Solaris box, and with it came a new version of PCL-CVS, which seems to have a somewhat altered user interface. Unfortunately, the documentation is not quite up-to-date (it claims to be for CVS version 2.5); it says "e" runs ediff, which is incorrect. ("e" runs cvs-examine, while "d e" runs ediff.) Is there a more up-to-date info-file available? -- ^.-.^ Mark Purtill <mpurtill(a)softwarerevolution.com> (425)345-6471 ((")) Software Revolution, 3330 Monte Villa Pkwy #100 Bothel WA 98021

3 participants
2 comments

Re: PSGML's syntax table for HTML error in XEmacs 21.1 23 years, 5 months

Gleb Arshinov

>>>>> "Jerry" == Jerry James <james(a)eecs.ukans.edu> writes: Gleb> It seems like I hit the problem previously reported in Gleb> http://www.xemacs.org/list-archives/xemacs-beta/200009/msg00153.html Jerry> The problem there was that Stephen had an old version of Jerry> PSGML installed. You appear to have the latest version, Jerry> however. Also note that Stephen's problem was with XML, Jerry> but your patch modifies sgml-parser-syntax. If you look at Jerry> the code in psgml-parse.el just after your patch, you will Jerry> see that the colon *is* in xml-parser-syntax. So this does Jerry> not seem to be the problem previously reported. Hi Jerry, The way I read it, Stephen's problem is exact same one I am reporting. Let me try to provide more detail. Jerry> What, exactly, were you trying to do, and what did PSGML do Jerry> that you consider incorrect? Basically, I wanted to migrate my HTML documents from "-//W3C//DTD HTML 4.0 Transitional//EN" to "-//W3C//DTD XHTML 1.0 Transitional//EN". Both are types of HTML. The latter also happens to be XML (XHTML is supposed to be an intersection of HTML spec and XML spec). I had old PSGML packages which did not include XHTML DTDs, so I upgraded all the packages to the latest versions. Then I tried to validate a small XHTML document: Jerry> Can you give some example SGML that shows the problem? <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> <html> <head> <title>My Title</title> </head> <body> <h1>My Title</h1> </body> </html> Save this to a file xhtml_test.html. Open it. Run C-c C-p `sgml-parse-prolog'. At this point PSGML attempted to compile xhtml1-transitional.dtd, and barfed while parsing it (i.e. while parsing the DTD not the XHTML test document). The backtrace for this is in my original message. After much scratching my head, I figured out that lines of the form: xml:lang language code (as per XML 1.0 spec) in xhtml1-transitional.dtd were causing the parsing error. When I removed these lines, PSGML was able to parse and compile the DTD. The reason parsing of this DTD fails seems to be that PSGML uses sgml-parser-syntax to parse the DTD and it considers ':' a terminator for the token. So adding ':' to sgml-parser-syntax got rid of the problem for me. Jerry> Finally, if this really is a problem with PSGML, it should Jerry> also be reported to Lennart Staflin, the PSGML maintainer. The way I read Stephen's message, it worked for him in 21.2. If this works in 21.2 but not in 21.1, I figure XEmacs team should have the first try. Gleb

1 participants
0 comments

FW: mswindows_handle_scrollbar_event crash in unpatched Notus, local build (PR#1504) 23 years, 5 months

Paul Krause

Is anybody monitoring the XEmacs Bug Tracking system (Jitterbug/XEmacs-bugs) anymore? There doesn't seem to have been any activity there since August, and the incoming queue is becoming so long that I'm beginning to wonder if my report will ever make it to the top. -----Original Message----- From: xemacsbugs(a)cvs.xemacs.org [mailto:xemacsbugs＠cvs.xemacs.org] Sent: Friday, November 10, 2000 11:54 AM To: pkrause(a)soundbite.com Subject: Re: mswindows_handle_scrollbar_event crash in unpatched Notus, local build (PR#1504) Thank you for your submission to the XEmacs bug tracking system. We will look at your message as soon as possible. If we have any questions, we will contact you. If you would like to view the status of your report, which is 1504, point your web browser at http://cvs.xemacs.org/XEmacs-bugs?findid=1504 Again, thank you for your support of XEmacs! -- The XEmacs development team

1 participants
0 comments

PSGML's syntax table for HTML error in XEmacs 21.1 23 years, 5 months

Gleb Arshinov

It seems like I hit the problem previously reported in http://www.xemacs.org/list-archives/xemacs-beta/200009/msg00153.html Note that this is in Xemacs 21.1. Adding ':' to the list of characters as follows, gets rid of the error. gleb＠one 9 % diff -c psgml-parse.el~ psgml-parse.el *** psgml-parse.el~ Fri Oct 6 01:38:12 2000 --- psgml-parse.el Fri Nov 10 15:32:29 2000 *************** *** 291,297 **** (mapconcat (function (lambda (c) (modify-syntax-entry c "w" sgml-parser-syntax))) ! "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrtsuvwxyz" "") (mapconcat (function (lambda (c) (modify-syntax-entry c "_" sgml-parser-syntax))) "-.0123456789" "") --- 291,297 ---- (mapconcat (function (lambda (c) (modify-syntax-entry c "w" sgml-parser-syntax))) ! ":ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrtsuvwxyz" "") (mapconcat (function (lambda (c) (modify-syntax-entry c "_" sgml-parser-syntax))) "-.0123456789" "") Backtrace Signaling: (error "Name expected; at: :lang NMT") signal(error ("Name expected; at: :lang NMT")) cerror("Name expected; at: %s" ":lang NMT") apply(cerror ("Name expected; at: %s" ":lang NMT")) error("Name expected; at: %s" ":lang NMT") apply(error "Name expected; at: %s" ":lang NMT") sgml-error("Name expected; at: %s" ":lang NMT") apply(sgml-error "Name expected; at: %s" ":lang NMT") sgml-parse-error("Name expected") sgml-check-declared-value() sgml-parse-attribute-definition() sgml-declare-attlist() sgml-parse-markup-declaration(dtd) sgml-check-dtd-subset() sgml-compile-dtd("/home/gleb/local/xemacs-packages/etc/psgml/xhtml1-transitional.dtd" "/home/gleb/local/xemacs-packages/etc/psgml/cdtd/xhtml1-transitional" nil) sgml-bdtd-load("/home/gleb/local/xemacs-packages/etc/psgml/cdtd/xhtml1-transitional" "/home/gleb/local/xemacs-packages/etc/psgml/xhtml1-transitional.dtd" nil) sgml-try-merge-special-case("-//W3C//DTD XHTML 1.0 Transitional//EN//" "/home/gleb/local/xemacs-packages/etc/psgml/xhtml1-transitional.dtd" "/home/gleb/local/xemacs-packages/etc/psgml/cdtd/xhtml1-transitional" nil) sgml-try-merge-compiled-dtd("-//W3C//DTD XHTML 1.0 Transitional//EN" "/home/gleb/local/xemacs-packages/etc/psgml/xhtml1-transitional.dtd") sgml-push-to-entity(("HTML" dtd ("-//W3C//DTD XHTML 1.0 Transitional//EN" nil. "/home/gleb/") nil)) sgml-setup-doctype("HTML" ("-//W3C//DTD XHTML 1.0 Transitional//EN" nil . "/home/gleb/")) sgml-do-doctype() sgml-parse-markup-declaration(prolog) sgml-parse-prolog() sgml-load-doctype() sgml-need-dtd() sgml-parse-to(62) #<compiled-function nil "...(23)" [sgml-throw-on-warning push-mark sgml-note-change-at sgml-parse-to trouble (sgml-parse-until-end-of nil t) message "Ok"] 3 ("/home/gleb/local/xemacs-packages/lisp/psgml/psgml-edit.elc" . 10031) nil>() call-interactively(sgml-next-trouble-spot) XEmacs psgml package version 1.20 Emacs : XEmacs 21.1 (patch 3) "Acadia" [Lucid] (sparc-sun-solaris2.6) of Tue Aug 3 1999 on fsui02 Package: psgml.el 1.2.1 current state: ============== (setq major-mode 'list-packages-mode sgml-always-quote-attributes t sgml-auto-activate-dtd nil sgml-auto-insert-required-elements t sgml-balanced-tag-edit t sgml-catalog-files '("CATALOG" "/home/gleb/local/xemacs-packages/etc/psgml/CATALOG") sgml-declaration nil sgml-doctype nil sgml-ecat-files '("ECAT" "~/sgml/ECAT" "/home/gleb/local/xemacs-packages/etc/psgml/ECAT") sgml-indent-data nil sgml-indent-step 2 sgml-leave-point-after-insert nil sgml-live-element-indicator nil sgml-local-catalogs nil sgml-local-ecat-files nil sgml-markup-faces '((start-tag . bold) (end-tag . bold) (comment . italic) (pi . bold) (sgml . bold) (doctype . bold) (entity . bold-italic) (shortref . bold)) sgml-minimize-attributes nil sgml-normalize-trims t sgml-omittag t sgml-omittag-transparent nil sgml-parent-document nil sgml-public-map '("%S" "/home/gleb/local/xemacs-packages/etc/psgml%o/%c/%d") sgml-set-face nil sgml-shorttag t sgml-namecase-general t sgml-tag-region-if-active t )

2 participants
1 comments

Re: byte-compile emu-mule.el 23 years, 5 months

Adrian Aichner

>>>>> "SY" == Steve Youngs <youngs(a)xemacs.org> writes: SY> * "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: APA> This causes emu-mule.el (and some others requiring mule) not APA> to be byte-compiled when the package is built. Stephen> Do you mean that such files are sprinkled around outside Stephen> of the xemacs-packages/mule sources? If so, can you Stephen> suggest a way for me to quickly identify them (eg, grep Stephen> for BUILD_WITHOUT_MULE in package Makefiles)? Stephen> I would like to purge code that requires Mule to build Stephen> correctly from the main codebase. SY> Please don't. Having packages split across two different SY> places will make maintenance a bitch. Yeah Steve, you catch my drift. This was exactly the concern I tried to convey to Stephen. Building a package is just not as simple as marking all .el files in a dired buffer and byte-copmiling them all. But make distclean make bindist isn't really asking too much of people who want to build their own packages, I think. Having to copy xemacs-packages/Local.rules.template to xemacs-packages/Local.rules and configuring it correctly is the trickiest part. We should probably have a xemacs-packages/README file explaining this and advertising xemacs-packages/NEWS.packages as well. Steve, are you willing to write that file? Adrian SY> But what you could do is add a 'PROBLEMS' file to each SY> non-Mule package that contains Mule files. [1] [2] SY> ,----[ ./PROBLEMS ] SY> | This package contains files that will only byte-compile using a SY> | Mule-enabled XEmacs. SY> | SY> | Those files are: x.el, y.el, z.el ... SY> | SY> | If your XEmacs is not Mule-enabled, don't panic, this package does not SY> | lose any functionality by not having the above files byte-compiled. SY> `---- SY> These are the packages that have Mule files... [3] SY> ,----[ find -name "Makefile" -exec sh -c 'grep -H "_MULE" {}' \; ] SY> | ./comm/footnote/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./comm/mew/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./comm/mew/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./comm/tm/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./libs/apel/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./mule/edict/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./mule/egg-its/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./mule/leim/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./mule/locale/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./mule/mule-base/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./mule/skk/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./oa/calendar/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> | ./wp/auctex/Makefile:ifeq ($(BUILD_WITHOUT_MULE),) SY> `---- SY> Footnotes: SY> [1] I know that this isn't the cleanest of solutions, but I think its SY> a pretty good trade-off between ease of maintenance and user SY> complaint. So far, I've only seen one complaint like this (the SY> one that started this thread). SY> [2] Just mail them to me and I'll add them to the CVS tree. SY> [3] Obviously the packages under ./mule/ don't need this SY> 'enhancement'. SY> -- SY> |---<Regards, Steve Youngs>-----------[GnuPG KeyID: 59E4C4B2]---| SY> | XEmacs - It's not just an editor... | SY> | It's a way of life. | SY> |----------------------------------<mailto:youngs＠xemacs.org>---| -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org

3 participants
3 comments

Bug in many .texi files 23 years, 5 months

Stephen J. Turnbull

Many of our Texinfo files have file cross-references of the following form: *Note Sexp Types: (widget)Sexp Types, for information about widgets to use with the `:type' keyword. When you try to follow this cross reference, you get a error: No such node: Sexp Types, for information about widgets to use with the `:type' keyword -- 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."

3 participants
5 comments

Re: Patch queue status 23 years, 5 months

Adrian Aichner

>>>>> "Yoshiki" == Yoshiki Hayashi <yoshiki(a)xemacs.org> writes: Yoshiki> --Multipart_Wed_Nov__8_16:54:55_2000-1 Yoshiki> Content-Type: text/plain; charset=US-ASCII Yoshiki> This is my only job as a patch tracker... Yoshiki> Here's my patch queue status as of yesterday. If you have Yoshiki> any patches unlisted without response, please send them Yoshiki> again. Yoshiki> All date is converted to GMT. There might be some incorrect Yoshiki> URI. Yoshiki> For all reviewers: Yoshiki> Please review them if you have time. Hello Yoshiki, I intend to review following patch on the weekend. First perusal a few days ago looked promising. What about ps-print relative to MULE. Are there any opne issues with that? I intend to compare this to os/ps-print-nomule. Best regards, Adrian Yoshiki> 1999-12-29 "Kevin Delia" <Kevin.Delia(a)globalone.net> Yoshiki> Fix for ps-print.el used by NT XEmacs Yoshiki> <386A47EC.DCFBB7B7(a)globalone.net> -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org

3 participants
2 comments

Mouse problems in Beta 35 Nike 23 years, 5 months

Peter B. West

Hello all. I'm still running the version above, still, and I have noticed some difficulties with the mouse for some time now. I could not use the mouse to select text for searching via C-r or C-s. I put it down to user incompetence, and was unprepared to search the documents, so I just put up with it. Recently I was using an earlier version (can't tell you which one) on a Solaris, and to my surprise, such selections seemed to work quite intuitively. On my linux 2.2.16-3, if I C-s, then move the cursor and double-click to select a word, the word selects, but I get "Mark set" message, and have exited Isearch mode. I leave the text selected, C-s again. Selection remains. I then move the cursor over the minibuffer and Button-2. I get: Signaling: (invalid-function (#<marker at 4728 in MassText.dtd 0x874f0b4> . #<marker at 4721 in MassText.dtd 0x874f09c>)) (#<marker at 4728 in MassText.dtd 0x874f0b4> . #<marker at 4721 in MassText.dtd 0x874f09c>)() isearch-yank((#<marker at 4728 in MassText.dtd 0x874f0b4> . #<marker at 4721 in MassText.dtd 0x874f09c>)) #<compiled-function nil "...(5)" [isearch-yank get-selection] 2 941965 nil>() call-interactively(isearch-yank-selection) Incidentally, if at this point I decide I want another frame, and select New frame from the View menu on the Backtrace frame, I get the new frame, and I also get: (1) (error/warning) Error in `pre-command-hook' (setting hook to nil): (wrong-type-argument unable to bind this type of event #<misc-user-event (call-interactively make-frame)>) In the midst of all of this fun and games, I will sometimes find myself trapped in Isearch mode. Don't ask me how. I know that sometimes I can get this to work, but today is not one of those days. The moon is just past full. Nothing short of killing XEmacs seems to shake that darn Isearch mode. On the subject of mice and men, has anyone else noticed what happens when you drag a slider bar? Your mouse pointer gets ahead of the slider; mine does anyway. Keep the button down, and repeatedly move right and left. -- Peter B. West pbwest(a)powerup.com.au http://powerup.com.au/~pbwest "Lord, to whom shall we go?"

1 participants
0 comments

Re: byte-compile emu-mule.el 23 years, 5 months

Dhruva_KRISHNAMURTHY＠delmia.com

Hi, The main problem I faced was not with the functional aspect of the XEmacs as a whole, the "byte-force-recompile" of the xemacs-package folder stops at this point and does not proceed beyond this. This acts as a unsurpassable hurdle. An alternative would be for XEmacs to ignore this and go ahead with byte-compiling the other folders. I am not sure whether adding a PROBLEM file would help. I may be wrong though. I am a novice and am not sure whether I should be giving suggestions. with best regards, dhruva

2 participants
1 comments

ldap on native win32 23 years, 5 months

Fabrice Popineau

Ldap is available on many win32 platforms, but unfortunately not on all of them. Compiling with ldap is ok with nt, but xemacs.exe will fail to load on platforms lacking Wldap32.dll . What would be an acceptable solution to enable ldap on win32 platforms that have this dll ? One immediate solution is to encapsulate calls to basic ldap_* C functions, and let them return a default value. But this will lead to ldap functions being available at the elisp level, but doing nothing at the C level. Another answer would be to put the ldap stuff in a module, but the modules are not yet supported on native win32. Any idea on this subject ? -- Fabrice

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