Mercurial > hg > xemacs-beta
view etc/MAILINGLISTS @ 788:026c5bf9c134
[xemacs-hg @ 2002-03-21 07:29:57 by ben]
chartab.c: Fix bugs in implementation and doc strings.
config.h.in: Add foo_checking_assert_at_line() macros. Not clear whether these
are actually useful, though; I'll take them out if not.
symsinit.h, emacs.c: Some improvements to the timeline. Rearrange a bit the init
calls. Add call for reinit_vars_of_object_mswindows() and
declare in symsinit.h.
event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, event-tty.c, events.c, events.h: Introduce new event methods for printing, comparing, and hashing
magic events, to avoid event-type-specific stuff that had crept
into events.c. (And was crashing, since the channel in MS Windows
magic events may be nil.) Implement the methods in
event-{tty,gtk,Xt,mswindows}.c. Make wrapping functions
event_stream_{compare,hash,format}_magic_event() to check if
everything's OK and call the actual callback. Fix events.c to use
the new methods. Add a new event-stream-operation
EVENT_STREAM_NOTHING -- event stream not actually required to be
able to do anything, just be open. (#### This
event-stream-operation stuff needs to be rethought.)
Fixed describe_event() in event-Xt.c to print its output to a
stream, not always to stderr, so it can be used
elsewhere. (e.g. in print-event when a magic event is
encountered?)
lisp.h, lrecord.h: Define new assert_at_line(), for use in asserts inside of inline
functions. The assert will report the line and file of the inline
function, which is almost certainly not what you want as it's
useless. what you want to see is where the pseudo-macro was
called from. So, when error-checking is on, we pass in the line
and file into the macros, for accurate printout using
assert_at_line(). Happens only when error-checking is defined so
doesn't slow down non-error-checking builds. Fix XCHAR, XINT,
XCHAR_OR_INT, XFOO, and wrap_foo() in this fashion.
lstream.c, lstream.h: Add resizing_buffer_to_lisp_string().
objects-gtk.c: Fix typo.
objects-msw.c: Implement a smarter way of determining whether a font matches a
charset. Formerly we just looked at the "script" element of the
font spec, converted it to a code page, and compared it with the
code page derived from the charset. Now, as well as doing this,
we ask the font for the list of unicode ranges it supports, see
what range the charset falls into (#### bogus! need to do this
char-by-char), and see if any of the font's supported ranges
include the charset's range. also do some caching in
Vfont_signature_data of previous inquiries.
charset.h, text.c, mule-charset.c: New fun; extracted out of
Fmake_char() and declare prototype in charset.h.
text.h: introduce assert_by_line() to make
REP_BYTES_BY_FIRST_BYTE report the file and line more accurately
in an assertion failure.
unicode.c: make non-static (used in objects-msw.c), declare in charset.h.
mule\mule-category.el: Start implementing a category API compatible with FSF. Not there yet.
We need improvements to char-tables.
mule\mule-charset.el: Copy translation table code from FSF 21.1 and fix up. Eventually
we'll have them in XEmacs. (used in ccl) Not here quite yet, and
we need some improvements to char-tables.
mule\cyril-util.el, mule\cyrillic.el, mule\devan-util.el, mule\ethio-util.el, mule\korea-util.el, mule\mule-tty-init.el, mule\tibet-util.el, mule\viet-util.el, mule\vietnamese.el: Fix numerous compilation warnings. Fix up code related to
translation tables and other types of char-tables.
menubar-items.el: Move the frame commands from
the View menu to the File menu, to be consistent with how most other
programs do things. Move less-used revert/recover items to a submenu.
Make "recover" not prompt for a file, but recover the current buffer.
TODO.ben-mule-21-5: Create bug list for latest problems.
| author | ben |
|---|---|
| date | Thu, 21 Mar 2002 07:31:30 +0000 |
| parents | 3ecd8885ac67 |
| children |
line wrap: on
line source
XEmacs Electronic Mailing Lists. Last Modified: 1999-11-08 XEmacs has its own mailing lists and newsgroup which are distinct from the FSF GNU Emacs mailing lists and newsgroups. The mailing lists are: xemacs@xemacs.org comp.emacs.xemacs bi-directional gateway. xemacs is an open list for discussion and bug reporting for XEmacs. This mailing list is bi-directionally gatewayed with the USENET newsgroup comp.emacs.xemacs. xemacs-announce@xemacs.org XEmacs Announcements. xemacs-announce is a read-only, low volume list for announcements concerning the XEmacs project and new releases of the XEmacs software. xemacs-beta@xemacs.org XEmacs Beta Testers. xemacs-beta is an open list for bug reports and general communication about beta versions of XEmacs. xemacs-build-reports@xemacs.org XEmacs Build Report Submissions. xemacs-build-reports is an open list for submission of build-reports on beta versions of XEmacs. For information on what the build-reports should contain, please see the `etc/BETA' file which is included in each beta distribution. xemacs-cvs@xemacs.org XEmacs CVS Commit Notices. xemacs-cvs is a read-only list for notices and information on what has been committed to the XEmacs CVS trees, by whom, and for what. (For more information on the XEmacs CVS Archive: http://cvs.xemacs.org/.) xemacs-mule@xemacs.org XEmacs International Extensions. xemacs-mule is an open mailing list for discussion of International extensions to XEmacs including Mule, XIM, I18n issues, etc, and is not confined to developmental issues. This list is not restricted to English, postings in all languages are welcome. xemacs-nt@xemacs.org XEmacs on Windows NT/98/95. xemacs-nt is a developer's only mailing list and is intended for people who wish to work actively on the porting of XEmacs to Microsoft Windows NT and Microsoft Windows 98/95. xemacs-patches@xemacs.org XEmacs Patch Submissions. xemacs-patches is an open, moderated list for submission of patches to the XEmacs distribution and its packages. Anyone may subscribe or submit to xemacs-patches, but all submissions are reviewed by the list moderator before they are distributed to the list. Discussion is not appropriate on xemacs-patches. xemacs-users-ja@xemacs.org XEmacs (Japanese). xemacs-users-ja is an open list for discussion and bug reporting for XEmacs. Japanese is the preferred language of discussion. It is not gated to comp.emacs.xemacs or the xemacs list. For fastest response, bugs not specifically related to Japanese or Mule features should be reported on xemacs (in English). xemacs-beta-ja@xemacs.org XEmacs Beta (Japanese). xemacs-beta-ja is an open list for bug reports and general communication about beta versions of XEmacs, especially features related to Mule and Japanese-handling. Japanese is the preferred language of discussion. Bugs not specifically related to Japanese or Mule features should be reported on xemacs-beta (in English). Please consider sending bug reports on Mule to xemacs-mule, in English. The most up to date information on the mailing lists can always be found at http://www.xemacs.org/. Subscriptions: Subscription to all the lists is accomplished by sending an e-mail message to LISTNAME-request@xemacs.org with `subscribe' (without the quotes) as the BODY of the message. To unsubscribe, send an e-mail to LISTNAME-request@xemacs.org with `unsubscribe' (without the quotes) as the BODY of the message. List Archives: A browsable and searchable archive of these lists is available at http://www.xemacs.org/list-archives/. Problems: Any comments, questions, or complaints about the lists should be brought to the attention of the XEmacs Mailing List Manager <list-manager@xemacs.org>. ----------------------------------------------------------------------- GNU Project Electronic Mailing Lists and gnUSENET Newsgroups: The XEmacs project is separate from and not managed by the GNU project. The latest information about the GNU project mailing lists can be found at ftp://ftp.gnu.org/gnu/GNUinfo/MAILINGLISTS Please do NOT send messages about problems with XEmacs to the FSF GNU Emacs newsgroups and mailing lists unless you are sure that the problem you are reporting is a problem with both versions of GNU Emacs. People who aren't subscribed to the XEmacs mailing list most likely are not interested in hearing about problems with it.