August 2007 - XEmacs-Beta - XEmacs Mailing List Archives

Re: New Test for file modification 17 years, 3 months

Aidan Kehoe

Ar an seachtú lá déag de mí Lúnasa, scríobh Stephen J. Turnbull: > [...] Also, as long as we're here, it has long been my opinion that there > should be a single test suite, with individual tests conditionalized on > version as appropriate. This could be packaged, which would also make > test-harness.el available to packages for their own automated tests. > > However Martin was quite strongly opposed, on the grounds that tests are > very often implementation specific. My response to that (at the risk of > understating his reasons) is that where code can be shared, it should be, > and where it can't be, it should be explicitly marked as such. The one > test suite, version-conditional tests satisfies both criteria IMO. > > Comments? Yes, that’s a reasonable approach. > Vin Shelton writes: > > > So, I think there are 3 things wrong here: > > > > (1) [Minor] the "Wrote /home/acs/test-revert-buffer-resets-modiff" > > should be suppressed. > > Wrap the call to `save-buffer' in a call to `Silence-Message'. This > may have been intentional to ensure a reminder to fix: > > > BTW, why is it writing this file to my home > > directory? Shouldn't the test use some temporary directory or the > > build or test directory? > > Yes. I couldn't remember whether `make-temp-name' was the sanctioned > (robust and secure) way to do this, so I punted. It is, AIUI. Though the Gnus people do check with #’file-already-exists after they call it--see http://tinyurl.com/2hm355 in Google code search. > > (2) The actual unexpected errors: "Unsupported Unicode code point"... > > If Aidan wants to work on this, he probably knows more about it than I > do offhand. If he doesn't, I'll get to it. The issue here is that I just changed the Lisp reader to error when it sees a Unicode code point that the current XEmacs doesn’t support. Portable code needs to be able to handle this case, because that’s what GNU does too; and we support all valid UCS code points right now in Mule XEmacs, so we don’t error illegitimately there. However, it happens *all the time* under non-Mule XEmacs, which is kind of the point of non-Mule XEmacs. Okay, I’ve got a solution; call #’read at runtime on escaped versions of the relevant strings. The tests aren’t executed on non-Mule, so the error won’t happen, but the Unicode escape functionality will still be tested in passing (while testing the coding-cookie-in-compiled-files functionality). I’ll send a patch later today. > > (3) The fact that the summary does not report the unexpected errors. > > This may be hard to do well. I'll take a look at it. > > > Unexpected error (error "Can't activate input method > > `german-postfix'") while executing interpreted code. > > This is due to the fact that the Makefile suppresses adding packages > to the load-path. Probably the best thing to do is have a > package-dependent-tests.el, which is run as a separate command. os-tests.el calls #’Skip-Test-Unless in a similar context (when components required for a test are not available) so something similar might be the least intrusive approach; I’m not certain what the right check would be, though-- (assq 'leim packages-package-list) ? But leim doesn’t provide all the input methods--egg and skk are exceptions, at least. -- On the quay of the little Black Sea port, where the rescued pair came once more into contact with civilization, Dobrinton was bitten by a dog which was assumed to be mad, though it may only have been indiscriminating. (Saki) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: New Test for file modification 17 years, 3 months

SL Baur

On 8/16/07, Stephen J. Turnbull <stephen(a)xemacs.org> wrote: > I don't have time to actually generate patches right now, but this can > wait a week to ten days, right? OK with me. Further general comments below. > Vin Shelton writes: > > > So, I think there are 3 things wrong here: > > > > (1) [Minor] the "Wrote /home/acs/test-revert-buffer-resets-modiff" > > should be suppressed. > > Wrap the call to `save-buffer' in a call to `Silence-Message'. This > may have been intentional to ensure a reminder to fix: This is a symptom of a bigger problem, in my opinion. `save-buffer' does not document that it can output a message and should. There's nothing to "fix" that's useful to me, but this needs to get documented. > > BTW, why is it writing this file to my home > > directory? Shouldn't the test use some temporary directory or the > > build or test directory? > > Yes. I couldn't remember whether `make-temp-name' was the sanctioned > (robust and secure) way to do this, so I punted. Is it? Inquiring minds want to know and it should be documented. -sb _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

