Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <sryoungs@bigpond.net.au>
Cc: Gnus List <ding@gnus.org>, Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Splitting mail -- XEmacs 21.4 vs 21.5
Date: Tue, 02 Mar 2004 16:59:31 +1000	[thread overview]
Message-ID: <microsoft-free.87brnflooc.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <b9y1xodvwzr.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 01 Mar 2004 16:37:28 +0900")

[-- Attachment #1: Type: text/plain, Size: 3376 bytes --]

* Katsumi Yamaoka <yamaoka@jpl.org> writes:

  >>>>>> In <b9yn071w5gr.fsf@jpl.org> Katsumi Yamaoka wrote:
  >> You may be able to solve the problem by setting the
  >> `nnmail-split-fancy-match-partial-words' variable as t.

  > Oops, sorry.  Gnus should be built with XEmacs 21.5 if it is
  > used with XEmacs 21.5.  

Yes, building Gnus with XEmacs 21.5 gets around it, and _that_ Gnus
seems to work OK in XEmacs 21.4 too.

  > See also:

  >> http://thread.gmane.org/sdd685fw0w.fsf@wes.hardakers.net

Seems that we've (XEmacs.org) screwed things royally.  Who's big on
syntax tables that could take a look at this?

  > The bug came to light by Gnus on January 7, 2004.

The only things that I could find that might be remotely related
are... 

2003-02-28  Ben Wing  <ben@xemacs.org>

  [...]

	* chartab.c (fill_char_table):
	* chartab.c (put_char_table):
	* lrecord.h:
	Fix crash due to attempt to free objects across dump/undump.

This patch is at:

<http://list-archive.xemacs.org/xemacs-patches/200303/msg00000.html>


And...

2003-02-14  Ben Wing  <ben@xemacs.org>

	* buffer.c:
	* syntax.c:
	Move syntax table description from buffer.c to syntax.c.
	
	* chartab.c:
	* chartab.c (set_char_table_dirty):
	* chartab.c (fill_char_table):
	* chartab.c (Fmake_char_table):
	* chartab.c (Fcopy_char_table):
	* chartab.c (get_range_char_table_1):
	* chartab.c (get_range_char_table):
	* chartab.c (put_char_table):
	* chartab.h:
	* chartab.h (struct Lisp_Char_Table):
	Free extra char table entries to avoid excessive garbage.
	Add flags for dirty and mirror_table_p to char tables.
	Add a back pointer from mirror tables to the original syntax table.
	When modifying a syntax table, don't update the mirror table right
	away, just mark as dirty.
	Add various asserts to make sure we are dealing with the right type
	of table (mirror or non-mirror).
	
	* font-lock.c:
	* font-lock.c (find_context):
	* syntax.c (init_syntax_cache):
	* syntax.c (setup_syntax_cache):
	* syntax.c (mark_buffer_syntax_cache):
	* syntax.c (init_buffer_syntax_cache):
	* syntax.c (syntax_cache_table_was_changed):
	* syntax.c (update_syntax_cache):
	* syntax.c (scan_lists):
	* syntax.c (scan_sexps_forward):
	* syntax.c (copy_if_not_already_present):
	* syntax.c (update_just_this_syntax_table):
	* syntax.c (update_syntax_table):
	* syntax.c (vars_of_syntax):
	* syntax.h:
	* syntax.h (struct syntax_cache):
	Add entry to syntax caches for the non-mirror table.  Set it
	appropriately when initializing the syntax table.  Use it, not
	the mirror table, for calls to syntax_match().
	Don't create a bogus float each time, just once at startup.
	Add some asserts, as in chartab.c.

	* syntax.h (SYNTAX_CODE_FROM_CACHE):
	When retrieving the syntax code, check the dirty flag and update
	the mirror tables as appropriate.
	Add some asserts, as above.

This one is here:
	
<http://list-archive.xemacs.org/xemacs-patches/200302/msg00150.html>

Thanks very much for getting back to me on this, Katsumi, I really
appreciate it.  BTW, do you know enough about these kind of things to
take a look at these two patches and perhaps offer some suggestions?

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|        XEmacs - The only _______ you'll ever need.       |
|          Fill in the blank, yes, it's THAT good!         |
|------------------------------<sryoungs@bigpond.net.au>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-03-02  6:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01  2:20 Steve Youngs
2004-03-01  4:34 ` Katsumi Yamaoka
2004-03-01  7:37   ` Katsumi Yamaoka
2004-03-02  6:59     ` Steve Youngs [this message]
2004-03-03  2:30     ` Stephen J. Turnbull
2004-03-03  3:25       ` Katsumi Yamaoka
2004-03-01 20:10 ` Karl Pflästerer
2004-03-03  2:20 ` Stephen J. Turnbull

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=microsoft-free.87brnflooc.fsf@eicq.dnsalias.org \
    --to=sryoungs@bigpond.net.au \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).