Friday, November 22, 2024

command line – Unknown locale, assuming C – Error message in terminal

Word: The query is just not about tips on how to change the locale, or what’s the locale. The query is about why is there a locale-based error in man in 10.3, however no error in 12.6, regardless that the locales are an identical in each circumstances.


After working man, studying a guide entry and shutting it, I obtain the next error

$ man curl                     # The guide opens, I learn it, then shut
Unknown locale, assuming C
$ man zsh                      # The guide opens, I learn it, then shut
Unknown locale, assuming C

The guide pages work accurately, and will be browsed, however I don’t know the place the error comes from, and it’s reasonably annoying.

That is what I acquire when working locale

$ locale
LANG=""
LC_COLLATE="C"
LC_CTYPE="UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=

I am utilizing Ventura 13.0. The identical error doesn’t occur in 12.6 regardless that the locale is an identical (see beneath), so I don’t suppose that it is a matter with locale, however reasonably a difficulty with man.

Word that locale says

   LANG         Used as an alternative choice to any unset LC_* variable.     
If LANG is unset, it is going to act as if set to "C".  If any of LANG or    
LC_* are set to invalid values, locale acts as if they're all unset.

so there ought to be no error, LANG ought to be routinely set to C.

EDIT:

Some new perception. I ran the identical instructions on two computer systems.

Pc 1 runs 13.0 outputs the error.
This laptop has man for MacOS 13.0 from January 9 2021.

Pc 2 runs 12.6 and outputs no error.
This laptop has man model 1.6g from September 19 2005.

The output of the locale command is totally an identical on each computer systems, specifically they each have LC_CTYPE="UTF-8".

Might or not it’s a man bug?

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles