Re: Open bugs in 21.5

----- Original Message ----- From: "Frank Schmitt" <ich(a)Frank-Schmitt.net&gt; To: <xemacs-beta(a)xemacs.org&gt; Cc: <ben(a)xemacs.org&gt; Sent: Saturday, October 26, 2002 4:29 AM Subject: Open bugs in 21.5 Hello I reported most of those bugs several times before, but as they still aren't resolved, I bring them hereby back into mind in the hope that now after Ben seems to be back at work, some of them (or even better all of them:-)) can be resolved. XEmacs is from CVS, native windows, build some days ago with MS VC++ 6, all external packages. Detailed info is attached. Everything tested under xemacs -vanilla. 1) XEmacs is currently broken in respect to detection of character set for European users. This started with a patch by Katsumi Yamaoka which fixes some issues for Japanese users, I applied the reverse patch from http://list-archive.xemacs.org/xemacs-beta/200209/msg00454.html now everything is fine again, there should be a general solution which satisfies both groups of users. This bug is very urgent IMO since it really makes XEmacs almost unusable.

2) It is impossible to display characters which are part of Unicode, but of no other coding-system known to XEmacs. Instead of the character a bold = is drawn.

3) M-x set-input-method has some problems: Tab completion doesn't work. Enter any character, it will say "No match". For me it defaults to german-postfix. If I accept it via enter it says "Can't activate input method german-postfix", if I enter german-postix at the prompt it says "No match". The same problem with M-x toggle-input method: "Can't activate input method german-postfix". Language Environment is set to German as you can guess. 4) (prefer-coding-system 'arg) doesn't work, if arg is a windows charset or a unicode encoding scheme like utf-8, XEmacs states "Can't prefer coding-system `utf-8'" 5) Selecting rectangles with the mouse via M - button1 doesn't work. The meta key is ignored, XEmacs behaves as if I didn't hold it. Under 21.4.6 it works as suggested. 6) There seems to be no support for UTF-7. It would be nice to have support for this because some Outlook Express users use it, because it solves the wrong signature delimiter bug in Outlook Express. I see there's already code which deals with UTF-7, but it's commented out. 7) XEmacs crashes _very_ often if you choose Edit->Find from the menu (about one out of three times for me). Backtrace is attached.

8) Often after I use XEmacs for a longer time, it suddenly doesn't update display anymore. Input is processed, but there's no change in the display, if I change size of the XEmacs window, it works again and I see the changes I made while display wasn't updated. I normally work with a maximized XEmacs window if this matters. 9) If I want to input a ^ it works in every Windows application to type ^<space>, only in XEmacs it doesn't work. I didn't find any possibility to type a single ^ but hitting the key two times and deleting the second one. The same goes for ´ and `. This is especially annoying if a command is bound to one of these. 10) (This one showed sometimes in 21.4.x but is much worse with 21.5.x so I report it here as well as it's more a flyspell issue) XEmacs will stall and not respond any more if you do the following: Open a file, enter flyspell-mode, paste a large portion of text (20-30 lines), move the scrollbar to the top of the buffer and back to the bottom again, give focus to buffer. The problem seems to be, that Flyspell checks every word in the buffer you pass when scrolling, sometimes words are checked many times. This doesn't happen if you use page-up - page-down instead of the scroll-bar. 11) There was a discussion some time ago regarding a bug-tracking system for XEmacs, general agreement was "we need one", but nothing really happened since then (or I've missed it). 12) Shortcut for search: In the menu (Edit->Find) there's no shortcut given, it should read "Find C-s" instead of "Find". 13) There's no documentation for winclient.exe, further on it should be possible to open a file in a new frame with winclient. 14) I'm absolutely sure there was one more issue but I just can't remember what it was :-) In general XEmacs 21.5 in the current state is usable but there are really _many_ quirks and issues which have to be resolved before it can be made available for general use.