From: Ricardo Wurmus <rekado@elephly.net>
To: Alex Kost <alezost@gmail.com>
Cc: 31652@debbugs.gnu.org
Subject: bug#31652: Use of ‘keymap’ vs. ‘layout’ in manual
Date: Wed, 30 May 2018 13:27:27 +0200 [thread overview]
Message-ID: <87y3g1pen4.fsf@elephly.net> (raw)
In-Reply-To: <87vab5tsx5.fsf@gmail.com>
Alex Kost <alezost@gmail.com> writes:
> Tobias Geerinckx-Rice (2018-05-30 05:49 +0200) wrote:
>
>> Guix,
>>
>> Grepping the manual for ‘keyboard layout’ will get you to section
>> 6.1.4.1 (setting the layout temporarily during installation using
>> loadkeys), but not 6.2.7.1 where you might learn about using
>> console-keymap-service to make the change permanent.
>>
>> This bug is a reminder to myself to replace at least one occurrence of
>> ‘keymap’ with the common term.
>
> Do you mean ‘layout’ is the common term? "man loadkeys" mentions
> "layout" only once, and "keymap" a lot.
>
> I think we can just put a reference to that section. Maybe like this:
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 09749b15e..02425e791 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -8418,7 +8418,9 @@ loadkeys dvorak
>
> See the files under @file{/run/current-system/profile/share/keymaps} for
> a list of available keyboard layouts. Run @command{man loadkeys} for
> -more information.
> +more information. After installing GuixSD, you can set your default
> +keyboard layout with @code{console-keymap-service} (@pxref{Base
> +Services}).
>
> @subsubsection Networking
This is fine. We should also consider adding more @cindex entries to
cover all terms that people might search for. The index should guide
people to the relevant places in the manual.
--
Ricardo
next prev parent reply other threads:[~2018-05-31 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 3:49 bug#31652: Use of ‘keymap’ vs. ‘layout’ in manual Tobias Geerinckx-Rice
2018-05-30 9:05 ` Alex Kost
2018-05-30 11:27 ` Ricardo Wurmus [this message]
2021-09-24 0:56 ` Sarah Morgensen
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=87y3g1pen4.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=31652@debbugs.gnu.org \
--cc=alezost@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 external index
https://git.savannah.gnu.org/cgit/guix.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.