unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 30815@debbugs.gnu.org, aaronjensen@gmail.com
Subject: bug#30815: 26.0.91; unicode right single quote mark with syntax entry of w not respected by forward-word
Date: Wed, 14 Mar 2018 17:59:49 +0200	[thread overview]
Message-ID: <83a7vasl56.fsf@gnu.org> (raw)
In-Reply-To: <87y3ivwg0h.fsf@gmail.com> (message from Noam Postavsky on Tue, 13 Mar 2018 22:24:46 -0400)

> From: Noam Postavsky <npostavs@gmail.com>
> Date: Tue, 13 Mar 2018 22:24:46 -0400
> Cc: 30815@debbugs.gnu.org
> 
> diff --git a/src/syntax.c b/src/syntax.c
> index 378064611c..d3dd79229a 100644
> --- a/src/syntax.c
> +++ b/src/syntax.c
> @@ -1555,7 +1555,8 @@ DEFUN ("forward-word", Fforward_word, Sforward_word, 0, 1, "^p",
>  table, but `find-word-boundary-function-table', such as set up
>  by `subword-mode', can change that.  If a Lisp program needs to
>  move by words determined strictly by the syntax table, it should
> -use `forward-word-strictly' instead.  */)
> +use `forward-word-strictly' instead.  See Info node `(elisp) Word
> +Motion' for details.  */)

I think we should at least mention char-script-table before sending
the reader to the manual.  Currently we mention the syntax table, but
keep complete silence regarding the script differences.

Thanks.





  parent reply	other threads:[~2018-03-14 15:59 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
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 [this message]
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=83a7vasl56.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30815@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    --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).