From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Lack of tooling slowing down contributions
Date: Tue, 18 Jun 2019 00:08:09 +0300 [thread overview]
Message-ID: <87r27rc292.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvh88pw3tp.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 16 Jun 2019 18:44:52 -0400")
>>> I.e, using single spacing, then M-q won't change that, because Emacs
>>> doesn't recognize that as being two separate sentences.
>>
>> This feature is sorely missed: every time I copy text from web browsers
>> to Emacs I have to manually insert additional space at the end of every
>> copied sentence before typing M-q.
>
> What would you want it to do?
> Does setting sentence-end-double-space to nil solve it?
> If not, what's the difference?
I tried to set sentence-end-double-space to nil, but reverted back to t
because paragraphs with sentences separated by double space are easier to read
when editing text using a monospaced font in Emacs (there is no such problem
with proportional fonts in web browsers).
> Would you want to recognize single-space end of sentence but change
> them to a double space?
Yes, maybe a separate command is needed, e.g. M-x sentence-use-double-space
that would recognize single-space that doesn't separate an abbreviation
and insert additional space.
next prev parent reply other threads:[~2019-06-17 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 7:38 Lack of tooling slowing down contributions Damien Cassou
2019-06-14 7:58 ` Eli Zaretskii
2019-06-14 11:19 ` Noam Postavsky
2019-06-16 19:20 ` Juri Linkov
2019-06-16 22:44 ` Stefan Monnier
2019-06-17 21:08 ` Juri Linkov [this message]
2019-06-16 23:06 ` Phil Sainty
2019-06-17 5:44 ` Van L
2019-06-17 9:53 ` Marcin Borkowski
2019-06-17 10:22 ` Yuri Khan
2019-06-17 21:19 ` Juri Linkov
2019-06-18 21:29 ` Juri Linkov
2019-06-19 12:50 ` Andy Moreton
2019-06-19 20:47 ` Juri Linkov
2019-06-19 21:26 ` Noam Postavsky
2019-06-17 6:57 ` Damien Cassou
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=87r27rc292.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).