On 25/12/19 11:53, Ed Greshko wrote:
On 2019-12-25 08:26, Doug McGarrett wrote:
On 12/24/2019 06:58 PM, Bob Goodwin wrote:
On 2019-12-24 18:40, Ed Greshko wrote:
What is LC_TYPE?.
Something from my subconscious apparently ...
LC_TIME="C" works and I get 24 hour time after rebooting.
On 2019-12-25 07:58, Bob Goodwin wrote:
>
> On 2019-12-24 18:40, Ed Greshko wrote:
>> What is LC_TYPE?.
>
> Something from my subconscious apparently ...
>
> LC_TIME="C" works and I get 24 hour time after rebooting.
>
> Thank you
>
You were probably thinking of "LC_CTYPE". But that has to do
Hello Ed,
On Wed, 25 Dec 2019 07:40:23 +0800 Ed Greshko wrote:
> On 2019-12-25 07:24, Bob Goodwin wrote:
> >
> > On 2019-12-24 17:56, Ed Greshko wrote:
> >> It sounds as if you're not running with the environment variable LC_TIME=C.
> >>
> >> What does the followng LONG command string
On 2019-12-25 08:26, Doug McGarrett wrote:
>
>
> On 12/24/2019 06:58 PM, Bob Goodwin wrote:
>>
>> On 2019-12-24 18:40, Ed Greshko wrote:
>>> What is LC_TYPE?.
>>
>> Something from my subconscious apparently ...
>>
>> LC_TIME="C" works and I get 24 hour time after rebooting.
>>
>> Thank you
>>
On 12/24/2019 06:58 PM, Bob Goodwin wrote:
On 2019-12-24 18:40, Ed Greshko wrote:
What is LC_TYPE?.
Something from my subconscious apparently ...
LC_TIME="C" works and I get 24 hour time after rebooting.
Thank you
I'd like to have 24 hour time also but this theme has confused me.
On 2019-12-25 08:07, Samuel Sieb wrote:
> On 12/24/19 3:40 PM, Ed Greshko wrote:
>> OK, why did you not enter the command as I typed it? It would have avoided
>> any issues of what the PID is.
>>
>> Anyway, the PID is 1652 but your next command is wrong
>>
>> It should have been
>>
>>
On 12/24/19 3:40 PM, Ed Greshko wrote:
OK, why did you not enter the command as I typed it? It would have avoided any
issues of what the PID is.
Anyway, the PID is 1652 but your next command is wrong
It should have been
cat /proc1652/environ | grep "LC_TIME=[Cc]" ; echo $?
You
On 12/24/19 3:24 PM, Bob Goodwin wrote:
[bobg@Workstation-2 ~]$ ps ax | grep thunderbird
1652 ? Sl 0:50 /usr/lib64/thunderbird/thunderbird
2431 pts/1 S+ 0:00 grep --color=auto thunderbird
[bobg@Workstation-2 ~]$ cat /proc/$1652/environ | grep "LC_TIME=[Cc]" ;
echo $?
On 2019-12-24 18:40, Ed Greshko wrote:
What is LC_TYPE?.
Something from my subconscious apparently ...
LC_TIME="C" works and I get 24 hour time after rebooting.
Thank you
--
Bob Goodwin - Zuni, Virginia,
Fedora Linux-31 XFCE
___
users mailing
On 2019-12-25 07:24, Bob Goodwin wrote:
>
> On 2019-12-24 17:56, Ed Greshko wrote:
>> It sounds as if you're not running with the environment variable LC_TIME=C.
>>
>> What does the followng LONG command string return?
>>
>> xx=`pidof thunderbird` ; cat/proc/$xx/environ | grep "LC_TIME=[Cc]" ;
On 2019-12-24 17:56, Ed Greshko wrote:
It sounds as if you're not running with the environment variable LC_TIME=C.
What does the followng LONG command string return?
xx=`pidof thunderbird` ; cat/proc/$xx/environ | grep "LC_TIME=[Cc]" ; echo $?
-
.
Well I do have this which I hope runs
On 2019-12-25 04:22, Bob Goodwin wrote:
> On a new fedora 31 installed this week and updated i am unable to get
> Thunderbird-68.3.1 to display a message list using 24 hour time.
>
> The Date and Time Regional setting can not be changed from US English to und
> as expected. I've tried
On a new fedora 31 installed this week and updated i am unable to get
Thunderbird-68.3.1 to display a message list using 24 hour time.
The Date and Time Regional setting can not be changed from US English
to und as expected. I've tried downgrading Thunderbird, and rebooted the
system,
13 matches
Mail list logo
