unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Thierry Volpiatto <thievol@posteo.net>,
	70163@debbugs.gnu.org, schwab@linux-m68k.org,
	monnier@iro.umontreal.ca
Subject: bug#70163: 29.3; hexl-mode incorrect docstring
Date: Sat, 06 Apr 2024 12:52:06 +0000	[thread overview]
Message-ID: <87il0upsax.fsf@localhost> (raw)
In-Reply-To: <86jzla3h1g.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> Thanks, here some more places:
>>  ...
>> org-use-fast-todo-selection        => org.el
>> org-babel-no-eval-on-ctrl-c-ctrl-c => ob-core.el
>
> I fixed the first two, but IMO they are not really relevant to this
> bug: the functions are not autoloaded, so you don't see that "Uses a
> keymap..." blurb.
>
> As for the other two: they are in Org, so I leave it to the Org
> developers to DTRT.

`org-use-fast-todo-selection' and `org-babel-no-eval-on-ctrl-c-ctrl-c'
are also not autoloaded.

And I do not see how to use the proposed approach to them - they both
use \[...] in the first line of the docstring:

(defcustom org-babel-no-eval-on-ctrl-c-ctrl-c nil
  "\\<org-mode-map>\
Remove code block evaluation from the `\\[org-ctrl-c-ctrl-c]' key binding."

(defcustom org-use-fast-todo-selection 'auto
  "\\<org-mode-map>\
Non-nil means use the fast todo selection scheme with `\\[org-todo]'.

Moving \<org-mode-map> to the second line is thus not an option.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  parent reply	other threads:[~2024-04-06 12:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 15:02 bug#70163: 29.3; hexl-mode incorrect docstring Thierry Volpiatto
2024-04-03 15:50 ` Eli Zaretskii
2024-04-03 16:37   ` Andreas Schwab
2024-04-03 17:04     ` Thierry Volpiatto
2024-04-03 18:14       ` Eli Zaretskii
2024-04-04  5:47         ` Thierry Volpiatto
2024-04-04 12:18           ` Eli Zaretskii
2024-04-04 12:45             ` Andreas Schwab
2024-04-04 13:07               ` Eli Zaretskii
2024-04-04 13:20                 ` Andreas Schwab
2024-04-04 12:54             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 13:16               ` Andreas Schwab
2024-04-04 13:23               ` Eli Zaretskii
2024-04-04 13:37                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 18:41                   ` Thierry Volpiatto
2024-04-05  5:46                     ` Eli Zaretskii
2024-04-05  6:29                       ` Thierry Volpiatto
2024-04-06 10:46                         ` Eli Zaretskii
2024-04-06 11:27                           ` Thierry Volpiatto
2024-04-06 12:52                           ` Ihor Radchenko [this message]
2024-04-06 14:05                             ` Andreas Schwab
2024-04-06 14:15                               ` Eli Zaretskii
2024-04-06 15:05                                 ` Andreas Schwab
2024-04-06 15:27                                   ` Eli Zaretskii
2024-04-06 15:49                         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 16:16                           ` Eli Zaretskii
2024-04-06 20:01                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 20:21                               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07  5:29                               ` Eli Zaretskii
2024-04-07 14:48                                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 14:57                                   ` Eli Zaretskii
2024-04-07 16:07                                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 16:11                                       ` Eli Zaretskii
2024-04-03 17:04   ` Thierry Volpiatto

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=87il0upsax.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=70163@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@linux-m68k.org \
    --cc=thievol@posteo.net \
    /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).