linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marko Myllynen <myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH] locale.1: minor output format clarification
Date: Fri, 12 Jun 2015 16:31:53 +0300	[thread overview]
Message-ID: <557ADF49.40303@redhat.com> (raw)

Hi Michael,

a minor clarification for the locale output format which was brought up
at https://sourceware.org/bugzilla/show_bug.cgi?id=18516.

------

For reference, see

https://sourceware.org/bugzilla/show_bug.cgi?id=18516
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/locale.html
---
 man1/locale.1 | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/man1/locale.1 b/man1/locale.1
index 1bd233e..19cf13e 100644
--- a/man1/locale.1
+++ b/man1/locale.1
@@ -45,6 +45,8 @@ displays the current locale settings for each locale category (see
 based on the settings of the environment variables that control the locale
 (see
 .BR locale (7)).
+Values for variables set in the environment are printed without double 
+quotes, implied values are printed with double quotes.
 
 If either the
 .B \-a

Thanks,

-- 
Marko Myllynen
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2015-06-12 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 13:31 Marko Myllynen [this message]
     [not found] ` <557ADF49.40303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-12 18:18   ` [PATCH] locale.1: minor output format clarification Michael Kerrisk (man-pages)

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=557ADF49.40303@redhat.com \
    --to=myllynen-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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. 
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 NNTP newsgroup(s).