all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arjan Bos <Arjan.Bos@nospam.ISeeYou.nl>
Subject: parens matching not matching all matching parens
Date: Thu, 16 Sep 2004 21:19:42 +0200	[thread overview]
Message-ID: <cicpfn$h66$1@reader11.wxs.nl> (raw)

Hi all,

I'm currently developing yet another rich text format writer. And as you 
might know, RTF is using curly braces a lot. Alas, every now and then, a 
normal parentheses pops up between a set of matching {}. Both the parens 
matching colouring and the forward-sexp / backward-sexp can't handle 
this. How can I (help to) solve this?

An rtf snippet is included here:

{\rtf1\mac\ansicpg10000\uc1
{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang{\pntxta )}}}

This is a complete piece of (non-sensical, but correct) rtf. The first 
`{' matches the last `}'. Only C-M-f jumps from the first `{' to the 
one-to-last `}'.

I'm wondering if this is a bug or not.

TIA,

Arjan


-- 
--
If you really want to contact me, then replace the "I see you" text by 
its three letter accronym, hetnet.

Fabricate Diem PVNC, Motto of the Night Watch -- Terry Pratchett

             reply	other threads:[~2004-09-16 19:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 19:19 Arjan Bos [this message]
2004-09-16 19:42 ` parens matching not matching all matching parens J. David Boyd
     [not found] ` <mailman.3032.1095364141.1998.help-gnu-emacs@gnu.org>
2004-09-16 20:19   ` Arjan Bos
2004-09-16 21:45     ` Miles Bader
2004-09-17 17:25       ` Arjan Bos
2004-09-17 18:17         ` Stefan Monnier
2004-09-18  0:25           ` Miles Bader
2004-09-17 18:22         ` Stefan Monnier
2004-09-17 18:36           ` Arjan Bos
2004-09-17  2:18 ` Greg Hill
     [not found] ` <mailman.3063.1095387904.1998.help-gnu-emacs@gnu.org>
2004-09-17 17:29   ` Arjan Bos
2004-09-17 20:43     ` Greg Hill

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='cicpfn$h66$1@reader11.wxs.nl' \
    --to=arjan.bos@nospam.iseeyou.nl \
    --cc=Arjan.Bos@ISeeYou.nl \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.