Re: [address@hidden: Re: ":" in Scheme names.]

[Thien-Thi Nguyen]

   From: Aubrey Jaffer <agj@alum.mit.edu>
   Date: Sun, 19 Jan 2003 16:59:45 -0500 (EST)

   If the patch improves some (but not all) behaviors, then it is still
   worth releasing.

yes.  which behaviors does it improve?  what goes in the change log?

   If you show me how to provoke the remaining misbehaviors, then I can
   look at fixing them.

here is an interactive test case, w/ expected output:

evaluate: (info "/usr/share/info/slib.tar.gz")

then, 
; type                  ; expect
  i RET                   buffer changes to show index
  C-s array-indexes RET   point moves to match
  m RET                   buffer changes to show array mapping funcs
  l                       back to index
  C-s batch: RET          point moves to match
  m RET                   buffer changes to show batch funcs
  l                       back to index

this sequence exercises several parsing contexts, to start; from here
you can try other `m' and `i' variants.

for me, not all of the expected behaviors take place.  some signal
end-of-file error.  (after applying the patch i started looking at all
functions that have ":" in their regexp strings to see if they make
similar assumptions (that this patch fixes for this function) about tag
charset; i'm not sure what i'm working with exactly anymore, ymmv. :-)

the constraint "must not contain colon followed by space" is easy for
tags comprising programming language terms to meet w/o special handling,
and it is more permissive than the current "must not contain colon", so
as a fix it is ok.  but i wonder if there is a better fix.

thi