From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: checkdoc doc fix
Date: Thu, 01 Nov 2018 12:27:17 -0700 [thread overview]
Message-ID: <877ehwlht6.fsf@ericabrahamsen.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 87 bytes --]
Very meta.
Can I apply doc fixes to the release branch without checking first?
Eric
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Doc-fix-for-checkdoc-continue.patch --]
[-- Type: text/x-patch, Size: 1221 bytes --]
From b957d2bf54bd24022da49e79078ea87162a08b9c Mon Sep 17 00:00:00 2001
From: Eric Abrahamsen <eric@ericabrahamsen.net>
Date: Thu, 1 Nov 2018 12:18:15 -0700
Subject: [PATCH] Doc fix for checkdoc-continue
* lisp/emacs-lisp/checkdoc.el (checkdoc-continue): There is no second
optional argument, and the function always starts from point.
---
lisp/emacs-lisp/checkdoc.el | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/lisp/emacs-lisp/checkdoc.el b/lisp/emacs-lisp/checkdoc.el
index 83929beb1e..86d211c729 100644
--- a/lisp/emacs-lisp/checkdoc.el
+++ b/lisp/emacs-lisp/checkdoc.el
@@ -884,9 +884,8 @@ checkdoc-start
;;;###autoload
(defun checkdoc-continue (&optional take-notes)
"Find the next doc string in the current buffer which has a style error.
-Prefix argument TAKE-NOTES means to continue through the whole buffer and
-save warnings in a separate buffer. Second optional argument START-POINT
-is the starting location. If this is nil, `point-min' is used instead."
+Prefix argument TAKE-NOTES means to continue through the whole
+buffer and save warnings in a separate buffer."
(interactive "P")
(let ((wrong nil) (msg nil)
;; Assign a flag to spellcheck flag
--
2.19.1
next reply other threads:[~2018-11-01 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 19:27 Eric Abrahamsen [this message]
2018-11-01 19:47 ` checkdoc doc fix Eli Zaretskii
2018-11-01 20:21 ` Eric Abrahamsen
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=877ehwlht6.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
/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.