From: Y. E. via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53231@debbugs.gnu.org
Subject: bug#53231: 28.0.90; [PATCH] GNU ELPA: Enable sentence-end-double-space in README
Date: Thu, 13 Jan 2022 17:02:15 +0200 [thread overview]
Message-ID: <m2fspru1ag.fsf@ego.team> (raw)
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
This update is for those (like me) who have 'sentence-end-double-space'
disabled in their configurations. As far as I understand,
'.dir-locals.el' is not added on purpose to this directory, right?
Thanks,
YE
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: README (Local variables): Enable sentence-end-double-space --]
[-- Type: text/x-patch, Size: 621 bytes --]
From a8ab2128960e79b5df28fa8a02f30481784188d5 Mon Sep 17 00:00:00 2001
From: YugaEgo <yet@ego.team>
Date: Thu, 13 Jan 2022 16:51:07 +0200
Subject: [PATCH] * README (Local variables): Enable sentence-end-double-space
---
README | 1 +
1 file changed, 1 insertion(+)
diff --git a/README b/README
index f05e9e58ac..ff2a5d0f92 100644
--- a/README
+++ b/README
@@ -588,6 +588,7 @@ along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>.
Local variables:
mode: org
fill-column: 70
+sentence-end-double-space: t
paragraph-separate: "[ \f]*$"
time-stamp-pattern: "4/#\\+DATE: %Y-%02m-%02d$"
end:
--
2.34.1
next reply other threads:[~2022-01-13 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 15:02 Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-14 7:53 ` bug#53231: 28.0.90; [PATCH] GNU ELPA: Enable sentence-end-double-space in README Lars Ingebrigtsen
2022-01-14 16:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-17 16:48 ` Y. E. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-17 21:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 9:11 ` Lars Ingebrigtsen
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=m2fspru1ag.fsf@ego.team \
--to=bug-gnu-emacs@gnu.org \
--cc=53231@debbugs.gnu.org \
--cc=yet@ego.team \
/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).