Gnus development mailing list
 help / color / mirror / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: shy group bug in XEmacs 21.4
Date: Sat, 04 Sep 2004 00:17:19 +0900	[thread overview]
Message-ID: <878ybr4c1s.fsf@tleepslib.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <b9ywtzbbpue.fsf_-_@jpl.org> (Katsumi Yamaoka's message of "Fri, 03 Sep 2004 19:37:29 +0900")

>>>>> "KY" == Katsumi Yamaoka <yamaoka@jpl.org> writes:

    KY> If anything, I don't feel like degenerating them.  Because
    KY> using `shy group' is hopeful to improve the performance.

IIRC, shy groups by themselves make negligible difference to XEmacs's
regexps.  I think the improvement in clarity and flexibility of
subexpressions is well worth it though.

    KY> Isn't there a chance of fixing XEmacs 21.4?

It depends on exactly what code needs to be changed, although Vin
S. has final say either way.  Do you have any idea where the bug is?
It's been a while since I looked at regexp.c.


-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.



  reply	other threads:[~2004-09-03 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03  6:05 [Fixed] list identifiers don't disappear in summary Katsumi Yamaoka
     [not found] ` <hhwtzbzuzw.fsf@blah.pl>
2004-09-03  8:27   ` Katsumi Yamaoka
2004-09-03 10:37     ` shy group bug in XEmacs 21.4 (was Re: [Fixed] list identifiers...) Katsumi Yamaoka
2004-09-03 15:17       ` Stephen J. Turnbull [this message]
2004-09-03 16:12         ` shy group bug in XEmacs 21.4 Katsumi Yamaoka
2004-09-10  0:03 ` [Fixed] list identifiers don't disappear in summary Miles Bader

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=878ybr4c1s.fsf@tleepslib.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=ding@gnus.org \
    --cc=xemacs-beta@xemacs.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).