XEmacs Packages have been pre-released (2008-11-19-21)
16 years, 12 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:
===========================
auctex-1.51-pkg.tar.gz upstream version: 11.84
ediff-1.76-pkg.tar.gz upstream version: 2.75
viper-1.64-pkg.tar.gz upstream version: 3.09
Previously Announced Packages Still in Pre-Release:
==================================================
apel-1.33-pkg.tar.gz upstream version: 10.6
calendar-1.38-pkg.tar.gz upstream version: none
cedet-common-1.01-pkg.tar.gz upstream version: 1.0pre4
dired-1.19-pkg.tar.gz upstream version: 7.16
easypg-1.02-pkg.tar.gz upstream version: 0.0.16
edit-utils-2.40-pkg.tar.gz upstream version: none
edt-1.14-pkg.tar.gz upstream version: none
efs-1.34-pkg.tar.gz upstream version: 1.24
eieio-1.06-pkg.tar.gz upstream version: 1.0pre4
elib-1.13-pkg.tar.gz upstream version: 1.0
erc-0.22-pkg.tar.gz upstream version: Version 5.1.2 Revision: 1.796.2.6
eshell-1.16-pkg.tar.gz upstream version: 0fc80a3f6bb3bb59f42e9ff83cc8b89bf90fe658
eudc-1.40-pkg.tar.gz upstream version: 1.32
fsf-compat-1.17-pkg.tar.gz upstream version: none
games-1.18-pkg.tar.gz upstream version: 1.04
general-docs-1.05-pkg.tar.gz upstream version: none
gnus-1.93-pkg.tar.gz upstream version: 5.10.8
guided-tour-0.52-pkg.tar.gz upstream version: none
hm--html-menus-1.24-pkg.tar.gz upstream version: 5.9
hyperbole-1.17-pkg.tar.gz upstream version: 5.0
igrep-1.16-pkg.tar.gz upstream version: 2.111
latin-euro-standards-1.08-pkg.ta upstream version: 1.08
leim-1.27-pkg.tar.gz upstream version: none
locale-1.28-pkg.tar.gz upstream version: none
mail-lib-1.80-pkg.tar.gz upstream version: none
mh-e-1.31-pkg.tar.gz upstream version: 7.4.2
mule-base-1.53-pkg.tar.gz upstream version: none
mule-ucs-1.17-pkg.tar.gz upstream version: 0.84
net-utils-1.56-pkg.tar.gz upstream version: N/A
oo-browser-1.05-pkg.tar.gz upstream version: 4.08
os-utils-1.41-pkg.tar.gz upstream version: none
pcl-cvs-1.68-pkg.tar.gz upstream version: R-2_9_9
pcomplete-1.05-pkg.tar.gz upstream version: 1.1.6
perl-modes-1.14-pkg.tar.gz upstream version: none
prog-modes-2.17-pkg.tar.gz upstream version: none
ps-print-1.12-pkg.tar.gz upstream version: 6.5.6
psgml-1.45-pkg.tar.gz upstream version: 1.3.2
python-modes-1.10-pkg.tar.gz upstream version: 426
scheme-1.17-pkg.tar.gz upstream version: none
sh-script-1.24-pkg.tar.gz upstream version: 2.0f
skk-1.24-pkg.tar.gz upstream version: 10.62a
speedbar-1.29-pkg.tar.gz upstream version: 1.0pre4
text-modes-1.95-pkg.tar.gz upstream version: none
tm-1.39-pkg.tar.gz upstream version: none
tramp-1.40-pkg.tar.gz upstream version: 2.0.56
vc-1.45-pkg.tar.gz upstream version: none
vm-8.07-pkg.tar.gz upstream version: 8.0.12-devo
w3-1.35-pkg.tar.gz upstream version: 4.0pre47
x-symbol-1.11-pkg.tar.gz upstream version: 4.5.1
xemacs-base-2.18-pkg.tar.gz upstream version: none
xemacs-devel-1.78-pkg.tar.gz upstream version: none
xetla-1.02-pkg.tar.gz upstream version: steve(a)eicq.org--2005/xetla--main--1.1--version-0
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/auctex/ChangeLog -------
2008-11-19 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.51 released.
- ------- ChangeLog Entries from xemacs-packages/ediff/ChangeLog -------
2008-11-19 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.76 released.
2008-16-06 Michael Kifer <kifer(a)cs.stonybrook.edu>
* ediff-util.el (ediff-toggle-multiframe): Check if control window is
live.
(ediff-save-buffer): Let window-min-height to 2.
* ediff-wind.el (ediff-setup-windows-plain-compare): Avoid selecting
the minibuffer.
* ediff*.el, ediff.texi: Copied changes from Emacs CVS.
- ------- ChangeLog Entries from xemacs-packages/viper/ChangeLog -------
2008-11-19 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.64 released.
2008-11-16 Michael Kifer <kifer(a)cs.stonybrook.edu>
* viper-init.el (viper-ESC-keyseq-timeout): Make it into a function
instead of a variable.
* viper-util.el (viper-fast-keysequence-p): Changed to use
viper-ESC-keyseq-timeout as a function.
(viper-get-saved-cursor-color-in-replace-mode): Use defun instead of
defsubst.
* viper-cmd.el: Let line-move-visual to nil when using next-line or
previous-line.
(viper-R-state-post-command-sentinel): Use defun instead of defsubst.
* viper-keym.el (viper-ESC-key): Use (kbd "ESC").
* viper*.el, viper.texi: copied changes from Emacs CVS.
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.9 (GNU/Linux)
iD8DBQFJJHRwgu3ywdHdhM0RAoiuAKCFqVCSRKo239grYv0sNEVfSBZl5gCgm8ih
hE4KL1IuOTGMuqA2p5jXBhM=
=hMyP
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
21.5 Mule UTF use un-define (Mule-Ucs)
16 years, 12 months
Uwe Brauer
Hello
I have heard no very positive things about Mule UCS in the sense that
nobody besides its author really understands it.
that's why I am asking is it recommendable to use it via
(require 'un-define)
and
(set-default-coding-systems 'utf-8)
thanks
I am asking this because there are some issues with the latest babel.el
which now works with Xemacs (thanks to some extra work by the author)
but still has some coding issues, which I will report in the next email.
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
babel: problem with the output
16 years, 12 months
Uwe Brauer
Hello
This problem looks less wired in a way.
I want to translate
Nation-->Nación (spanish)
So first I don't have used
(set-default-coding-systems 'utf-8)
I open a new file I type Nation I run babel but I obtain
Nación
Which looks like UTF-8 buts somehow the *babel* buffer can not deal with
it.
So I thought using
(set-default-coding-systems 'utf-8)
Would solve the issue since it the buffer must display then utf-8
correctly but it does not so I am puzzled.
Most likely the solution is easy, can somebody please enlighten me
again?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
babel: problem with the input
16 years, 12 months
Uwe Brauer
Hello
As I said before babel.el is a very nice package and I hope to make it
run smoothly under xemacs.
There are two remaining problems concerning the coding, by this I mean
for the moment non-ascii (mostly iso-8859-1).
- the input contains non-ascii (say german->english)
- the output contains non-ascii (say english->german)
I must add that everything works fine under GNU emacs 22, for which this
pkg was written but the author was friendly enough to make it run under
Xemacs save this coding problems.
I will concentrate for the moment to Xemacs 21.4.19 Mule.
And I start with the first problem the input non ascii (German->English)
When I open a new file and type
höchst (like highest)
and save the file as test in iso-8859-1 coding
(file test gives test: ISO-8859 text
Or even as raw text-unix
Than everything works fine with babel
Now the problem is if I have set in my init file
(require 'un-define)
(set-default-coding-systems 'utf-8) ;Version:1.171
(register-input-method
"TeX" "UTF-8" 'quail-use-package
"\\" "LaTeX-like input method for many characters."
"latin-ltx")
(set-coding-priority-list '(utf-8))
(set-coding-category-system 'utf-8 'utf-8)
I open a new file
and type again
höchst
I save the file (file test2: ISO-8859 text)!!!! No UTF-8!
but babel fails:
Produces stuff which I attach
Now I save the file explicitly via
set-buffer-file-coding-system to utf-8 and right file test2 tells me it
is utf8 but again babel fails the way I described.
I am very puzzled by this can somebody please enlighten me.
The next mail describe the problem with the output when the output
contains non-ascii.
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
GC debugging tips?
16 years, 12 months
Julian Bradfield
Does anybody have any particular good tips for how to debug crashes
that happen in GC ?
I've contrived to provoke (repeatably) a crash in my own version,
which, upon bisection, turns out also to happen in the vanilla 21.4.21
code, albeit compiled with error-checking and debug, and without any
optimization.
(Load a 45MB VM folder, wait a while, and some time later VM does
something and then GC happens and crashes.)
It's a bit intimidating at first sight, since it happens about 300000
stack frames down, which makes the back-trace a little hard to read...
Since it's not my changes that are causing it, I'm not in a huge
hurry, but nonetheless, I don't want XEmacs segfaulting on me ever!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs ignores system dpi settings
17 years
Roni Simonian
My XEmacs seems to ignore overall system dpi settings. It has *very*
small fonts not only for the text but for the menus as well. It seems
like it's using it's own settings different from the rest of the
system.
This is a screen shot of the XEmacs window on top of a web page with
normal text and menu font sizes:
<http://picasaweb.google.com/theothersimonian/XEmacsScreenshot#52638051980...>
http://picasaweb.google.com/theothersimonian/XEmacsScreenshot#52638051980...
I have XEmacs 21.4 (patch 21) and XEmacs 21.5 (beta28). The former
used to look normal before the last reboot but the latter being like
this even before the reboot. 2 days ago I restarted the computer and
now both versions of XEmacs look like this. I did not change
anything recently. The automatic system updates were enabled and could
have changed something. The OS is Fedora 9 with GNOME.
Removing "init.el" did not help. I posted the question on several forums
and received no response.
Any help is greatly appreciated!!!
Thank you!
Roni.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: yet another XEmacs fork;-)
17 years
Aidan Kehoe
Ar an dara lá déag de mí na Samhain, scríobh Julian Bradfield:
> [Aidan wrote:]
>
> Thanks for those comments and incisive questions. I think I've already
> thought about most of them, though one did point out to me that I
> haven't checked everything I should have checked!
> [...] I don't know why you think the [Mule] coding systems won't know
> about Unicode.
You didn’t say anything at all about them knowing about Unicode!
> They don't right now, but I have lots of comments of the form
> /* ##### need to convert from Unicode here */ !
> This is just a generalization of the charset precedence lists already
> used in dealing with Unicode the mule-ucs and 21.5 way; or maybe it's
> just a generalization of Latin Unity. (I don't know, latin-unity is
> something I've never felt the need for - I usually know which European
> language I'm writing in, and otherwise I'm using utf-8 anyway.)
I don’t know what you mean by “generalisation” there.
> >We don’t have robust checks for whether a region is encodable or
> >not--see http://mid.gmane.org/18509.34907.513276.700290＠parhasard.net
> >for some work in that direction, and for me severely underestimating the
> >amount of work I have to do this year--but I can’t see that your
> >approach makes it easier.
>
> Thanks, interesting. I don't think I'd do it in lisp.
I would have been happy with it in Lisp, but the speed sucks, it needs to be
in C.
> >How are you encoding your Unicode characters in the escape-quoted external
> >encoding? Since this encoding is used for auto-saves and for byte-compiled
> >ELC files, it needs to be capable of encoding every possible XEmacs
> >character.
>
> Escape-quoted is an ISO2022 variant, and it can (and does) use the
> UTF-8 escape sequence.
You’ll need to implement that with the 21.4 code base. I’m sure it’ll be
easy to port stuff from 21.5, of course.
> [...]
> >Given that the Mule code points in 21.4 are 19 bits wide, with only #x80000
> >possible code points, and that Unicode’s code points go up to #x10FFFF,
> >how do you encode the excess of #x8FFFF code points?
>
> They're not 19 bits wide any more ;-)
OK; you hadn’t said that.
> >exception of the ISO IR 196 sequences that we use in escape-quoted
> >byte-compiled files in 21.5). We can’t easily do that on 21.5 given the
> >need for Windows support, something SXEmacs has dropped. Had you seen
> >that idea?
>
> Yes. But my preference at present is just to call out to libiconv
> internally for conversion, rather than actually doing encoding through
> iconv. Surely iconv conversion can be done in lisp, anyway?
Umm, well, the library was written in C, I don’t think anyone wants to port
it to Lisp! But bindings would be great, and implementing coding systems in
terms of iconv seems more or less ideal to me.
> My take on Windows is that I'm not actively hostile, so I don't want
> to do anything to make Windows support impossible, but I don't have,
> and am unlikely to make the effort to get, convenient access to a
> Windows development environment. (Maybe if my next laptop runs
> VMware...)
It might be reasonable to require
http://gnuwin32.sourceforge.net/packages/libiconv.htm for Mule support on
Win32, come to think of it.
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Need help with package maintenance
17 years
Marcus Harnisch
Hi all
Scratching an itch with mmm-mode, I found that the MMM package is in
need of some love. Better, I found that the latest version of MMM
(from 2004, BTW.) fixes the issue I am having.
Between our current version of MMM (0.4.7, 2001 A.D.) and the current
(0.4.8), there have been some changes in upstream file organization.
The current state of my work is that everything compiles with my
XEmacs 21.5.b28 and works as expected. In particular that bug is gone!
I split the ChangeLog into an upstream version and an XEmacs version
to track changes separately.
My questions are regarding packaging. Current MMM uses autoconf with
all these additional files. We're not really using any of these. Which
of these go into our CVS? Do we have to ship these files with the
compiled package for legal reasons?
What about pre-generated info files? These are really just courtesy
copies so I suppose we don't have to check them in.
Here is the list of files I am not sure what to do with:
Unknown INSTALL
Unknown Makefile.am
Unknown Makefile.in
Unknown acinclude.m4
Unknown aclocal.m4
Unknown configure
Unknown configure.in
Unknown elisp-comp
Unknown install-sh
Unknown mdate-sh
Unknown missing
Unknown mkinstalldirs
Unknown stamp-vti
Any ideas?
How shall we proceed?
Thanks
Marcus
--
note that "property" can also be used as syntaxtic sugar to reference
a property, breaking the clean design of verilog; [...]
(seen on http://www.veripool.com/verilog-mode_news.html)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Need help updating MMM package!
17 years
Marcus Harnisch
Hi all
In case you have a deja vu -- I tried sending something like this
yesterday, without success.
I am trying to update the MMM package to its latest updstream version
(dated 2004!). Most things are done, but I am not certain about
carrying over some new files:
- pre generated info files. Drop them since we regenerate these
anyway?
- autocrap. MMM has been converted, adding a few files which we will
not likely use. For legal reasons, I suppose we will have to copy
them, no? Disk space is cheap these days.
I have taken the liberty to split the ChangeLog into a
ChangeLog-upstream and ChangeLog (for XEmacs changes). The current
situation would lead to a mess after integrating upstream changes.
Regards
Marcus
--
note that "property" can also be used as syntaxtic sugar to reference
a property, breaking the clean design of verilog; [...]
(seen on http://www.veripool.com/verilog-mode_news.html)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta