public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkorb at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12054] New: too many behaviors depend upon LC_ALL
Date: Fri, 24 Sep 2010 21:35:00 -0000	[thread overview]
Message-ID: <20100924213532.12054.bkorb@gnu.org> (raw)

For years and years I've done "ls" with entries showing in ASCII order.
Recently (last few years), printers started printing past the end of
the page.  This is a new enhancement that I don't like very well.
Apparently, it comes back to glibc, "it tells us to use 290 mm page length".
I've tried LC_PAPER=en_US and LC_PAPER=letter, but that does not control
paper size.  Only LC_ALL does.  LC_ALL also controls how directories get
listed.  LC_ALL=en_US is totally brain damaged for "ls" and basically unusable.
It is all screwed up.  Please find a solution.  Misordered directories and/or
missing text on print outs is not a solution.

-- 
           Summary: too many behaviors depend upon LC_ALL
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper dot fsp at gmail dot com
        ReportedBy: bkorb at gnu dot org
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=12054

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2010-09-24 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 21:35 bkorb at gnu dot org [this message]
2010-09-25  2:24 ` [Bug libc/12054] " drepper dot fsp at gmail dot com

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=20100924213532.12054.bkorb@gnu.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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.
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).