font-lock-add-keywords and etc. 17 years, 3 months

John Kuhns

Hello, I saw a webpage describing a putback that added font-lock-add-keywords to xemacs. I have 21.4.20 here. What do I need to do to get that capability? Also I tried changing keyword if indentation likeso: (setq lisp-indent-function 'common-lisp-indent-function) (mapc #'(lambda (x) (put (cdr x) 'lisp-indent-function (car x))) '(((2 2 2 &rest 2) . foreach) ((2 2 2 2 2 2 2 &rest 2) . for) ((2 1 &rest 2) . if) ((2 &rest 2) . letseq))) All the other keywords work fine but <if> doesn't. Thanks, -John Kuhns _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

4 participants
3 comments

Re: Make the Mule-UCS CCL code a little saner. 17 years, 3 months

Aidan Kehoe

Ar an séú lá déag de mí Lúnasa, scríobh Mike FABIAN: > Yes, the same error message as in the build log: > > “Ccl error: Error in CCL program at code numbered ..., 5” Okay, perfect. Please do a M-x report-xemacs-bug and send on the output; I suspect optimisation or something of the sort (maybe the Union build?) in mule-ccl.c has led to register-code-conversion-map not working. -- On the quay of the little Black Sea port, where the rescued pair came once more into contact with civilization, Dobrinton was bitten by a dog which was assumed to be mad, though it may only have been indiscriminating. (Saki) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Make the Mule-UCS CCL code a little saner. 17 years, 3 months

Aidan Kehoe

(The problem in question is here: http://mid.gmane.org/s3thcn9doxz.fsf＠magellan.suse.de ) Ar an séú lá déag de mí Lúnasa, scríobh Mike FABIAN: > Aidan Kehoe <kehoea(a)parhasard.net> さんは書きました: > > > Ar an triú lá déag de mí Lúnasa, scríobh Mike FABIAN: > > > > > Aidan, > > > > > > did you find any solution to the CCL build problems in the XEmacs packages? > > > > Not yet; if as you say, you see it on all platforms, and I can’t see it on > > mine, then something’s very askew. > > Could it have something to do that I build the XEmacs packages in a > chroot which contains only the absolutely necessary things installed and > you are doing it in a “normal” system? That seems unlikely to me, but I can’t rule it out--thanks you for the information. If you start the XEmacs binary in question with -vanilla, and evaluate the following code in *scratch* -- paste it into the buffer, move to the last parenthesis, and hit C-j -- does it provoke an error message? (progn (register-code-conversion-map 'mucs-ccl-test-map-1 [10 10]) (register-code-conversion-map 'mucs-ccl-test-map-2 [0 1]) (ccl-execute [0 8 278815 4 -2 -1 (mucs-ccl-test-map-1 . code-conversion-map-id) (mucs-ccl-test-map-2 . code-conversion-map-id) 22] [0 0 0 0 0 0 0 0])) > > I haven’t yet tested Michael Sperber’s patch of > > http://mid.gmane.org/y9ltzr8hp05.fsf＠matt.informatik.uni-tuebingen.de ; > > hopefully this evening. If it works, I’ll commit it, and that should solve > > the package smoketest problems. -- On the quay of the little Black Sea port, where the rescued pair came once more into contact with civilization, Dobrinton was bitten by a dog which was assumed to be mad, though it may only have been indiscriminating. (Saki) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: [Q] Don't set the current langenv to ja just because someone used a japanese IM 17 years, 3 months

Aidan Kehoe

Ar an séú lá déag de mí Lúnasa, scríobh SL Baur: > On 8/15/07, Aidan Kehoe <kehoea(a)parhasard.net> wrote: > > > If the tramp package has been installed as a package, it automagically > > loads itself if a pathname matches some regexp of which I don't know > > the details. (I know this because I never use Tramp but still get > > "Loading tramp ..." during pathname completion now and then.) Because > > of this, the FSF's argument that Tramp is not distinct from XEmacs for > > the user clearly holds; if it were necessary for the user to activate > > the package for its functionality to be available in XEmacs, this would > > be less clear, and GPLV3 would have less relevance to XEmacs. > > It is clearly distinct from XEmacs, it is not distributed in the core > XEmacs tarball. It is also clearly a derived work and must be under the > GPL. The binding between tramp and core XEmacs is via the autoloads > mechanism that was designed by Stallman himself years and years ago. And by file-name-handler-alist , invisibly to the user. > The autoload may or may not be dumped with XEmacs. Remove the package and > it will not be, if you relink XEmacs. > > Nothing in the GPL v[123] discusses whether or not visibility to the user > has any relevance. > > What is the problem here? See 87zm1byrtr.fsf(a)gmx.de in the xemacs-review archives. The relevant paragraphs from the FSF copyright people: We believe that if someone shipped a GPLv3 Tramp with XEmacs, the entire XEmacs package would need to be shipped under the terms of GPLv3 as well. If developers wanted to leave GPLv2-or-later notices on the pieces under that license, to show other users which code had which license, that would be fine, but anybody distributing the whole combination would have to follow the rules of GPLv3. While I appreciate that Tramp is separable from the rest of XEmacs, they're not exactly completely independent works, either. As I understand it, if you take an XEmacs package that has Tramp bundled inside that, and then build and install that the normal way, XEmacs will automatically load Tramp on startup. To a user who wasn't familiar with the XEmacs architecture, there would be no reason to believe that the remote editing features were somehow separate from the rest of the editor. So, an XEmacs+Tramp distribution is not mere aggregation, but instead a combination, and you need to follow the terms of both programs' licenses to make that combination. In this case, the way to do that is to follow the terms of GPLv3, since that's what Tramp offers, and it's an option that's available for the rest of XEmacs too. Now of course that hasn’t been tested in court, but it’s not prima facie an unreasonable interpretation. -- On the quay of the little Black Sea port, where the rescued pair came once more into contact with civilization, Dobrinton was bitten by a dog which was assumed to be mad, though it may only have been indiscriminating. (Saki) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: [Bug: 21.5-b28] Crash in VM piping message to nonexistent command 17 years, 3 months

SL Baur

On 8/15/07, Stephen J. Turnbull <stephen(a)xemacs.org> wrote: > However, the suggestion there is that it's related to threads, eg, > some library is starting threads behind the program's back, which is > not the case AFAICS in ps or top. Libraries stealing signal handling can definitely cause wierd crashes. I think a library turning a non-threaded program into a threaded program might have the same problem. Also, XEmacs should never crash on a SIGPIPE even due to an OS or library bug. I think I'm not parsing: > What's fishy is that it we don't catch SIGPIPE There's a typo in there and my lonely blonde brain cell can't figure out the correction. -sb _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: [Q] Don't set the current langenv to ja just because someone used a japanese IM 17 years, 3 months

Aidan Kehoe

Ar an cúigiú lá déag de mí Lúnasa, scríobh Adrian Aichner: > > (An exception to this has just bitten us in the arse with Tramp, > > [...] Aidan, what is that issue with tramp you are referring to? If the tramp package has been installed as a package, it automagically loads itself if a pathname matches some regexp of which I don’t know the details. (I know this because I never use Tramp but still get "Loading tramp ..." during pathname completion now and then.) Because of this, the FSF’s argument that Tramp is not distinct from XEmacs for the user clearly holds; if it were necessary for the user to activate the package for its functionality to be available in XEmacs, this would be less clear, and GPLV3 would have less relevance to XEmacs. -- On the quay of the little Black Sea port, where the rescued pair came once more into contact with civilization, Dobrinton was bitten by a dog which was assumed to be mad, though it may only have been indiscriminating. (Saki) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

XEmacs Packages have been pre-released (2007-08-15-08) 17 years, 3 months

Norbert Koch

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey there everyone. I have just added the following packages to the 'Pre-Releases' directory: New Packages in Pre-Release: =========================== apel-1.33-pkg.tar.gz upstream version: 10.6 edt-1.14-pkg.tar.gz upstream version: none locale-1.27-pkg.tar.gz upstream version: none Previously Announced Packages Still in Pre-Release: ================================================== auctex-1.48-pkg.tar.gz upstream version: 11.55 calendar-1.33-pkg.tar.gz upstream version: none ediff-1.69-pkg.tar.gz upstream version: 2.75 eshell-1.11-pkg.tar.gz upstream version: 2.4.1 general-docs-1.05-pkg.tar.gz upstream version: none guided-tour-0.51-pkg.tar.gz upstream version: none hyperbole-1.17-pkg.tar.gz upstream version: 5.0 leim-1.25-pkg.tar.gz upstream version: none mule-base-1.52-pkg.tar.gz upstream version: none mule-ucs-1.15-pkg.tar.gz upstream version: 0.84 net-utils-1.53-pkg.tar.gz upstream version: N/A oo-browser-1.05-pkg.tar.gz upstream version: 4.08 perl-modes-1.10-pkg.tar.gz upstream version: none prog-modes-2.13-pkg.tar.gz upstream version: none psgml-1.45-pkg.tar.gz upstream version: 1.3.2 python-modes-1.09-pkg.tar.gz upstream version: none text-modes-1.95-pkg.tar.gz upstream version: none tramp-1.38-pkg.tar.gz upstream version: 2.0.56 viper-1.57-pkg.tar.gz upstream version: 3.09 xemacs-base-2.11-pkg.tar.gz upstream version: none Detailed Changes: ================ - ------- ChangeLog Entries from xemacs-packages/apel/ChangeLog ------- 2007-08-15 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.33 released. 2007-08-14 Aidan Kehoe <kehoea(a)parhasard.net> * pccl-20.el: * pccl-20.el (broken): * pccl-20.el (ccl-execute-eof-block-on-encoding-null): * pccl-20.el (ccl-execute-eof-block-on-encoding-some): * pccl-20.el (ccl-execute-eof-block-on-decoding-null): * pccl-20.el (ccl-execute-eof-block-on-decoding-some): Move all these tests to unconditionally returning t. We only support XEmacs 21.4 and XEmacs 21.5, where both of these things are true, and checking for CCL support at compile time is inappropriate when compile time can be a non-Mule XEmacs and runtime can be a Mule XEmacs. * pccl.el: Note that the logic of this package is rotten in our context. - ------- ChangeLog Entries from xemacs-packages/edt/ChangeLog ------- 2007-08-15 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.14 released. 2007-08-14 Aidan Kehoe <kehoea(a)parhasard.net> * edt.el (edt-load-keys): Respect the platform path separator when working out where to find edt-mapper.el. - ------- ChangeLog Entries from mule-packages/locale/ChangeLog ------- 2007-08-15 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.27 released. 2007-08-14 Aidan Kehoe <kehoea(a)parhasard.net> * app-defaults/de/Emacs: Apply Mike Fabian's patch of http://mid.gmane.org/s3ttzr780mm.fsf＠magellan.suse.de . This updates the German translation of the menus to better work with 21.5. Installing These: ================ Manually: - -------- 1) Download the packages that you want to install from: /ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/ 2) Unpack them to: [1] /usr/local/lib/xemacs/xemacs-packages/ 3) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.[245].x): - ---------------------------------------------- 1) Tools -> Packages -> Add Download Site -> Pre-Releases 2) Tools -> Packages -> List and Install 3) Select the packages you wish to install (there are brief instructions at the bottom of the packages buffer). 4) Packages -> Install/Remove Selected 5) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.1.14): - ------------------------------------------- 1) Options -> Manage Packages -> Add Download Site -> Pre-Releases 2) Options -> Manage Packages -> List and Install 3 - 5) As per XEmacs 21.[245].x. norbert - XEmacs Package Release Manager. Footnotes: [1] Note: Mule packages should be installed into: /usr/local/lib/xemacs/mule-packages/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGwq/Ngu3ywdHdhM0RAiYAAKCq7MLVx3gyPtN70KslXpJ0hSqx2ACg3DeX U3knQvuM7mFNcMA6xwKQREU= =M7+/ -----END PGP SIGNATURE----- _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Bug report 17 years, 3 months

Hossein et Isabelle Abbaspour

4 participants
6 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 August 2007