On Fri, Jul 04, 2008 at 09:57:39PM +0200, Andreas Röhler wrote:
[...]
 Played around with it now several months ago while
 looking for thing-at-point-utils. 
 
 AFAIR result of `forward-sexp' was
 unpredictable in certain circumstances due to
 unpredictable results of `scan-sexps'.
 
 Conclusion was to avoid it completely if encountering
 a problem.
 
 If you may send me a precise scenario, what to perform
 and where available tools fail, that may help to find a
 solution. 
You can try to edit the following script in shell-script mode, and put
your corser at the first `{' character. Then the first `)' character
will be highlighted, it should light the last `}' character instead of
that `)'.
--8<---------------cut here---------------start------------->8---
#!/bin/bash
function test_sexp() {
    case $1 in
	test)
	true
	;;
	up)
	true
	;;
	down)
	true
	;;
	left)
	true
	;;
	right)
	true
	;;
	*)
	echo good bye
	;;
	esac
}
--8<---------------cut here---------------end--------------->8---
 
 Andreas Röhler
 
 PS: Here XEmacs parens-highlighting is fine with
 shell-script-mode.
 
 XEmacs 21.5  (beta28) "fuki" (+CVS-20070806) [Lucid] (i386-suse-linux, Mule) 
 of Thu Jan 24 2008 on molitor
 
  
I've test this scenario on several platform (win32, Linux x64,
cygwin), all failed to do the right thing.
Thanks,
FKtPp
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta