XEmacs 21.5 (beta28) "fuki" (+CVS-20071205) [Lucid] (i386-apple-
darwin9.1.0, Mule) of Wed Jan 2 2008
In a terminal:
/Applications/XEmacs.app/Contents/MacOS/XEmacs -nw -q
C-x 2 C-x 2 ; 3 windows, of 4, 5, and 11 lines respectively
M-x
C-g ; 3 windows, of 4, 7, and 9 lines respectively
M-x
C-g ; 3 windows, of 4, 13, and 3 lines respectively
This happens in either terminal-mode or Cocoa windowed mode.
It does not happen with an X11 build of 21.4.20.
Other than that, I don't know whether this is a general xemacs
regression, or related to the Cocoa code.
--
Jamie Zawinski jwz(a)jwz.org http://www.jwz.org/
jwz(a)dnalounge.com http://www.dnalounge.com/http://jwz.livejournal.com/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
FKtPp writes:
> well, the problem is coding-system-p in XEmacs always return nil when
> invoked using the form of:
>
> (coding-system-p 'us-ascii)
> (coding-system-p 'cn-gb-2312)
That's correct; those are symbols. If you have a symbol naming a
coding system, you have to get the corresponding coding system first
using (get-coding-system name). But you won't get anywhere with
us-ascii, because it isn't a coding system. For ASCII use the coding
system `iso-8859-1'.
But why do you need to check whether something is a coding system or
not? Application code shouldn't be doing that.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
At long last the XEmacs Project enters the 21st century with a modern
issue tracker of its own.
It's based on the Roundup tracker designed by Ka-Ping Yee and
implemented by Richard Jones, with a few pieces (and probably more to
come) borrowed from the Python issue tracker.
It's been primed with about 125 XEmacs issues from the xemacs-beta
mailing list since October 1, 2007, and 60 or so tracker-specific
issues. Currently users are expected to interact with the tracker via
the web interface, but a filter on the xemacs-beta list which will
automatically forward bug reports to the tracker is planned for the
near future.
To get started with the tracker, visit
http://tracker.xemacs.org/XEmacs/its/
look at a few issues, and try a couple of queries to see how things
work. Then skim the User Guide to get an idea of how the tracker is
organized and how it tracks our workflow. (The link is at the top of
the Help block in the sidebar.)
Then register. The registration link is in the middle of the Login
block in the sidebar. In principle, registration is simple. You give
Roundup your preferred user name, password, full name, and principal
email address, and (optionally) alternate email addresses. Roundup
sends you a confirmation email, you reply to it, and you're
registered.
In practice, it's a little harder than that. First, email delays will
be experienced because first all email to the tracker needs to go
through moderation (until I feel more confident that tracker spamming
can be prevented), and then the tracker gets email once an hour on a
cron job. (Eventually the tracker host will get a proper MX and that
delay will be eliminated, too.) Outgoing email should be immediate,
though. Your patience is greatly appreciated!
Second, if you happen to be one of the lucky contributers to have your
issue already posted to the tracker, your email address will probably
have already been registered, and you won't be able to register
immediately.
If this happens, please bear with us and do one of the following things:
- Get Roundup to send you a new password. Go to "Lost your login?" in
the Login block of the sidebar, and in the "Password reset request"
page enter your email address in the appropriate field, and click
"Request password reset". Roundup will send you mail telling you
your username (usually equal to the mailbox portion of your email
address) and a new password.
- Send email to me <stephen(a)xemacs.org> with your preferred user name,
full name, principal email address, (optional) alternate email
addresses, and a *temporary* password. I'll fix you up, then you
can log in and change your password. (If you don't do so within a
week, I'll disable that user.)
Once you have a user registered, you can change anything, including
your username and principal email address, from the "Your Details"
page linked from the "Hello, user" block of the sidebar. The only
caveat is that it's difficult to change your principal email address
to one of the alternate addresses or vice versa (there's a race
condition checking for previous use of the email; someday I'll fix
that).
A copy of the instructions for registration are available as the first
section of the User Guide available on the tracker.
Happy tracking!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
This one works with gnu-emacs, but not xemacs. Anyone know why?
It's supposed to just add some font-lock keywords to python mode, but
it seems to override the python keywords instead (only the cython additions
seen below get highlighted, not the original python ones).
;;;; `Cython' mode.
(add-to-list 'auto-mode-alist '("\\.pyx\\'" . cython-mode))
(define-derived-mode cython-mode python-mode "Cython"
(font-lock-add-keywords
nil
`((,(concat "\\<\\(NULL"
"\\|c\\(def\\|har\\|typedef\\)"
"\\|e\\(num\\|xtern\\)"
"\\|float"
"\\|in\\(clude\\|t\\)"
"\\|object\\|public\\|struct\\|type\\|union\\|void"
"\\)\\>")
1 font-lock-keyword-face t))))
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
With M-x `customize-face', diff below delivers face at
point per default for customization.
One strange thing remains: to accept default, user
can't use num-pads "Enter"-key, keyboard-return must be
pressed.
Does this indicate a bug?
Thanks
Andreas Röhler
diff -u MY-PATH/xemacs/20080203/xemacs-21.5/lisp/cus-edit.el
MY-PATH/cus-edit.el
--- MY-PATH/xemacs/20080203/xemacs-21.5/lisp/cus-edit.el 2008-02-03
17:44:41.000000000 +0100
+++ MY-PATH/cus-edit.el 2008-02-03 17:44:41.000000000 +0100
@@ -874,8 +874,8 @@
(defun customize-face (&optional symbol)
"Customize SYMBOL, which should be a face name or nil.
If SYMBOL is nil, customize all faces."
- (interactive (list (completing-read "Customize face: (default all) "
- obarray 'find-face)))
+ (interactive (list (completing-read (concat "Customize face: ")
+ obarray 'find-face nil (if (get-char-property (point) 'face)
(format "%s" (get-char-property (point) 'face) nil)))))
(if (or (null symbol) (and (stringp symbol) (zerop (length symbol))))
(custom-buffer-create (custom-sort-items
(mapcar (lambda (symbol)
;;;;;;
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
> AFAIK, a core file is useless without both the executable that
> generated it and a debugger for the architecture that generated it.
I have put the executable at the same location (http://www.yorel.be/misc/).
> I don't have either; it's really necessary for you to run the debugger
> and post the resulting backtrace to xemacs-beta.
Oh, so you didn't get yesterday's message. I must have goofed after having my mails rejected a couple of times because the attachment was too big.
Here is that message again:
Thanks. --with-xim=no worked.
I rebuilt with the CFLAGS you said. The stack trace is below.
On my computer core files go to /var/core and only root can access that dir. I asked a friendly sysadmin to retrieve it for me. It's in the attachment. Well he retrieved two of them, I'm sending them both to be sure...
Cordially,
Jean-Louis
#0 0x00000000 in ?? ()
#1 0xfef620fc in XRegisterIMInstantiateCallback () from /usr/lib/libX11.so.4
#2 0x00163e40 in x_init_device (d=0x928b00, props=-33312648) at device-x.c:767
#3 0x000694c4 in Fmake_device (type=9603840, connection=-33312648, props=-33312648) at device.c:591
#4 0x0007ea5c in Ffuncall (nargs=-2, args=0xffbfe82c) at eval.c:3536
#5 0x000565a4 in execute_optimized_program (program=0x2d3794 "\207 by", stack_depth=2, constants_data=0xfe184098) at bytecode.c:748
#6 0x00058f90 in funcall_compiled_function (fun=-31767356, nargs=1, args=0xffbfe9f8) at bytecode.c:516
#7 0x0007e948 in Ffuncall (nargs=1, args=0xffbfe9f4) at eval.c:3572
#8 0x000565a4 in execute_optimized_program (program=0x90b52b "\210\nA\023Ë\211\024\207", stack_depth=1, constants_data=0xfe170440) at bytecode.c:748
#9 0x00058f90 in funcall_compiled_function (fun=-31791940, nargs=0, args=0xffbfebc0) at bytecode.c:516
#10 0x0007e948 in Ffuncall (nargs=0, args=0xffbfebbc) at eval.c:3572
#11 0x000565a4 in execute_optimized_program (
program=0x8b0f3b "\210Ò \210*Ó \210Ô \210rÕÖ!q\210× \210ØÙ!\210\016!Úa«\005\016\" \210)Û Üa«\bÝ ¬\004Þ \210ß \210Ù\026#Ý \004àÇ!)\207r buff",
stack_depth=0, constants_data=0xfe17f6c8) at bytecode.c:748
#12 0x00058f90 in funcall_compiled_function (fun=-31771864, nargs=0, args=0xffbfece0) at bytecode.c:516
#13 0x0007e064 in Feval (form=-32322356) at eval.c:3392
#14 0x0007be18 in condition_case_1 (handlers=-32327108, bfun=0x7d9c8 <Feval>, barg=-32322356, hfun=0x80630 <run_condition_case_handlers>, harg=-33338064)
at eval.c:1652
#15 0x0005563c in execute_rare_opcode (stack_ptr=0xffbfef74,
program_ptr=0x2d65a1 "\210Ì\r!\025\016.«\016ÚÓá\016.â ã $!\0267äå!\210\016&«\005äæ!\210Ü\026&ç \210\016(«\005äè!\210Ü\026(\t«\bé\t@\tA\"\210)\0168\003ê \207", opcode=Bcondition_case) at bytecode.c:1273
#16 0x00055c44 in execute_optimized_program (
program=0x2d65a1 "\210Ì\r!\025\016.«\016ÚÓá\016.â ã $!\0267äå!\210\016&«\005äæ!\210Ü\026&ç \210\016(«\005äè!\210Ü\026(\t«\bé\t@\tA\"\210)\0168\003ê \207", stack_depth=1, constants_data=0xfe17fd94) at bytecode.c:658
#17 0x00058f90 in funcall_compiled_function (fun=-31771024, nargs=0, args=0xffbff0a0) at bytecode.c:516
#18 0x0007e064 in Feval (form=-32399516) at eval.c:3392
#19 0x0007be18 in condition_case_1 (handlers=-33313032, bfun=0x7d9c8 <Feval>, barg=-32399516, hfun=0x609b0 <cmd_error>, harg=-33312648) at eval.c:1652
#20 0x00060b20 in top_level_1 (dummy=2731008) at cmdloop.c:206
#21 0x00079bd0 in internal_catch (tag=-33512040, func=0x60ad8 <top_level_1>, arg=-33312648, threw=0x0) at eval.c:1318
#22 0x00060bfc in initial_command_loop (load_me=395992) at cmdloop.c:285
#23 0x000787e8 in xemacs_21_4_21_sparc_sun_solaris2_10 (argc=1, argv=0xffbff5b4, envp=0x2be000, restart=0) at emacs.c:2460
#24 0x00079730 in main (argc=1, argv=0xffbff5b4, envp=0xffbff5bc) at emacs.c:2892
= = = = = = = = = = = = = = = = = = = = = = = = =
Fortis disclaimer :
http://www.fortis.be/legal/disclaimer.htm
Privacy policy related to banking activities of Fortis:
http://www.fortis.be/legal/privacy_policy.htm
= = = = = = = = = = = = = = = = = = = = = = = = =
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
The Roundup tracker has the capability of maintaining a "nosy list"
for each issue, which is the set of users who receive information
about changes to that issue.
Currently only the "Assigned To" developer is automatically added to
the nosy list. (I was worried about spew and to some extent spam.) I
plan to add the Creator (Roundup's term, this is the User who creates
the issue either by posting to the list or by "create new" on the web)
to the Nosy list automatically.
I do not plan to add those who contribute comments. They can add
themselves if they wish.
Comments?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
xemacs-cvs(a)xemacs.org writes:
> +# We include xemacs-base in the load path so as to get any the operator
> +# definitions in autoload-operators.el.
Typo "any the" in comment above.
> $(AUTOLOAD_PATH)/auto-autoloads.el :: $(GENERATED_ELC_DEPENDENCIES)
> - $(XEMACS_BATCH_CLEAN) $(LOAD_AUTOLOADS) \
> + $(XEMACS_BATCH_CLEAN) \
> + -eval '(setq load-path (cons "$(XEMACS_PACKAGES_BASE)/xemacs-packages/xemacs-base" load-path)))' \
> + $(LOAD_AUTOLOADS) \
> -eval "$(AUTOLOAD_PACKAGE_NAME)" \
> -eval "$(AUTOLOAD_FILE)" \
> -l autoload -f batch-update-autoloads $^
This is getting hideous. Maybe it's time for a library analogous to
package-compile.el?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta