From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 47129@debbugs.gnu.org
Subject: bug#47129: [PATCH] Fix reference to diff-font-lock-syntax in diff-mode documentation
Date: Sun, 14 Mar 2021 02:32:44 +0100 [thread overview]
Message-ID: <m1ft0yr03n.fsf@yahoo.es> (raw)
In-Reply-To: m1ft0yr03n.fsf.ref@yahoo.es
[-- Attachment #1: Type: text/plain, Size: 92 bytes --]
Here's a small patch that fixes an incomplete variable reference in the
Diff Mode manual.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-reference-to-diff-font-lock-syntax-in-diff-mode-.patch --]
[-- Type: text/x-patch, Size: 913 bytes --]
From 0b185a206e0d96e0fa0033cf3377ba24d6501f5f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Mart=C3=ADn?= <mardani29@yahoo.es>
Date: Sun, 14 Mar 2021 02:25:53 +0100
Subject: [PATCH] Fix reference to diff-font-lock-syntax in diff-mode
documentation
---
doc/emacs/files.texi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index 6b3bc430d9..912980b688 100644
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -1670,8 +1670,9 @@ Diff Mode
(``new'') source files.
@vindex diff-font-lock-syntax
- If non-@code{nil}, fragments of source in hunks are highlighted
-according to the appropriate major mode.
+ If @code{diff-font-lock-syntax} is non-@code{nil}, fragments of
+source in hunks are highlighted according to the appropriate major
+mode.
@node Copying and Naming
@section Copying, Naming and Renaming Files
--
2.28.0
next parent reply other threads:[~2021-03-14 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1ft0yr03n.fsf.ref@yahoo.es>
2021-03-14 1:32 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-14 6:04 ` bug#47129: [PATCH] Fix reference to diff-font-lock-syntax in diff-mode documentation Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1ft0yr03n.fsf@yahoo.es \
--to=bug-gnu-emacs@gnu.org \
--cc=47129@debbugs.gnu.org \
--cc=mardani29@yahoo.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.