From: Kevin Rodgers <kevinr@ihs.com>
Subject: Re: sgml-mode skip tag forward/back bug fix -- followup
Date: 29 Apr 2002 17:34:43 -0600 [thread overview]
Message-ID: <wefd6wit6y4.fsf@ihs.com> (raw)
In-Reply-To: E0DD84E4C306394C8C897D3ED9BB17E11B4B84@aisexch.ausinfo.com
"Mallory, Rich" <Rich.Mallory@ausinfo.com> writes:
> Further testing revealed that the bug fix proposed in that email
> was incomplete. The complete set of diffs follows, including the
> diffs from the original email. The proposed fix works without the
> new additions. However, the change to line 687 is needed to
> keep up-list from beeping each time function sgml-skip-tag-forward
> is executed. (My machine at work has no speaker, so I didn't hear
> a beep and ignored the message until I got home.) The original
> code for line 683 produces no beep, but the change to line 683
> seems advisable.
...
> The changes to lines 683 and 687 are required by the change to
> line 676. The latter causes the regexp 're' to match one
> additional character, leaving the point after that character. If this
> character is '>', the point is outside the tag matched by 're'. In
> the original code, the point was inside the tag, and up-list moved
> the point to the beginning of the tag. With the point after the
> closing '>', up-list can't do that.
Why don't you make use of the syntax table, and append "\\>" instead
to the tag regexp? That would prevent matching element names that are
a prefix of the one to be skipped as desired, and wouldn't match the
extra character that necessitates the call to backward-char before
up-list.
--
Kevin Rodgers <kevinr@ihs.com>
prev parent reply other threads:[~2002-04-29 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 19:51 sgml-mode skip tag forward/back bug fix -- followup Mallory, Rich
2002-04-29 23:34 ` Kevin Rodgers [this message]
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=wefd6wit6y4.fsf@ihs.com \
--to=kevinr@ihs.com \
/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.