From: "Stephen J. Eglen" <sje30@cam.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: Docstring fixes
Date: Sun, 26 Mar 2023 20:16:04 +0100 [thread overview]
Message-ID: <m2edpbwca4.fsf@cam.ac.uk> (raw)
In-Reply-To: <m2tty8lqqy.fsf@cam.ac.uk>
and a commit message.
org.el: Docstring fixes.
* lisp/org.el (org-hide-emphasis-markers)
(org-hide-macro-markers)
(org-pretty-entities-include-sub-superscripts): Follow elisp
convention for docstrings: 'Non-nil means ...'.
On Sat, Mar 25 2023, Stephen J. Eglen wrote:
> Some small docstring fixes to align with convention in Emacs for
> 'Non-nil means ...'
>
> Stephen
>
> diff --git a/lisp/org.el b/lisp/org.el
> index 4d12084d9..08a6f1a50 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -3600,13 +3600,13 @@ following symbols:
> (const :tag "Entities" entities))))
>
> (defcustom org-hide-emphasis-markers nil
> - "Non-nil mean font-lock should hide the emphasis marker characters."
> + "Non-nil means font-lock should hide the emphasis marker characters."
> :group 'org-appearance
> :type 'boolean
> :safe #'booleanp)
>
> (defcustom org-hide-macro-markers nil
> - "Non-nil mean font-lock should hide the brackets marking macro calls."
> + "Non-nil means font-lock should hide the brackets marking macro calls."
> :group 'org-appearance
> :type 'boolean)
>
> @@ -3618,7 +3618,7 @@ When nil, the \\name form remains in the buffer."
> :type 'boolean)
>
> (defcustom org-pretty-entities-include-sub-superscripts t
> - "Non-nil means, pretty entity display includes formatting sub/superscripts."
> + "Non-nil means pretty entity display includes formatting sub/superscripts."
> :group 'org-appearance
> :version "24.1"
> :type 'boolean)
next prev parent reply other threads:[~2023-03-26 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 16:49 Docstring fixes Stephen J. Eglen
2023-03-26 19:16 ` Stephen J. Eglen [this message]
2023-03-27 11:16 ` Ihor Radchenko
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=m2edpbwca4.fsf@cam.ac.uk \
--to=sje30@cam.ac.uk \
--cc=emacs-orgmode@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.