From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: 69341@debbugs.gnu.org
Subject: bug#69341: 30.0.50; [PATCH] Fix control char in docstring
Date: Sat, 24 Feb 2024 09:07:13 +0200 [thread overview]
Message-ID: <86wmquz6fy.fsf@gnu.org> (raw)
In-Reply-To: <m2r0h2yht9.fsf@macmutant.fritz.box> (message from Arash Esbati on Fri, 23 Feb 2024 22:46:58 +0100)
> From: Arash Esbati <arash@gnu.org>
> Date: Fri, 23 Feb 2024 22:46:58 +0100
>
> Hi all,
>
> this is a small change fixing an unwanted control char in docstring of
> `reftex-cite-format-builtin':
>
> --8<---------------cut here---------------start------------->8---
> diff --git a/lisp/textmodes/reftex-vars.el b/lisp/textmodes/reftex-vars.el
> index a0bc5c11ece..791b10412c9 100644
> --- a/lisp/textmodes/reftex-vars.el
> +++ b/lisp/textmodes/reftex-vars.el
> @@ -235,11 +235,10 @@ reftex-cite-format-builtin
> "ConTeXt bib module"
> ((?\C-m . "\\cite[%l]")
> (?s . "\\cite[][%l]")
> - (?n . "\\nocite[%l]")))
> - )
> + (?n . "\\nocite[%l]"))))
> "Builtin versions of the citation format.
> The following conventions are valid for all alist entries:
> -`?\C-m' should always point to a straight \\cite{%l} macro.
> +`?\\C-m' should always point to a straight \\cite{%l} macro.
> `?t' should point to a textual citation (citation as a noun).
> `?p' should point to a parenthetical citation.")
> --8<---------------cut here---------------end--------------->8---
>
> I can install this myself, release branch I presume?
At this point, fixes should be installed on the release branch only if
they are very important, or if they are in documentation parts.
AFAIU, this one is neither, so master, please.
Thanks.
next prev parent reply other threads:[~2024-02-24 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 21:46 bug#69341: 30.0.50; [PATCH] Fix control char in docstring Arash Esbati
2024-02-24 7:07 ` Eli Zaretskii [this message]
2024-02-24 8:41 ` Arash Esbati
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=86wmquz6fy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69341@debbugs.gnu.org \
--cc=arash@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 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).