From: Yuri Khan <yurivkhan@gmail.com>
To: van@scratch.space
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: FW: bug#32758: 26.1 emacs-mac 7.2; forward-sentence in eww
Date: Wed, 10 Oct 2018 18:28:25 +0700 [thread overview]
Message-ID: <CAP_d_8U3hLVuG3U+tWhbyWesumND6QxykjyBta2627t5MGdqhg@mail.gmail.com> (raw)
In-Reply-To: <CE7012A2-D45D-4E17-8621-04411E0A0FED@scratch.space>
On Wed, Oct 10, 2018 at 5:17 PM Van L <van@scratch.space> wrote:
> I am looking for a one-space after punctuation sentence-ending for M-e to jump by.
>
> Disabling the following variable stops short at Nov. or Gov. (see below)
>
> ┌────
> │ (setq sentence-end-double-space nil)
> └────
>
> ┌────
> │ Haley’s departure also stoked speculation she could replace Lindsey Graham as the senator from
> │ South Carolina, a possibility that Trump played down. Talk in Washington is that should Trump
> │ replace Attorney General Jeff Sessions with Graham after the Nov. 6 congressional elections,
> │ South Carolina Gov. Henry McMaster would be responsible for selecting a replacement to serve
> │ until the 2020 election. McMaster was previously Haley’s No. 2 in the state.
> └────
>
> and I’m aware of names like A. B. C. Nurmagomedov which will stop early, too.
It might be a good idea to treat the sequence “period followed by a
single non-breaking space” as not ending a sentence. This, coupled
with the proper use of non-breaking spaces with abbreviations and
initials, will go a long way in solving the above false positive in
sentence end detection.
> ┌────
> │ 178 (defun sentence-end ()
…
> │ 191 ;; We accept non-break space along with space.
…
> │ 199 "[ \u00a0\t\n]*")))
> └────
next prev parent reply other threads:[~2018-10-10 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 10:17 FW: bug#32758: 26.1 emacs-mac 7.2; forward-sentence in eww Van L
2018-10-10 11:28 ` Yuri Khan [this message]
2018-10-10 14:19 ` Van L
2018-10-10 15:17 ` FW: " Stefan Monnier
2018-10-10 15:56 ` Yuri Khan
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=CAP_d_8U3hLVuG3U+tWhbyWesumND6QxykjyBta2627t5MGdqhg@mail.gmail.com \
--to=yurivkhan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=van@scratch.space \
/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.
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).