From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 10494@debbugs.gnu.org, aaronecay@gmail.com
Subject: bug#10494: 24.0.92; Syntax table and non-ASCII character interaction
Date: Sat, 13 Aug 2016 09:56:57 +0300 [thread overview]
Message-ID: <83eg5tdume.fsf@gnu.org> (raw)
In-Reply-To: <87h9apy5ob.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Cc: 10494@debbugs.gnu.org, aaronecay@gmail.com
> Date: Fri, 12 Aug 2016 18:37:56 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Indeed. This is a feature:
>
> Ah, so doing
>
> (modify-syntax-entry ?’ "w" text-mode-syntax-table)
> (aset char-script-table ?’ 'latin)
>
> does let word motion skip over ’ as OP wanted.
Yes. But I don't recommend such a "solution", because that would most
probably bite elsewhere, when we do want that character behave as a
symbol.
> `(elisp) Word Motion' looks like a good place for it:
Right, thanks.
> The functions for parsing words described below use the syntax table
> -to decide whether a given character is part of a word. @xref{Syntax
> -Tables}.
> +and @code{char-script-table} to decide whether a given character is
> +part of a word. @xref{Syntax Tables} and @xref{Character Properties}.
@xref generates a capitalized "See", so is inappropriate in the middle
of a sentence. Please use "see @ref" instead.
> +@code{find-word-boundary-function-table}, described below. Characters
> +that belong to a different script (as defined by
I'd say "belong to different scripts", otherwise the text begs the
question "different from what?".
> +@code{char-syntax-table}), also mark a word boundary (@pxref{Character
"define a word boundary" sounds better to me.
Othwrise, LGTM, thanks. Please push to emacs-25.
next prev parent reply other threads:[~2016-08-13 6:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 8:40 bug#10494: 24.0.92; Syntax table and non-ASCII character interaction Aaron Ecay
2012-01-13 10:45 ` Andreas Schwab
2012-01-13 17:04 ` Aaron Ecay
2016-08-11 0:29 ` npostavs
2016-08-11 15:24 ` Eli Zaretskii
2016-08-12 22:37 ` npostavs
2016-08-13 6:56 ` Eli Zaretskii [this message]
2016-08-13 13:21 ` npostavs
2016-08-13 13:33 ` Eli Zaretskii
2016-08-13 14:19 ` npostavs
2016-08-13 14:31 ` Eli Zaretskii
2016-08-13 14:55 ` Eli Zaretskii
2016-08-13 18:14 ` npostavs
2016-08-13 18:35 ` Eli Zaretskii
2016-08-13 21:42 ` npostavs
2016-08-14 2:32 ` Eli Zaretskii
2016-08-14 2:58 ` npostavs
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eg5tdume.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10494@debbugs.gnu.org \
--cc=aaronecay@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).