From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 35885@debbugs.gnu.org, 42199@debbugs.gnu.org
Subject: bug#42199: bug#35885: 25.2; Few mistakes in Emacs Manual (+ proposals)
Date: Tue, 18 May 2021 15:15:46 +0200 [thread overview]
Message-ID: <87eee4gp31.fsf@gnus.org> (raw)
In-Reply-To: <a11f688d-2292-757a-5771-7322dbe8455c@gmail.com> (Sebastian Urban's message of "Tue, 18 May 2021 11:17:08 +0200")
Sebastian Urban <mrsebastianurban@gmail.com> writes:
>> Perhaps copy-pasting explanation from SCREEN.TEXI would be a better
>> solution, i.e. instead of
>> (which is ``control h and then t'')
>> something like this:
>> (hold down @key{Control} and type @kbd{h}, then let go of
>> @key{Control} and type @kbd{t})
>> ?
>
> If it's necessary, I'll open a new bug report.
Please do.
> I also believe it is now possible to close this bug report:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42199
> I mean at least the Emacs manual part is done.
OK; done.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-05-18 13:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 15:59 bug#35885: 25.2; Few mistakes in Emacs Manual (+ proposals) Sebastian Urban
2019-06-02 22:50 ` Sebastian Urban
2019-06-03 16:36 ` Eli Zaretskii
2019-06-04 10:48 ` Sebastian Urban
2019-06-04 15:12 ` Eli Zaretskii
2019-06-05 10:40 ` Sebastian Urban
2019-06-05 16:52 ` Eli Zaretskii
2019-06-06 9:49 ` Sebastian Urban
2019-06-06 21:19 ` Sebastian Urban
2019-06-09 8:31 ` Eli Zaretskii
2019-06-09 8:22 ` Eli Zaretskii
2019-06-10 10:30 ` Sebastian Urban
2019-06-10 17:01 ` Eli Zaretskii
2019-06-11 10:32 ` Sebastian Urban
2019-06-11 16:59 ` Eli Zaretskii
2019-06-12 8:44 ` Sebastian Urban
2019-06-12 13:25 ` Drew Adams
2019-06-03 16:32 ` Eli Zaretskii
2020-05-10 20:02 ` Sebastian Urban
2020-08-13 9:11 ` Sebastian Urban
2020-08-13 13:20 ` Eli Zaretskii
2020-08-13 14:06 ` Sebastian Urban
2020-08-13 14:16 ` Eli Zaretskii
2020-08-14 0:01 ` Sebastian Urban
2020-08-15 13:18 ` Lars Ingebrigtsen
2020-08-15 13:34 ` Eli Zaretskii
2020-08-15 13:52 ` Lars Ingebrigtsen
2020-08-15 14:11 ` Sebastian Urban
2020-08-16 11:16 ` Lars Ingebrigtsen
2020-08-16 13:00 ` Sebastian Urban
2020-08-18 14:54 ` Lars Ingebrigtsen
2020-08-18 15:07 ` Eli Zaretskii
2020-08-19 10:15 ` Lars Ingebrigtsen
2020-08-19 8:44 ` Sebastian Urban
2020-08-19 10:19 ` Lars Ingebrigtsen
2020-08-19 12:14 ` Sebastian Urban
2020-08-20 12:44 ` Lars Ingebrigtsen
2020-08-20 13:35 ` Eli Zaretskii
2020-08-20 18:24 ` Sebastian Urban
2020-08-22 7:20 ` Eli Zaretskii
2020-08-22 10:19 ` Sebastian Urban
2020-10-19 18:52 ` Sebastian Urban
2021-05-12 14:47 ` Lars Ingebrigtsen
2021-05-13 11:48 ` Sebastian Urban
2021-05-16 13:30 ` Lars Ingebrigtsen
2021-05-18 9:17 ` Sebastian Urban
2021-05-18 13:15 ` Lars Ingebrigtsen [this message]
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=87eee4gp31.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=35885@debbugs.gnu.org \
--cc=42199@debbugs.gnu.org \
--cc=mrsebastianurban@gmail.com \
/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).