unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aaron Jensen <aaronjensen@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 30815@debbugs.gnu.org
Subject: bug#30815: 26.0.91; unicode right single quote mark with syntax entry of w not respected by forward-word
Date: Tue, 13 Mar 2018 19:07:02 -0700	[thread overview]
Message-ID: <CAHyO48ymfyWWOX5apkKz1vPwwX-Pw0j7Os4-UJi4U92rh1aThQ@mail.gmail.com> (raw)
In-Reply-To: <87fu53xxzc.fsf@gmail.com>

On Tue, Mar 13, 2018 at 6:11 PM, Noam Postavsky <npostavs@gmail.com> wrote:
> See `(elisp) Word Motion':
>
>      Characters that belong to different scripts (as defined by
>      `char-syntax-table'), also define a word boundary
>
> and discussion in Bug#10494 which prompted the update of that section.
>
> Hmm, I think I meant `char-script-table', as `char-syntax-table' doesn't
> seem to exist...

Thank you for the pointer. FWIW, I checked the docs of forward-word
which only talks about buffer syntax tables. Perhaps that should
either reference the Word Motion docs or it should also describe the
whole picture.

Also, as I understand the thread it seems like this is "by design" and
there's no good/accepted way to get it to behave as I want without
risking breaking unknown things.





  reply	other threads:[~2018-03-14  2:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  0:14 bug#30815: 26.0.91; unicode right single quote mark with syntax entry of w not respected by forward-word Aaron Jensen
2018-03-14  1:11 ` Noam Postavsky
2018-03-14  2:07   ` Aaron Jensen [this message]
2018-03-14  2:24     ` Noam Postavsky
2018-03-14  2:43       ` Aaron Jensen
2018-03-14 16:09         ` Eli Zaretskii
2018-03-14 17:43           ` Aaron Jensen
2018-03-14 17:51             ` Eli Zaretskii
2018-03-14 15:59       ` Eli Zaretskii
2018-03-14 23:19         ` Noam Postavsky
2018-03-15  6:39           ` Eli Zaretskii
2018-03-17  0:03             ` Noam Postavsky

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=CAHyO48ymfyWWOX5apkKz1vPwwX-Pw0j7Os4-UJi4U92rh1aThQ@mail.gmail.com \
    --to=aaronjensen@gmail.com \
    --cc=30815@debbugs.gnu.org \
    --cc=npostavs@gmail.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 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).