Re: [slime-devel] Re: match-string-no-properties missing?
17 years, 4 months
Didier Verna
[ Cc'ing to xemacs-beta ]
Nathan Bird <nathan(a)acceleration.net> wrote:
> Marco Baringer wrote:
>> Alberto Riva <ariva(a)ufl.edu> writes:
>>
>>
>>> Hi,
>>>
>>> I recently updated to the latest slime from CVS, and now every time I
>>> do a M-. I get an emacs message that says "Symbol's function
>>> definition is void: match-string-no-properties."
>>>
>>> My emacs is XEmacs 21.4 (patch 15) (x86_64-redhat-linux, Mule). All
>>> help appreciated! Thanks,
>>>
>>
>> using "GNU Emacs 22.0.50.1 (powerpc-apple-darwin7.9.0) of 2006-08-13"
>> i have the match-string-no-properties function. is this then an emacs
>> only function?
>>
>>
>
> XEmacs doesn't have that function, I solved it for the time being by adding
> the following snippet
XEmacs has this function in xml.el, from the net-utils package. It is
actually defined as an alias on match-string. I'm not sure why it's there...
maybe a better place would be directly in replace.el (or in fsf-compat, but do
we really want to have to load that ?).
--
Looking for a Christmas present idea? http://cdbaby.com/cd/didierverna
Didier Verna EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XFT-relevant ~/.xemacs/init.el snippet.
17 years, 4 months
Aidan Kehoe
Ar an séiú lá de mí na Nollaig, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > In order to match them to the charsets without paying extra-special
> > attention to what order they’re in and what other languages they might
> > happen to match.
>
> I don't understand. If you get order vs other languages they match
> wrong, you're going to get bad display anyway. That means that you
> can't do `(set-face-font 'lovely "My Preferred Font for Klingon-12"
> nil '(startrek-charset-tag) 'remove-tag-set-prepend)' with reliability
> anyway.
>
> Sure, in legacy Mule-coding XEmacs with your charset-tag kludge it
> works (I assume), but that needs to die with Unicode internal, right?
If we’re still using the ISO 2022 infrastructure for X11 redisplay, it would
seem reasonable to keep it there. For other platforms, it seems the defined
subsets that Unicode.org give (with perhaps some special treatment of the
Windows Glyph List, in acknowledgement that fonts will disproportionately
tend to support that) would be the best approach, and specifier tags for
them might be workable.
> And what do you do if someone wants different fonts for Spanish and
> Swedish? Assume that the Spaniards are so poor they don't have any
> Euros to write about, so assign ISO-8859-1 to Spanish and ISO-8859-15
> to Swedish?
Language tagging is not something we have, and not something we can easily
write, in either internal encoding model. Differentiating between Spanish
and Swedish _needs_ language tagging, since most text in both languages is
ASCII. Cf. the text of two newspaper articles:
http://www.aftonbladet.se/vss/nyheter/story/0,2789,948144,00.html:
=> ((chinese-gb2312 . 4) (latin-iso8859-1 . 114) (ascii . 2235))
http://www.elmundo.es/elmundo/2006/12/06/internacional/1165391686.html
=> ((latin-iso8859-1 . 57) (ascii . 3965))
Übrigens, yay, I appear to finally be a Lisp coder:
(defun charset-character-count-in-string (string)
"Return an alist mapping from the charsets in STRING to how often
characters from each appear. "
(let (alist)
(dolist (char (append string nil) alist)
(unless (assq (char-charset char) alist)
(setq alist (cons (cons (char-charset char) 0) alist)))
(incf (cdr (assq (char-charset char) alist))))))
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XEmacs crash on startup
17 years, 4 months
Stephen J. Turnbull
sandor kovacs writes:
> I suspect this is also not an xemacs problem, but here is the error anyway:
>
> $ xemacs
> Warning: Missing charsets in String to FontSet conversion
Thanks for the followup.
This is actually an XEmacs problem in the sense that we've been lazy,
and allow XEmacs to expect you to have fonts for all the character
sets that XEmacs can use. But why should you install fonts you never
use?
The condition is harmless (except for cluttering your screen with the
warning), and would require fiddling with the X error handlers which
is easy to get wrong, so it's never been fixed. (Or something like
that.:-)
Thanks again for your help!
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XFT-relevant ~/.xemacs/init.el snippet.
17 years, 4 months
Aidan Kehoe
Ar an cúigiú lá de mí na Nollaig, scríobh Stephen J. Turnbull:
> > Hmm? These aren’t native fontconfig facilities?
>
> Sure, but what's the define-specifier-tag stuff for?
In order to match them to the charsets without paying extra-special
attention to what order they’re in and what other languages they might
happen to match.
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Debugging 64bit xemacs (beta, latest cvs) on sparc64 (Sun T1000)
17 years, 4 months
Andrew Walrond
Hello list,
I have a nice little pure 64bit distro running on a sun T1 (niagra) box.
Everything builds and runs fine, except xemacs, which crashes every
30secs or so.
Using exact same distro and xemacs build running pure 64bit on x86_64
boxes does _not_ show the same problems, so this is likely something
sparc64 specific.
Anyhow, to diagnose the problem I have downloaded (cvs) and built the
latest beta version and installed the sumo tarball.
I enabled core dumps, loaded up some kernel sources into xemacs and
started playing around, splitting windows and scrolling about. Sure
enough, I soon got a segfault, and here is the backtrace:
$ gdb /bin/xemacs /tmp/core
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "sparc64-unknown-linux-gnu"...Using host
libthread_db library "/pkg/glibc/lib/libthread_db.so.1".
Reading symbols from /pkg/berkeleydb/lib/libdb-4.5.so...done.
Loaded symbols for /pkg/berkeleydb/lib/libdb-4.5.so
Reading symbols from /pkg/ncurses/lib/libncurses.so.5...done.
Loaded symbols for /pkg/ncurses/lib/libncurses.so.5
Reading symbols from /pkg/glibc/lib/libm.so.6...done.
Loaded symbols for /pkg/glibc/lib/libm.so.6
Reading symbols from /pkg/glibc/lib/libdl.so.2...done.
Loaded symbols for /pkg/glibc/lib/libdl.so.2
Reading symbols from /pkg/glibc/lib/libutil.so.1...done.
Loaded symbols for /pkg/glibc/lib/libutil.so.1
Reading symbols from /pkg/glibc/lib/libc.so.6...done.
Loaded symbols for /pkg/glibc/lib/libc.so.6
Reading symbols from /pkg/glibc/lib/libpthread.so.0...done.
Loaded symbols for /pkg/glibc/lib/libpthread.so.0
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib64/ld-linux.so.2
Reading symbols from /pkg/glibc/lib/libnss_files.so.2...done.
Loaded symbols for /pkg/glibc/lib/libnss_files.so.2
Core was generated by `xemacs kernel/lockdep_internals.h'.
Program terminated with signal 11, Segmentation fault.
#0 0xfffff80100575548 in kill () from /pkg/glibc/lib/libc.so.6
(gdb) where
#0 0xfffff80100575548 in kill () from /pkg/glibc/lib/libc.so.6
#1 0x00000000001ab280 in fatal_error_signal (sig=11) at emacs.c:3800
#2 <signal handler called>
#3 0xfffff801005beffc in memcpy () from /pkg/glibc/lib/libc.so.6
#4 0x00000000002c4368 in Lstream_write_1 (lstr=0xc73280,
data=0x7feff769660, size=34) at lstream.c:555
#5 0x00000000002c4474 in Lstream_write (lstr=0xc73280,
data=0x7feff769660, size=34) at lstream.c:602
#6 0x00000000002d4958 in output_string (function=13054592,
nonreloc=0x0, reloc=6773424, offset=0, len=34) at print.c:442
#7 0x00000000002db654 in print_string (obj=6773424,
printcharfun=13054592, escapeflag=0) at print.c:1403
#8 0x00000000002dc600 in print_internal (obj=6773424,
printcharfun=13054592, escapeflag=0) at print.c:1761
#9 0x00000000002d6a78 in print_error_message (error_object=14321584,
stream=13054592) at print.c:1005
#10 0x00000000002d6e20 in Fdisplay_error (error_object=14321584,
stream=5514648) at print.c:1070
#11 0x00000000001ba458 in Ffuncall (nargs=3, args=0x7feff769e38) at
eval.c:3893
#12 0x000000000015bcc8 in execute_optimized_program (
program=0xf0cfa0 "�\033�\032\r�\034�\021�\211\020\026\035�\026\036
\016\037�\004� \210� \210\r\026 ��!\210��\f�a�\037�\rA＠!�\025�\rA＠GU�\r�
\rA＠�H!�\004Ъ\035Ѫ\032\f�a�\004Ҫ\022\f�s�\004Ԫ\n\f�a�\004֪\002�\"\210�
\r�\"\210� �\v��\016!\"\210��!\210+�\207", stack_depth=6,
constants_data=0x5f8198) at bytecode.c:862
#13 0x00000000001b9ce4 in funcall_compiled_function (fun=7183920,
nargs=1, args=0x7feff76a548) at eval.c:3495
#14 0x00000000001ba954 in Ffuncall (nargs=2, args=0x7feff76a540) at
eval.c:3932
#15 0x00000000001bcb6c in call1 (fn=5130984, arg0=14321584) at
eval.c:4545
#16 0x000000000016e958 in cmd_error (data=14321584,
unused_dummy=5516376) at cmdloop.c:212
#17 0x00000000001b3b84 in condition_case_1 (handlers=5511624,
bfun=0x16efb0 <command_loop_1>, barg=5516376, hfun=0x16e8d4 <cmd_error>,
harg=5516376) at eval.c:1908
#18 0x000000000016ead8 in command_loop_3 () at cmdloop.c:262
#19 0x000000000016eb0c in command_loop_2 (unused_dummy=5516376) at
cmdloop.c:275
#20 0x00000000001b33a8 in internal_catch (tag=5122200, func=0x16eafc
<command_loop_2>, arg=5516376, threw=0x0, thrown_tag=0x0,
backtrace_before_throw=0x0) at eval.c:1530
#21 0x000000000016ecc8 in initial_command_loop (load_me=5516376) at
cmdloop.c:313
#22 0x00000000001a9444 in xemacs_21_5_b27_sparc64_unknown_linux (argc=2,
argv=0x7feff76b5a8, unused_envp=0x0, restart=0) at emacs.c:2667
#23 0x00000000001aa5a0 in main (argc=2, argv=0x7feff76b5a8,
unused_envp=0x7feff76b5c0) at emacs.c:3111
(gdb)
You'll all understand that I _need_ xemacs to work ;) So any help in
nailing these problems will be much appreciated! I can test, and give
ssh access to the server if that would help.
Andrew Walrond
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XFT-relevant ~/.xemacs/init.el snippet.
17 years, 4 months
Aidan Kehoe
Ar an cúigiú lá de mí na Nollaig, scríobh Stephen J. Turnbull:
> > The Right Thing is to integrate something similar to the below in the
> > X11 startup code, but I won’t get to that for a while. In the
> > meantime, this makes non-ASCII a good more readable on XFT, IMO.
>
> Gaak. There's got to be a way to do this via native fontconfig facilities.
Hmm? These aren’t native fontconfig facilities?
[...]
(fc-name-unparse
(fc-font-match
(selected-device)
(fc-name-parse
(format "-%d:lang=%s" size tag-name))))
[...]
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XFT-relevant ~/.xemacs/init.el snippet.
17 years, 4 months
Aidan Kehoe
The Right Thing is to integrate something similar to the below in the X11
startup code, but I won’t get to that for a while. In the meantime, this
makes non-ASCII a good more readable on XFT, IMO.
(when (featurep 'xft)
(set-specifier
(face-font 'default)
(cons '(x)
(fc-name-unparse
(fc-font-match (selected-device)
(fc-name-parse "Monospace-11.5:lang=en")))))
(loop
for (tag-name regex size) in
'((zh-tw "^chinese-\\(big5\\|cns\\)" 18)
(zh "^chinese-" 18)
(ja "^\\(japanese\\|katakana\\)-" 18)
(ko "^korean-" 18)
(am "^ethiopic-" 18)
(vi "^vietnamese-" 14)
(el "^greek-" 12)
(ru "^cyrillic-" 12)
(hu "^latin-iso8859-2" 12)
(ar "^arabic-" 16))
do
(define-specifier-tag tag-name nil
(list 'lambda '(charset)
(list 'string-match regex
'(symbol-name (charset-name charset)))))
(set-face-font 'default
(fc-name-unparse
(fc-font-match
(selected-device)
(fc-name-parse
(format "-%d:lang=%s"
size tag-name))))
nil (list 'x tag-name) 'append)))
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Default newline on Windows
17 years, 4 months
Tony Freixas
I hope this is an easy question.
XEmacs appears to understand the different end-of-line conventions:
CR+LF on Windows, LF on Unix. When I open a file, it appears to examine
the first line to decide which convention to use. That's fine.
However, when I create a new file, it defaults to the Unix convention. I
would like it to default to the Windows convention, but haven't found
the magic incantation to do so. Can anyone help with this?
I'm using XEmacs 21.4.19.
--
Tony Freixas
Tiger Heron LLC
tony(a)tigerheron.com
http://www.tigerheron.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Archives coming back on line
17 years, 4 months
Stephen J. Turnbull
Good news!
At long last I've got the process of putting the mailing list archives
back online. The xemacs-beta archive for 2006 is now complete (ie,
January-August and October-current, September was a total loss). I
should have this going back to 2003 or so in a couple of days, and
will be starting on others. The spam that infested the archives will
be gone, I hope.
Please notify me <stephen(a)xemacs.org> or xemacs-services(a)xemacs.org if
you notice breakage in the archives, either remaining "spam"
(including vacation notices, virus blowback, and the like), or broken
threads that may be due to overaggressive spam filtering of the
archives.
In the interest of getting *something* online, I'm using the builtin
pipermail archiver that Mailman supplies. It's not great, but it
works. Caveats: the URLs generated are just sequence numbers. This
means that any changes to the archive will change them. I've been
discussing with the Mailman developers about some way to create true
URNs (probably based on the message-id), so don't depend on the URLs
being constant.
We don't have a search facility in place yet. The "wilma" engine that
we used before was a PITA to keep running; besides that (which is an
option), I'm looking at Xapian and Namazu. Hopefully Google will pick
our archives up pretty quickly though, so you'll at least have
"site:calypso.tux.org" to fall back on.
Still working on resurrecting lists.xemacs.org and
list-archive.xemacs.org, but we need to be careful about that as
Mailman is a little tricky to configure in a virtual domain.
Regards,
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs Packages have been pre-released (2006-12-01-22)
17 years, 4 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:
===========================
mule-base-1.49-pkg.tar.gz upstream version: none
Previously Announced Packages Still in Pre-Release:
==================================================
calendar-1.30-pkg.tar.gz upstream version: none
debug-1.18-pkg.tar.gz upstream version: none
edebug-1.22-pkg.tar.gz upstream version: none
ediff-1.66-pkg.tar.gz upstream version: 2.75
edit-utils-2.36-pkg.tar.gz upstream version: none
haskell-mode-1.10-pkg.tar.gz upstream version: 2.1
hyperbole-1.16-pkg.tar.gz upstream version: 4.18
ilisp-1.34-pkg.tar.gz upstream version: 5.12.0
latin-unity-1.19-pkg.tar.gz upstream version: 1.19
leim-1.24-pkg.tar.gz upstream version: none
locale-1.24-pkg.tar.gz upstream version: none
mail-lib-1.78-pkg.tar.gz upstream version: none
net-utils-1.49-pkg.tar.gz upstream version: N/A
ocaml-0.06-pkg.tar.gz upstream version: 3.06
os-utils-1.39-pkg.tar.gz upstream version: none
pcl-cvs-1.67-pkg.tar.gz upstream version: R-2_9_9
prog-modes-2.09-pkg.tar.gz upstream version: none
python-modes-1.08-pkg.tar.gz upstream version: none
text-modes-1.92-pkg.tar.gz upstream version: none
tramp-1.34-pkg.tar.gz upstream version: 2.0.54
vhdl-1.22-pkg.tar.gz upstream version: 3.33.12
viper-1.53-pkg.tar.gz upstream version: 3.09
w3-1.33-pkg.tar.gz upstream version: 4.0pre47
xemacs-base-2.08-pkg.tar.gz upstream version: none
xemacs-devel-1.75-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from mule-packages/mule-base/ChangeLog -------
2006-12-01 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.49 released.
2006-12-01 Aidan Kehoe <kehoea(a)parhasard.net>
* fsf-compat-unicode.el:
* fsf-compat-unicode.el (fsf-compat-ccl-encode-to-ucs-2): Removed.
* fsf-compat-unicode.el (eval-when-compile):
Pre-expand the macro if we're compiling on 21.4; fixes a packages
smoketest failure.
2006-11-29 Aidan Kehoe <kehoea(a)parhasard.net>
* Makefile (ELCS):
* fsf-compat-unicode.el:
Provide support for some FSF-specific Unicode-coverage Mule
charsets.
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.3 (GNU/Linux)
iD8DBQFFcKUlgu3ywdHdhM0RAowIAKDMZQeflSTwp2+hpjjEVN7bmaj9qwCfd73i
CeLzryqYu34I0GrfykSzfEQ=
=vy7g
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta