patch for antialiased text with Xrender/Xft
23 years, 11 months
Vladimir Vukicevic
Vladimir Vukicevic
[I'd sent this the first time a little bit ago to xemacs-patches,
before realizing that -beta might be a better location for it. So here
it is.]
Here's a patch against 21.1.12 that gives xemacs the ability to
take advantage of the XRender extension and use antialiased fonts for
display. A new configure flag, --enable-xrender, turns this on.
Fonts are specified using "XFT:font name:size". There are still a few
issues, but by and large it works. It also doesn't handle
non-proportional fonts gracefully (it does the maximum-width thing).
The patch is at
http://www.intrepid.com/~vladimir/xemacs21_aa.patch.gz .
Screenshot at http://www.intrepid.com/~vladimir/xemacs_aa.png
Xrender setup bits are at http://www.xfree86.org/~keithp/render/,
it's included in xfree86 CVS or the 4.0.1z release. (I /think/
the latest debian woody should do fine, but you may have to end up
rebuilding X so that you can define FREETYPE2.. it's not defined
in the debian X dist for yet :-P)
Try "xemacs -fn 'XFT:Lucida Console:24'" and drool ;-)
Things left to do:
- bug in clipping. lines which should be half-drawn will draw
over the modeline. this involves getting the right bits to
XftDrawSetClip.
- get rid of XFT:blah. this is a hack, as the fonts come from
a different namespace. However, the right way to do this would
be to parse the fontspec string with a family of -xft-...; this
would enable lisp code which modifies these strings (i.e. to make
bold/italic variants) work corrently.
- a color bug that I need to hunt down.
Let me know what you think!
(Please keep me in the Cc line of any responses, I'm not subscribed to
xemacs-beta.)
- Vlad
- 1 participants
- 0 comments
Re: [crash,xemacs_21_2_b36_i686_bittersweet_linux] Dumped core reloading byte-code
23 years, 11 months
Karl M. Hegbloom
Karl M. Hegbloom
>>>>> "Yoshiki" == Yoshiki Hayashi <yoshiki(a)xemacs.org> writes:
Yoshiki> karlheg(a)bittersweet.inetarena.com (Karl M. Hegbloom) writes:
>> I had just patched up the copy of dired that I am currently using
>> (with the patches I mailed earlier), and rebuilt it. I used `dired'
>> `L' to load the newly rebuilt "dired.elc", and it crashed and dumped
>> core. Do you need any more information? I will save the core file
>> and a copy of this binary.
Yoshiki> Can you reproduce it with 21.2.38? It looks like a GC bug.
I don't know. If it happens again, I'll submit a bug report.
--
mailto: Karl M. Hegbloom <karlheg(a)debian.org>
http://people.debian.org/~karlheg/
( <-- These are full-on slotskis. --> )
This is only a semi-colon --> ;
- 1 participants
- 0 comments
Email Problems
23 years, 11 months
Steve Youngs
Steve Youngs
Hey Everyone
I'm experiencing some huge problems with my current ISP. I'm in the
process of finding a better one to switch to. But in the meantime I
may be a little hard to get a hold of. Probably for about a week - 10
days.
--
|---<Regards, Steve Youngs>-----------[GnuPG KeyID: 59E4C4B2]---|
| XEmacs - It's not just an editor... |
| It's a way of life. |
|----------------------------------<mailto:youngs＠xemacs.org>---|
- 1 participants
- 0 comments
[crash,xemacs_21_2_b36_i686_bittersweet_linux] Dumped core reloading byte-code
23 years, 11 months
Karl M. Hegbloom
Karl M. Hegbloom
I had just patched up the copy of dired that I am currently using
(with the patches I mailed earlier), and rebuilt it. I used `dired'
`L' to load the newly rebuilt "dired.elc", and it crashed and dumped
core. Do you need any more information? I will save the core file
and a copy of this binary.
Fatal error (11).
Your files have been auto-saved.
[... standard crash blurb elided, of course ...]
Lisp backtrace follows:
# bind (print-message-label)
display-error((wrong-type-argument stringp
[ It just ends right there. ]
bittersweet% gdb xemacs core
GNU gdb 5.0
Copyright 2000 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 "i686-pc-linux-gnu"...
Core was generated by `xemacs -unmapped -f gnuserv-start'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/X11R6/lib/libXaw3d.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXaw3d.so.6
Reading symbols from /usr/lib/libtiff.so.3...done.
Loaded symbols for /usr/lib/libtiff.so.3
Reading symbols from /usr/lib/libpng.so.2...done.
Loaded symbols for /usr/lib/libpng.so.2
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /usr/lib/libcompface.so.1...done.
Loaded symbols for /usr/lib/libcompface.so.1
Reading symbols from /usr/X11R6/lib/libXpm.so.4...done.
Loaded symbols for /usr/X11R6/lib/libXpm.so.4
Reading symbols from /usr/X11R6/lib/libXmu.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXmu.so.6
Reading symbols from /usr/X11R6/lib/libXt.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXt.so.6
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Loaded symbols for /usr/X11R6/lib/libXext.so.6
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Loaded symbols for /usr/X11R6/lib/libX11.so.6
Reading symbols from /usr/X11R6/lib/libSM.so.6...done.
Loaded symbols for /usr/X11R6/lib/libSM.so.6
Reading symbols from /usr/X11R6/lib/libICE.so.6...done.
Loaded symbols for /usr/X11R6/lib/libICE.so.6
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/libgpm.so.1...done.
Loaded symbols for /usr/lib/libgpm.so.1
Reading symbols from /lib/libncurses.so.5...done.
Loaded symbols for /lib/libncurses.so.5
Reading symbols from /usr/lib/libesd.so.0...done.
Loaded symbols for /usr/lib/libesd.so.0
Reading symbols from /usr/lib/libaudiofile.so.0...done.
Loaded symbols for /usr/lib/libaudiofile.so.0
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /usr/lib/libpq.so.2.1...done.
Loaded symbols for /usr/lib/libpq.so.2.1
Reading symbols from /usr/lib/libldap.so.2...done.
Loaded symbols for /usr/lib/libldap.so.2
Reading symbols from /lib/libutil.so.1...done.
Loaded symbols for /lib/libutil.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /usr/lib/libdb2.so.2...done.
Loaded symbols for /usr/lib/libdb2.so.2
Reading symbols from /lib/libcrypt.so.1...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /usr/lib/liblber.so.2...done.
Loaded symbols for /usr/lib/liblber.so.2
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /usr/lib/libsasl.so.7...done.
Loaded symbols for /usr/lib/libsasl.so.7
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libpam.so.0...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_dns.so.2...done.
Loaded symbols for /lib/libnss_dns.so.2
Reading symbols from /lib/libnss_compat.so.2...done.
Loaded symbols for /lib/libnss_compat.so.2
#0 0x81808cb in print_internal (obj=141644532, printcharfun=137421732,
escapeflag=1)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/print.c:1339
warning: Source file is more recent than executable.
(gdb) where full
#0 0x81808cb in print_internal (obj=141644532, printcharfun=137421732,
escapeflag=1)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/print.c:1339
gcpro1 = {next = 0xbfffeb44, var = 0xbfffeb14, nvars = 1}
gcpro2 = {next = 0xbfffeabc, var = 0xbfffeb18, nvars = 1}
#1 0x818018c in print_cons (obj=148375320, printcharfun=137421732,
escapeflag=1)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/print.c:1075
len = 2
max = 2147483647
tortoise = 148375344
gcpro1 = {next = 0xbfffec50, var = 0xbfffeb64, nvars = 1}
gcpro2 = {next = 0xbfffeb50, var = 0xbfffeb68, nvars = 1}
#2 0x81808e2 in print_internal (obj=148375440, printcharfun=137421732,
escapeflag=1)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/print.c:1340
gcpro1 = {next = 0xbfffece4, var = 0xbfffecb4, nvars = 1}
gcpro2 = {next = 0xbfffec5c, var = 0xbfffecb8, nvars = 1}
#3 0x8181e04 in Fprin1 (object=148375440, stream=137421732)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/print.c:637
frame = 137274900
gcpro1 = {next = 0xbfffed64, var = 0xbfffed04, nvars = 1}
gcpro2 = {next = 0xbfffecf0, var = 0xbfffed08, nvars = 1}
#4 0x80c22b7 in Fbacktrace (stream=137421732, detailed=137274924)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/eval.c:5217
i = 0
tem = 137421516
backlist = (struct backtrace *) 0xbffff32c
catches = (struct catchtag *) 0xbffff64c
speccount = 5
old_nl = 0
old_pr = 0
old_level = 137274900
oiq = 137274924
gcpro1 = {next = 0xbffff1e8, var = 0xbfffed84, nvars = 1}
gcpro2 = {next = 0xbfffed70, var = 0xbfffed54, nvars = 1}
#5 0x80b5c31 in fatal_error_signal (sig=11)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/emacs.c:514
No locals.
#6 0x4037cf38 in sigaction () from /lib/libc.so.6
No symbol table info available.
#7 0x817f6dc in print_error_message (error_object=148375440, stream=137584280)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/print.c:787
first = -1073745340
speccount = 5
frame = 141948984
gcpro1 = {next = 0xbffff3a8, var = 0xbffff2a0, nvars = 1}
type = 1
method = 137274900
tail = -1073745668
#8 0x8181d94 in Fdisplay_error (error_object=148375440, stream=137274924)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/print.c:842
No locals.
#9 0x80bee6a in Ffuncall (nargs=3, args=0xbffff360)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/eval.c:3528
PF_fn = (void (*)()) 0
max_args = -1073747176
spacious_args = {137274900, 137350876, 137274900, 136035563,
137498108, 136672148, 137274900, 137439412}
fun = 136858920
val = -1073745052
backtrace = {next = 0xbffff47c, function = 0xbffff360,
args = 0xbffff364, nargs = 2, pdlcount = 5, evalargs = 0 '\000',
debug_on_exit = 0 '\000'}
fun_nargs = 2
fun_args = (Lisp_Object *) 0xbffff364
#10 0x8093b6e in execute_optimized_program (
program=0x885e008 "\013\032Æ\031Ç\e\r¢\034Ç\020Æ\211\026 \026!Ç\026\"\016#«\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Ù «\031\n«\fÊÚ!\210Û \210ÊÜ!\210ÊÝ\016%\"\210Þß!\210,Æ\207", stack_depth=2,
constants_data=0x83b0cb8)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/bytecode.c:746
n = 2
opcode = 34
program_ptr = (
Opbyte *) 0x885e071 "\210Ù «\031\n«\fÊÚ!\210Û \210ÊÜ!\210ÊÝ\016%\"\210Þß!\210,Æ\207"
stack_ptr = (Lisp_Object *) 0xbffff360
speccount = 1
gcpro1 = {next = 0xbffff4c8, var = 0xbffff360, nvars = 6}
stack_beg = (Lisp_Object *) 0xbffff35c
stack_end = (Lisp_Object *) 0xbffff374
#11 0x8093783 in funcall_compiled_function (fun=138053392, nargs=1,
args=0xbffff4c4)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/bytecode.c:518
value = 137274900
speccount = 0
i = 1
optional = 0
#12 0x80bf00f in Ffuncall (nargs=2, args=0xbffff4c0)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/eval.c:3563
fun = 138053392
val = -1073744700
backtrace = {next = 0x0, function = 0xbffff4c0, args = 0xbffff4c4,
nargs = 1, pdlcount = 0, evalargs = 0 '\000', debug_on_exit = 0 '\000'}
fun_nargs = 1
fun_args = (Lisp_Object *) 0xbffff4c4
#13 0x80c45c2 in call1 (fn=0, arg0=-1073747176)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/eval.c:4183
ret_ungc_val = 141644532
gcpro1 = {next = 0x0, var = 0xbffff4c0, nvars = 2}
args = {137350876, 148375440}
#14 0x809df9a in cmd_error (data=148375440, dummy=137274900)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/cmdloop.c:195
No locals.
#15 0x80c5060 in condition_case_1 (handlers=137274996,
bfun=0x809dea4 <command_loop_1>, barg=137274900,
hfun=0x809df54 <cmd_error>, harg=137274900)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/eval.c:1634
speccount = 0
c = {tag = 150117188, val = 148375440, next = 0xbffff64c, gcpro = 0x0,
jmp = {{__jmpbuf = {137274900, -1073744036, -1073743812, -1073744396,
-1073744644, 135024712}, __mask_was_saved = 0, __saved_mask = {
__val = {134639649, 139397928, 3221222956, 3221222804, 134869544,
139518048, 3221223260, 0, 0, 137274900, 149891272, 3221222836,
134911546, 137274900, 1, 3221222868, 135049911, 149891272, 0,
3221222884, 135483794, 139518048, 3221223260, 1073833876,
1078779072, 139518048, 3221223260, 3221222916, 135273349, 149891272,
1073792046, 3221222916}}}}, backlist = 0x0, lisp_eval_depth = 0,
pdlcount = 0}
gcpro1 = {next = 0x0, var = 0xbffff60c, nvars = 1}
#16 0x809e047 in command_loop_2 (dummy=137274900)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/cmdloop.c:256
No locals.
#17 0x80c4f8c in internal_catch (tag=141644532,
func=0x809e00c <command_loop_2>, arg=137274900, threw=0x0)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/eval.c:1317
c = {tag = 137350924, val = 137274900, next = 0x0, gcpro = 0x0, jmp = {
{__jmpbuf = {137274900, -1073744036, -1073743812, -1073744124,
-1073744340, 135024487}, __mask_was_saved = 0, __saved_mask = {
__val = {3221223260, 3221223260, 3221223260, 3221223260, 3221223277,
3288332123, 3221223260, 3288332123, 0, 0, 0, 0, 0, 137846676, 16,
139416564, 134217728, 3221223004, 12, 3221223156, 134759786,
137846676, 4294967295, 3221223172, 134759786, 3221223212,
1073792217, 1073833876, 1078779072, 7, 0, 3221223204}}}},
backlist = 0x0, lisp_eval_depth = 0, pdlcount = 0}
#18 0x809d488 in initial_command_loop (load_me=0)
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/cmdloop.c:305
No locals.
#19 0x80b6c3e in xemacs_21_2_b36_i686_bittersweet_linux ()
at /usr/local/src/PKG/woody/main/xemacs/xemacs/src/emacs.c:2228
(gdb) x/16 141644532
0x87152f4: 0xffffffff 0xf78eaceb 0xdeadbeef 0xdeadbeef
0x8715304: 0x00000008 0x00000033 0x087d18b0 0x082ea614
0x8715314: 0xffffffff 0xf78eac7b 0xdeadbeef 0xdeadbeef
0x8715324: 0x00000008 0x00000011 0x08742af0 0x082ea614
--
mailto: Karl M. Hegbloom <karlheg(a)debian.org>
http://people.debian.org/~karlheg/
- 3 participants
- 2 comments
Improve Common Lisp Support
23 years, 11 months
Craig Lanning
Craig Lanning
This patch is intended to move lisp-mode toward better conformance
with Common Lisp. To this end:
o It removes case sensitivity in the highlighting code
o Adds some commonly used CL forms to the highlighting lists
o Adds indention specs for commonly used CL forms
Please note that I do not know what dependencies modes other than
emacs-lisp-mode may have on lisp-mode. It may turn out that it would be
better to implement my changes by creating a new common-lisp-mode and
have the .lisp and .lsp extensions select that mode instead of lisp-mode.
Craig
----------------------------------------------------------------------
2000-12-07 Craig Lanning <lanning(a)scra.org>
* font-lock.el: Support Common Lisp better
* font-lock.el (lisp-mode): Make case insensitive per Common Lisp
* font-lock.el (emacs-lisp-mode): Separate from lisp-mode so that
it can maintain its case sensitivity
* font-lock.el (lisp-font-lock-keywords-1): Support things like
cl:defvar or foo::define-object
* font-lock.el (lisp-font-lock-keywords-2):
Add with-open-file, with-open-stream, with-slots, handler-bind,
and handler-case to set of highlighted keywords
Add &body and &key to list of lambda list keywords
* lisp-mode.el (handler-case): Specify indention
* lisp-mode.el (handler-bind): ..
* lisp-mode.el (with-output-to-string): Change indention
* lisp-mode.el (with-slots): Specify indention
* lisp-mode.el (with-open-file): ..
* lisp-mode.el (with-open-stream): ..
* lisp-mode.el (print-unreadable-object): ..
----------------------------------------------------------------------
cvs server: Diffing lisp
Index: lisp/font-lock.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/font-lock.el,v
retrieving revision 1.7.2.26
diff -u -r1.7.2.26 font-lock.el
--- font-lock.el 2000/11/02 15:15:06 1.7.2.26
+++ font-lock.el 2000/12/07 13:11:50
＠＠ -1817,14 +1817,22 ＠＠
(put 'lisp-mode 'font-lock-defaults
'((lisp-font-lock-keywords
lisp-font-lock-keywords-1 lisp-font-lock-keywords-2)
- nil nil
+ nil t
((?: . "w") (?- . "w") (?* . "w") (?+ . "w") (?. . "w") (?< . "w")
(?> . "w") (?= . "w") (?! . "w") (?? . "w") (?$ . "w") (?% . "w")
(?_ . "w") (?& . "w") (?~ . "w") (?^ . "w") (?/ . "w"))
beginning-of-defun))
-(put 'emacs-lisp-mode 'font-lock-defaults 'lisp-mode)
(put 'lisp-interaction-mode 'font-lock-defaults 'lisp-mode)
+(put 'emacs-lisp-mode 'font-lock-defaults
+ '((lisp-font-lock-keywords
+ lisp-font-lock-keywords-1 lisp-font-lock-keywords-2)
+ nil nil
+ ((?: . "w") (?- . "w") (?* . "w") (?+ . "w") (?. . "w") (?< . "w")
+ (?> . "w") (?= . "w") (?! . "w") (?? . "w") (?$ . "w") (?% . "w")
+ (?_ . "w") (?& . "w") (?~ . "w") (?^ . "w") (?/ . "w"))
+ beginning-of-defun))
+
(put 'scheme-mode 'font-lock-defaults
'(scheme-font-lock-keywords
nil t
＠＠ -1864,7 +1872,7 ＠＠
;; Anything not a variable or type declaration is fontified as a function.
;; It would be cleaner to allow preceding whitespace, but it would also be
;; about five times slower.
- (list (concat "^(\\(def\\("
+ (list (concat "^(\\(\\(\\sw+::?\\)?def\\("
;; Variable declarations.
"\\(const\\(\\|ant\\)\\|ine-key\\(\\|-after\\)\\|var\\|custom\\)\\|"
;; Structure declarations.
＠＠ -1876,8 +1884,8 ＠＠
"[ \t'\(]*"
"\\([^ \t\n\)]+\\)?")
'(1 font-lock-keyword-face)
- '(8 (cond ((match-beginning 3) 'font-lock-variable-name-face)
- ((match-beginning 6) 'font-lock-type-face)
+ '(9 (cond ((match-beginning 4) 'font-lock-variable-name-face)
+ ((match-beginning 7) 'font-lock-type-face)
(t 'font-lock-function-name-face))
nil t))
)
＠＠ -1902,10 +1910,11 ＠＠
;; "save-current-buffer" "with-current-buffer"
;; "save-selected-window" "with-selected-window"
;; "save-selected-frame" "with-selected-frame"
+ ;; "with-open-file" "with-open-stream"
;; "with-temp-file" "with-temp-buffer" "with-output-to-string"
- ;; "with-string-as-buffer-contents"
+ ;; "with-string-as-buffer-contents" "with-slots"
;; "save-match-data" "unwind-protect" "call-with-condition-handler"
- ;; "condition-case" "track-mouse" "autoload"
+ ;; "handler-bind" "handler-case" "condition-case" "track-mouse" "autoload"
;; "eval-after-load" "eval-and-compile" "eval-when-compile"
;; "when" "unless" "do" "dolist" "dotimes" "flet" "labels"
;; "lambda" "block" "return" "return-from" "loop") t)
＠＠ -1914,12 +1923,13 ＠＠
"autoload\\|block\\|c\\(?:a\\(?:ll-with-condition-handler\\|tch\\)\\|"
"ond\\(?:ition-case\\)?\\)\\|do\\(?:list\\|times\\)?\\|"
"eval-\\(?:a\\(?:fter-load\\|nd-compile\\)\\|when-compile\\)\\|flet\\|"
- "if\\|l\\(?:a\\(?:bels\\|mbda\\)\\|et\\*?\\|oop\\)\\|prog[12nv]?\\|"
- "return\\(?:-from\\)?\\|save-\\(?:current-buffer\\|excursion\\|"
- "match-data\\|restriction\\|selected-\\(?:frame\\|window\\)\\|"
- "window-excursion\\)\\|t\\(?:hrow\\|rack-mouse\\)\\|un\\(?:less\\|"
- "wind-protect\\)\\|w\\(?:h\\(?:en\\|ile\\)\\|ith-\\(?:current-buffer\\|"
- "output-to-string\\|s\\(?:elected-\\(?:frame\\|window\\)\\|"
+ "handler-\\(?:bind\\|case\\)\\|if\\|l\\(?:a\\(?:bels\\|mbda\\)\\|"
+ "et\\*?\\|oop\\)\\|prog[12nv]?\\|return\\(?:-from\\)?\\|"
+ "save-\\(?:current-buffer\\|excursion\\|match-data\\|restriction\\|"
+ "selected-\\(?:frame\\|window\\)\\|window-excursion\\)\\|t\\(?:hrow\\|"
+ "rack-mouse\\)\\|un\\(?:less\\|wind-protect\\)\\|w\\(?:h\\(?:en\\|"
+ "ile\\)\\|ith-\\(?:current-buffer\\|o\\(?:pen-\\(?:file\\|stream\\)\\|"
+ "utput-to-string\\)\\|s\\(?:elected-\\(?:frame\\|window\\)\\|lots\\|"
"tring-as-buffer-contents\\)\\|temp-\\(?:buffer\\|file\\)\\)\\)"
;; end of generated stuff
"\\)\\>") 1)
＠＠ -1938,7 +1948,7 ＠＠
'("\\<:\\sw+\\>" 0 font-lock-reference-face prepend)
;;
;; ELisp and CLisp `&' keywords as types.
- '("\\<\\&\\(optional\\|rest\\|whole\\)\\>" . font-lock-type-face)
+ '("\\<\\&\\(body\\|key\\|optional\\|rest\\|whole\\)\\>" . font-lock-type-face)
))
"Gaudy level highlighting for Lisp modes.")
Index: lisp/lisp-mode.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/lisp-mode.el,v
retrieving revision 1.10.2.7
diff -u -r1.10.2.7 lisp-mode.el
--- lisp-mode.el 2000/11/23 06:27:36 1.10.2.7
+++ lisp-mode.el 2000/12/07 13:11:51
＠＠ -802,6 +802,8 ＠＠
(put 'if 'lisp-indent-function 2)
(put 'catch 'lisp-indent-function 1)
(put 'condition-case 'lisp-indent-function 2)
+(put 'handler-case 'lisp-indent-function 1)
+(put 'handler-bind 'lisp-indent-function 1)
(put 'call-with-condition-handler 'lisp-indent-function 2)
(put 'unwind-protect 'lisp-indent-function 1)
(put 'save-current-buffer 'lisp-indent-function 0)
＠＠ -809,14 +811,18 ＠＠
(put 'with-string-as-buffer-contents 'lisp-indent-function 1)
(put 'with-temp-file 'lisp-indent-function 1)
(put 'with-temp-buffer 'lisp-indent-function 0)
-(put 'with-output-to-string 'lisp-indent-function 0)
+(put 'with-output-to-string 'lisp-indent-function 1)
(put 'with-output-to-temp-buffer 'lisp-indent-function 1)
+(put 'with-slots 'lisp-indent-function 2)
+(put 'with-open-file 'lisp-indent-function 1)
+(put 'with-open-stream 'lisp-indent-function 1)
(put 'eval-after-load 'lisp-indent-function 1)
(put 'display-message 'lisp-indent-function 1)
(put 'display-warning 'lisp-indent-function 1)
(put 'lmessage 'lisp-indent-function 2)
(put 'lwarn 'lisp-indent-function 2)
(put 'global-set-key 'lisp-indent-function 1)
+(put 'print-unreadable-object 'lisp-indent-function 1)
(defun indent-sexp (&optional endpos)
"Indent each line of the list starting just after point.
cvs server: Diffing lisp/mule
cvs server: Diffing lisp/term
- 2 participants
- 1 comments
Anybody Home? Test Ignore
23 years, 11 months
Steven T. Hatton
Steven T. Hatton
I did not receive a confirmation from marjordomo
--
Populi Romani imperium Rhenum finire.
-- Sugambri message to Caesar
- 1 participants
- 0 comments
External modules
23 years, 11 months
Jerry James
Jerry James
It appears that the consensus from the discussion following my earlier
modules question was that:
a) I should do my own autoconf magic (which, as somebody mentioned,
wasn't all that hard); and
b) I should structure my module so that it can be compiled outside of
the XEmacs source tree (i.e., make it an external module).
For the information of whoever is responsible for modules (I don't see
anyone listed on <URL:http://xemacs.sourceforge.net/Develop/jobs.html>),
here are the obstacles I have encountered so far in accomplishing (b),
working with the XEmacs 21.2.37 distribution:
1) Missing header files.
a) emodules.h is not installed anywhere when XEmacs is installed,
so I can't very well include it.
b) A bunch of other header files, needed by emodules.h, are also
not installed. These include lisp.h, sysdep.h, window.h,
buffer.h, etc.
Incidentally, speaking of installed header files, why are the
entire s&m directories installed in
.../lib/xemacs-21.2-b37/config-name/include? It's a
machine-specific directory, so why do I want header files for every
machine under the sun?
2) Lack of examples.
a) The examples in the modules directory of the XEmacs distribution
are all of internal modules. That is, they only build inside
the XEmacs source tree. And even then, they aren't right. They
only build inside the source tree *if you built XEmacs itself
inside the source tree*. If you, like me, build XEmacs for
multiple platforms, and therefore use VPATH to build outside of
the source tree, the modules won't build at all, due to
assumptions about the location of ellcc and make-docfile.
b) The example Makefiles (and, strangely, not the README in the
modules directory) all refer to "samples in the sub-directory
'installed'" to show how to write modules to be compiled outside
of the XEmacs source tree. That subdirectory is not part of the
XEmacs 21.2.37 distribution, the comments are in the wrong
place, and I doubt that such examples even exist due to problem
#1.
I am willing to be a guinea pig to help get external modules working,
but I need some direction from the list and whoever is coordinating
module development.
Regards,
--
Jerry James
- 3 participants
- 8 comments
Re: Modules and configure
23 years, 11 months
William M. Perry
William M. Perry
Martin Buchholz <martin(a)xemacs.org> writes:
> >>>>> "WMP" == William M Perry <wmperry(a)aventail.com> writes:
>
> WMP> For actual OS things that they would need to check for that XEmacs'
> WMP> config.h doesn't take care of... I can't see many other than AC_CHECK_LIB
> WMP> and testing for module-specific includes. But creating the makefiles, etc,
> WMP> etc, is definitely best left to the modules themselves.
>
> WMP> I've been meaning for well over a year to make the package system use
> WMP> autoconf, but have never found the time. :(
>
> Time....
>
> One idea is that the module needs an XEmacs, and XEmacs already knows
> _everything_ about the system.
I argue that this is a false statement. XEmacs _cannot_ know everything
about the system. Just say that we broke LDAP out into a separately
distributed module. Why should the core XEmacs have a configure-time test
for all the oddities of the different LDAP implementations? Or why should
it check for the existence of 'libghttp' just on the off chance that
someone will write a module that uses it?
XEmacs knows everything for the lispy side of things, but a module is not
going to be really worthwhile unless it interfaces with something XEmacs
doesn't know about yet (otherwise, why write it in C unless speed is
killing you?)
> And its configuration variables are available from lisp via
> config-value-hash-table.
Emacs/W3 used to take advantage of this, and actually uses the same type of
thing in w3-cfg.el, but it still cannot give you everything. There needs
to be a mixture.
-bp
- 1 participants
- 0 comments
Re: Something is changed with file-attributes?!
23 years, 11 months
Adrian Aichner
Adrian Aichner
>>>>> "Konstantin" == Konstantin Malakhanov <km(a)isoware.de> writes:
This problem is still present in
"XEmacs 21.2 (beta38) \"Peisino,Ak(B\" [Lucid] (i586-pc-win32) of
Fri Dec 08 2000 on ZJ75T"
test cases:
(file-attributes "d:\\Users\\AichnerAd\\")
nil
(file-attributes "d:\\Users\\AichnerAd")
(t 1 0 0 (14896 50939) (14896 50863) (14564 37795) 0 "drwxrwxrwx" nil 0 3)
(file-attributes "d:/Users/AichnerAd/")
nil
(file-attributes "d:/Users/AichnerAd")
(t 1 0 0 (14896 50939) (14896 50863) (14564 37795) 0 "drwxrwxrwx" nil 0 3)
It keeps me from using Gnus and therefor from testing 21.2 betas very
much.
Is anybody interested in fixing this together with me?
Best regards,
Adrian
Konstantin> I use precompiled XEmacs version
Konstantin> XEmacs 21.2 (beta35) "Nike" [Lucid] (i586-pc-win32) of Fri Sep 08
Konstantin> 2000 on NEVERYON
Konstantin> The defun file-attributes doesn't work with directory names ending
Konstantin> with double backslash, i.e:
Konstantin> (file-attributes "c:\\programme\\")
Konstantin> nil
Konstantin> (file-attributes "c:\\programme")
Konstantin> (t 1 0 0 (14785 4701) (14785 4701) (14488 58112) 0 "drwxrwxrwx" nil 0 2)
Konstantin> or, open any file not directly under drive (with directory in path)
Konstantin> and evaluate in buffer:
Konstantin> (file-attributes default-directory)
Konstantin> It gives nil too.
Konstantin> It works both way with drive-only paths:
Konstantin> (file-attributes "c:\\")
Konstantin> (t 1 0 0 (4814 38896) (4814 38896) (4814 38896) 0 "drwxrwxrwx" nil 0 2)
Konstantin> (file-attributes "c:")
Konstantin> (t 1 0 0 (4814 38896) (4814 38896) (4814 38896) 0 "drwxrwxrwx" nil 0 2)
Konstantin> Bug or feature?! Workarounds?
Konstantin> TIA.
Konstantin> --
Konstantin> Konstantin Malakhanov
Konstantin> ISOWARE GmbH, Feithstr. 142, 58097 Hagen, Germany
Konstantin> email: km(a)isoware.de Tel: 02331/8019-67 FAX: 02331/8019-99
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
- 1 participants
- 0 comments
[info.el] top line splitting under MULE
23 years, 11 months
Tetsuo Tsukamoto
Tetsuo Tsukamoto
In function `Info-fontify-region', top line is split into multiple
lines if it is very long.
The code is not good for MULE, since it confuses columns and
characters. The problem appears when we read skk.info.
When a page with long top line is displayed for the first time, it
seems OK. Go to next node ([space] twice) and get back ([BS] twice).
This time one more new line is inserted at the point where the split
occurred.
(Anyway, this feature doesn't seem very important to me. Simply
disabling it under MULE may not be a bad idea.)
--
Tetsuo Tsukamoto
<czkmt(a)remus.dti.ne.jp>
- 1 participants
- 0 comments