Re: Default date output format changed after an upgrade to buster

On 2019-09-12, Greg Wooledge wrote: > On Wed, Sep 11, 2019 at 07:31:13PM -0500, David Wright wrote: >> Even more astonishing is the fact that the US Government switched >> their am/pm meanings sometime between 2000 and 2008, which shows >> just how ambiguous they are. > > [citation needed] > > ht

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

On Thu, Sep 12, 2019 at 09:42:03AM -0400, The Wanderer wrote: I take a slightly different approach, based on the apparent actual meanings of the words for which "AM" and "PM are abbreviations. It seems intuitively obvious to me that between 11:59 Ante-Meridiem and 12:01 Post-Meridiem must lie 12

24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

On 2019-09-12 at 06:30, Dan Ritter wrote: > David Wright wrote: >> >> What surprised me is the use of 12am and 12pm in the States. When I >> was at grammar school (in the days of 12hour times), you lost marks >> for writing either of these contradictions. It was either 12 noon, >> 12 midnight, or

Re: Default date output format changed after an upgrade to buster

On Thu 12 Sep 2019 at 06:30:21 (-0400), Dan Ritter wrote: > David Wright wrote: > > > > What surprised me is the use of 12am and 12pm in the States. When > > I was at grammar school (in the days of 12hour times), you lost > > marks for writing either of these contradictions. It was either > > 12

Re: Default date output format changed after an upgrade to buster

On Wed, Sep 11, 2019 at 07:31:13PM -0500, David Wright wrote: > Even more astonishing is the fact that the US Government switched > their am/pm meanings sometime between 2000 and 2008, which shows > just how ambiguous they are. [citation needed]

Re: Default date output format changed after an upgrade to buster

* On 2019 12 Sep 06:16 -0500, rhkra...@gmail.com wrote: > Now I consider establishments like Walgreens, Rite-Aid, Walmart, and others > to > be foreign infiltrators, as, when they have an In and an Out door side by > side, > the In is on the left. (Ok, Walmart is only a halfway foreign infiltr

Re: Default date output format changed after an upgrade to buster

On Thu, Sep 12, 2019 at 06:30:21AM -0400, Dan Ritter wrote: David Wright wrote: What surprised me is the use of 12am and 12pm in the States. When I was at grammar school (in the days of 12hour times), you lost marks for writing either of these contradictions. It was either 12 noon, 12 midnight,

Re: Default date output format changed after an upgrade to buster

On 2019-09-12, rhkra...@gmail.com wrote: > > But, ok, I'll try to burn that into my memory -- at night (when it is dark) > 12:00 (midnight) is the beginning of morning (12:00 am). During the day, > when > it is light 12:00 (noon) is the beginning of night (12:00 pm). > >> If 11:59 PM is two mi

Re: Default date output format changed after an upgrade to buster

On Thursday, September 12, 2019 06:30:21 AM Dan Ritter wrote: > David Wright wrote: > > Even more astonishing is the fact that the US Government switched > > their am/pm meanings sometime between 2000 and 2008, which shows > > just how ambiguous they are. Wow! I believe that, I just didn't realiz

Re: Default date output format changed after an upgrade to buster

David Wright wrote: > > What surprised me is the use of 12am and 12pm in the States. When > I was at grammar school (in the days of 12hour times), you lost > marks for writing either of these contradictions. It was either > 12 noon, 12 midnight, or 12 o'clock (where there's no ambiguity). 12 o'c

Re: Default date output format changed after an upgrade to buster

On Wed 11 Sep 2019 at 07:26:33 (-), Curt wrote: > On 2019-09-10, Sven Joachim wrote: > > On 2019-09-10 22:06 +0200, Rainer Dorsch wrote: > >> > >> after an upgrade from stretch to buster, the date default output changed > >> on my > >> system >

Re: Default date output format changed after an upgrade to buster

On Wednesday, September 11, 2019 09:14:19 AM Greg Wooledge wrote: > On Wed, Sep 11, 2019 at 09:07:10AM -0400, rhkra...@gmail.com wrote: > > On Wednesday, September 11, 2019 07:57:37 AM Michael Stone wrote: > > > those strings are expected to change depending on > > > things like locale settings, an

Re: Default date output format changed after an upgrade to buster

On Wed, Sep 11, 2019 at 09:07:10AM -0400, rhkra...@gmail.com wrote: Interesting! I have no argument with what you say, it makes perfect sense, but it must be one of those things that "goes without saying" -- I can't claim to be a Linux guru, but in the years I've spent with Linux and with a fair

Re: Default date output format changed after an upgrade to buster

On Wed, Sep 11, 2019 at 09:07:10AM -0400, rhkra...@gmail.com wrote: > On Wednesday, September 11, 2019 07:57:37 AM Michael Stone wrote: > > those strings are expected to change depending on > > things like locale settings, and are for humans to read, not programs. > > Interesting! I have no argum

Re: Default date output format changed after an upgrade to buster

On Wednesday, September 11, 2019 07:57:37 AM Michael Stone wrote: > apt-listchanges in what? If you run the stretch date on buster, you'll > get the same output. The change is that the localized string changed to > something more sensible and date uses the localized string. If

Re: Default date output format changed after an upgrade to buster

e: > >> > after an upgrade from stretch to buster, the date default output > >> > changed > >> > on my system > >> > > >> > As an example: > >> > > >> > Tue Sep 10 19:50:26 CEST 2019 (stretch) > >> > Tue 10

Re: Default date output format changed after an upgrade to buster

g yet. So I think the suggestion would have been that either the changelog or the NEWS entry from the Debian-packaged version of glibc which first included the patch which makes this change should have had a comment pointing out that the default date format for this common locale would change. >

Re: Default date output format changed after an upgrade to buster

On Wed, Sep 11, 2019 at 08:36:49AM +0200, Rainer Dorsch wrote: Am Dienstag, 10. September 2019, 22:52:03 CEST schrieb Greg Wooledge: On Tue, Sep 10, 2019 at 10:06:37PM +0200, Rainer Dorsch wrote: > after an upgrade from stretch to buster, the date default output changed > on my system >

Re: Default date output format changed after an upgrade to buster

On 2019-09-11, Curt wrote: > On 2019-09-10, Sven Joachim wrote: >> On 2019-09-10 22:06 +0200, Rainer Dorsch wrote: >> >>> Hi, >>> >>> after an upgrade from stretch to buster, the date default output changed on >>> my >>> system

Re: Default date output format changed after an upgrade to buster

On 2019-09-10, Sven Joachim wrote: > On 2019-09-10 22:06 +0200, Rainer Dorsch wrote: > >> Hi, >> >> after an upgrade from stretch to buster, the date default output changed on >> my >> system >> >> As an example: >> >> Tue Sep 10 19:50:

Re: Default date output format changed after an upgrade to buster

Am Dienstag, 10. September 2019, 22:52:03 CEST schrieb Greg Wooledge: > On Tue, Sep 10, 2019 at 10:06:37PM +0200, Rainer Dorsch wrote: > > after an upgrade from stretch to buster, the date default output changed > > on my system > > > > As an example: > >

Re: Default date output format changed after an upgrade to buster

On 2019-09-10 22:06 +0200, Rainer Dorsch wrote: > Hi, > > after an upgrade from stretch to buster, the date default output changed on my > system > > As an example: > > Tue Sep 10 19:50:26 CEST 2019 (stretch) > Tue 10 Sep 2019 09:26:33 PM CEST (buster) > >

Re: Default date output format changed after an upgrade to buster

On Tue, Sep 10, 2019 at 10:06:37PM +0200, Rainer Dorsch wrote: after an upgrade from stretch to buster, the date default output changed on my system As an example: Tue Sep 10 19:50:26 CEST 2019 (stretch) Tue 10 Sep 2019 09:26:33 PM CEST (buster) I am just wondering if this is a known

Re: Default date output format changed after an upgrade to buster

On Tue, Sep 10, 2019 at 10:06:37PM +0200, Rainer Dorsch wrote: > after an upgrade from stretch to buster, the date default output changed on > my > system > > As an example: > > Tue Sep 10 19:50:26 CEST 2019 (stretch) > Tue 10 Sep 2019 09:26:33 PM CEST (buster)

Default date output format changed after an upgrade to buster

Hi, after an upgrade from stretch to buster, the date default output changed on my system As an example: Tue Sep 10 19:50:26 CEST 2019 (stretch) Tue 10 Sep 2019 09:26:33 PM CEST (buster) I am just wondering if this is a known issue or if another configuration change during the upgrade

Re: Date format for Thunderbird 60.7 -- partial success in changing it

Thank you Greg for the clarification. I find your third link https://wiki.debian.org/DotFiles very worth reading. Regards, Jörg Greg Wooledge wrote on 05/06/2019 14:52: > On Wed, Jun 05, 2019 at 11:18:55AM +0200, Jörg-Volker Peetz wrote: >> As user of thunderbird you best set the environment vari

Re: Date format for Thunderbird 60.7 -- partial success in changing it

On Wed, Jun 05, 2019 at 11:18:55AM +0200, Jörg-Volker Peetz wrote: > As user of thunderbird you best set the environment variable LC_TIME in your > profile, e.g. via ~/.bash_profile . Check it with the command > > $ locale > > You have to log out (from desktop and from computer) before changes in

Re: Date format for Thunderbird 60.7 -- partial success in changing it

As user of thunderbird you best set the environment variable LC_TIME in your profile, e.g. via ~/.bash_profile . Check it with the command $ locale You have to log out (from desktop and from computer) before changes in .bash_profile get applied. Regards, Jörg.

Re: Date format for Thunderbird 60.7 -- partial success in changing it

On 2019-06-05, Ken Heard wrote: > > The latest version of Thunderbird for Debian Stretch, 70.7 which I now > use, still allows only the US date format, MM-DD-, but for me at > least expresses the time as HH:MM (24 hour clock). In a partially > successful attempt to change th

Date format for Thunderbird 60.7 -- partial success in changing it

The latest version of Thunderbird for Debian Stretch, 70.7 which I now use, still allows only the US date format, MM-DD-, but for me at least expresses the time as HH:MM (24 hour clock). In a partially successful attempt to change the date format I did the following. 1. Ran update-locales

Re: ISO 8601 Date/Time format in future Debian versions

On Wed 29 May 2019 at 01:00:27 (+0200), Garret Robinson wrote: > It is extremely frustrating to have different time/date formats scattered > throughout one's operating system. If you say so. I find different formats appropriate in different circumstances. For example, my screen clock

ISO 8601 Date/Time format in future Debian versions

It is extremely frustrating to have different time/date formats scattered throughout one's operating system. Even when one modifies one's Region & Language for an international standard (e.g., by setting en_US.UTF-8 as default but editing the LC_TIME section to copy en_

Re: date(1) in stretch and buster

On Wed 10 Apr 2019 at 13:26:39 (+0200), Vincent Lefevre wrote: > On 2019-04-09 13:28:40 -0500, David Wright wrote: > > On Tue 09 Apr 2019 at 15:38:43 (+0200), Vincent Lefevre wrote: > > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > > stretch$ TZ=UTC date > &

Re: date(1) in stretch and buster

On 2019-04-09 13:28:40 -0500, David Wright wrote: > On Tue 09 Apr 2019 at 15:38:43 (+0200), Vincent Lefevre wrote: > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > stretch$ TZ=UTC date > > > Mon Apr 8 15:22:02 UTC 2019 > > > buster$ TZ=UTC date &

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 20:07:37 (-), Curt wrote: > On 2019-04-09, Étienne Mollier wrote: > > > > The output may differ depending on you operating system level, > > given Reco's observations. Feel free to have à look at > > /usr/share/zoneinfo/, to have an idea of the available > > locations. >

Re: date(1) in stretch and buster

On 2019-04-09, Étienne Mollier wrote: > > The output may differ depending on you operating system level, > given Reco's observations. Feel free to have à look at > /usr/share/zoneinfo/, to have an idea of the available > locations. I took a look. I was confused to note the presence of the UCT z

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 14:55:37 (-0400), Greg Wooledge wrote: > On Tue, Apr 09, 2019 at 01:28:40PM -0500, David Wright wrote: > > My question about the OP's issue is whether I'm going to have to > > change something to keep what I get in jessie and stretch, or is > > this just a temporary bug in bus

Re: date(1) in stretch and buster

imes or anything else. > > You mean, like this ? > > $ TZ=Zulu date > Tue Apr 9 18:46:20 UTC 2019 Yes, but only Zulu works here, not Z, nor all the rest. But we were using it as the shortest unambiguous representation of the timezone we were currently sailing in, suitab

Re: date(1) in stretch and buster

On Tuesday 09 April 2019 14:39:19 David Wright wrote: > On Tue 09 Apr 2019 at 14:03:08 (-0400), Gene Heskett wrote: > > On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > > stretch$ TZ=UTC date > &

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 03:11:27PM -0400, Gene Heskett wrote: The point I was trying to make Mike, is, if thats to be a std, its an extremely obtuse way of writing that std. Consequently I suspect it will be 100% ignored. And folks will continue to muddle along just fine. :) It reads fine to me

Re: date(1) in stretch and buster

On Tuesday 09 April 2019 14:28:18 Michael Stone wrote: > On Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote: > >On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > >> On 2019-04-08 18:26:23 +0300, Reco wrote: > >> > stretch$ TZ=UTC date >

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 01:28:40PM -0500, David Wright wrote: > My question about the OP's issue is whether I'm going to have to > change something to keep what I get in jessie and stretch, or is > this just a temporary bug in buster. Or has the US format been > wrong all along? (As an expat, I'm u

Re: date(1) in stretch and buster

On 4/9/19 8:39 PM, David Wright wrote: > We avoided the problem when I went to sea by using the letter codes, > Z(ulu), A(lpha), B(ravo) etc. because there are no civil timezones, > daylight savings times or anything else. You mean, like this ? $ TZ=Zulu date Tue Apr 9

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 14:03:08 (-0400), Gene Heskett wrote: > On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > stretch$ TZ=UTC date > > > Mon Apr 8 15:22:02 UTC 2019 > > > buster$ TZ=UTC date &

Re: date(1) in stretch and buster

if your offset is -4 or +4, etc. Maintainers of `tzdata` handle that for you (a great "Thank You!" to these people by the way). Usually, people in my neighborhood would use the equivalent of the following, for instance: $ TZ=Europe/Paris LC_TIME=fr_FR.UTF-8 date mardi 9 a

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 15:38:43 (+0200), Vincent Lefevre wrote: > On 2019-04-08 18:26:23 +0300, Reco wrote: > > stretch$ TZ=UTC date > > Mon Apr 8 15:22:02 UTC 2019 > > buster$ TZ=UTC date > > Mon 08 Apr 2019 03:22:04 PM UTC > > This is unrelated to your issue, bu

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote: On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: On 2019-04-08 18:26:23 +0300, Reco wrote: > stretch$ TZ=UTC date > Mon Apr 8 15:22:02 UTC 2019 > buster$ TZ=UTC date > Mon 08 Apr 2019 03:22:04 PM UTC This is

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote: > Yikes. Can that be actually put into English? "Use date -u instead."

Re: date(1) in stretch and buster

On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > On 2019-04-08 18:26:23 +0300, Reco wrote: > > stretch$ TZ=UTC date > > Mon Apr 8 15:22:02 UTC 2019 > > buster$ TZ=UTC date > > Mon 08 Apr 2019 03:22:04 PM UTC > > This is unrelated to your issue, but note

Re: date(1) in stretch and buster

On 2019-04-08 18:26:23 +0300, Reco wrote: > stretch$ TZ=UTC date > Mon Apr 8 15:22:02 UTC 2019 > buster$ TZ=UTC date > Mon 08 Apr 2019 03:22:04 PM UTC This is unrelated to your issue, but note that the correct TZ string for UTC is "UTC0", not "UTC". See http

Re: date(1) in stretch and buster

ate_fmt variable inside the LC_TIME section. So first, I logged into a stretch box and found what it was using: stretch:~$ locale -k LC_TIME | grep date_fmt date_fmt="%a %b %e %H:%M:%S %Z %Y" Next, I edited the ~/.locale/src/en_US file and replaced the date_fmt line. BEFORE: % Approp

Re: date(1) in stretch and buster

Cindy-Sue Causey, on 2019-04-08 : > Found this over at Tecmint: > > https://www.tecmint.com/set-system-locales-in-linux/ > > locale -k LC_TIME > > Very coo AND further implies *WHAT ELSE can that little puppy do*, but > my brain's already cognitively sundowning so am passing the baton on > for some

Re: date(1) in stretch and buster

Hi. On Mon, Apr 08, 2019 at 07:10:50PM +0200, Étienne Mollier wrote: > > My question is - can anyone suggest me appropriate LC_TIME setting that > > can show buster's date in stretch's format? > > $ LC_TIME=en_US.UTF-8 TZ=UTC date >

Re: date(1) in stretch and buster

Hi, Cindy Sue Causey wrote: > I'd like mine to be in the '2009.04.08' format. $ date +'%Y.%m.%d' 2019.04.08 Have a nice day :) Thomas

Re: date(1) in stretch and buster

On 4/8/19, Étienne Mollier wrote: > On 4/8/19 5:26 PM, Reco wrote: >> Dear list, >> >> the following thing got my attention recently: >> >> stretch$ TZ=UTC date >> Mon Apr 8 15:22:02 UTC 2019 >> buster$ TZ=UTC date >> Mon 08 Apr 2019 03:2

Re: date(1) in stretch and buster

On 4/8/19 5:26 PM, Reco wrote: > Dear list, > > the following thing got my attention recently: > > stretch$ TZ=UTC date > Mon Apr 8 15:22:02 UTC 2019 > buster$ TZ=UTC date > Mon 08 Apr 2019 03:22:04 PM UTC > > It's not that I depend on certain date for

date(1) in stretch and buster

Dear list, the following thing got my attention recently: stretch$ TZ=UTC date Mon Apr 8 15:22:02 UTC 2019 buster$ TZ=UTC date Mon 08 Apr 2019 03:22:04 PM UTC It's not that I depend on certain date format in scripts, but I got used to this 24-hour time format after all these years

Re: Display full date in Thunderbird

On 06/24/2018 11:56 PM, Ken Heard wrote: How do I get Thunderbird to use the same format for dates/times more than a week old? You need to use the config editor to create/edit mail.ui.display.dateformat.today, mail.ui.display.dateformat.thisweek, and mail.ui.display.dateformat.default as In

Re: Display full date in Thunderbird

On Mon, Jun 25, 2018 at 05:36:55PM +0200, Sven Joachim wrote: > On 2018-06-24 23:56 -0400, Ken Heard wrote: > > > I start Thunderbird with the following script: > > > > #! /bin/bash > > export LC_TIME=en_DK.utf8 && thunderbird "$@" > > > > For emails sent or received today only the time is shown,

Re: Display full date in Thunderbird

On 2018-06-24 23:56 -0400, Ken Heard wrote: > I start Thunderbird with the following script: > > #! /bin/bash > export LC_TIME=en_DK.utf8 && thunderbird "$@" > > For emails sent or received today only the time is shown, e.g., 13:17. > For emails sent or received more than a week ago, the year, mon

Display full date in Thunderbird

I start Thunderbird with the following script: #! /bin/bash export LC_TIME=en_DK.utf8 && thunderbird "$@" For emails sent or received today only the time is shown, e.g., 13:17. For emails sent or received more than a week ago, the year, month, day and time are shown, e.g., 2018-06-13 07:43. F

Re: postfix "delivery-date" - how to?

Dan Ritter writes: [...] > but I think you want in-message headers. So you need a filter > that can insert one cleanly. My conclusions are the same (and another solution: lmtp, because it would be put into dovecot accessed mailboxes) > I'm not sure why you want to do all this, though, becaus

Re: postfix "delivery-date" - how to?

On Tue, Apr 24, 2018 at 08:38:39PM +0200, Kamil Jońca wrote: > > Exim has a nice feature: it puts "Delivery-date" header when terminates > delivery to pipe/mailbox. > > Is it posible with postfix? It is possible, not necessarily convenient. Here's ho

postfix "delivery-date" - how to?

Exim has a nice feature: it puts "Delivery-date" header when terminates delivery to pipe/mailbox. Is it posible with postfix? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Down with categorical imperative!

coreutils date behavior (buggy) (was: Re: policy around 'wontfix' bug tag)

On 2018-02-06 13:07:53 -0300, Lucas Castro wrote: > Em 06-02-2018 10:38, Vincent Lefevre escreveu: > > On 2018-02-06 13:48:19 +0100, Vincent Lefevre wrote: > > > This is completely crazy: > > > > > > zira% date +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month&

coreutils date behavior (buggy) (was: Re: policy around 'wontfix' bug tag)

On 2018-02-06 09:01:58 -0500, rhkra...@gmail.com wrote: > Just an attempt to get a more informative subject line--maybe > somebody can improve it. Corrected the subject. This is not related to bash at all (I'm under zsh, BTW). The GNU date utility comes from the coreutils. > On Tue

bash date behavior (buggy) (was: Re: policy around 'wontfix' bug tag)

gt; Anyway, here's what I came up with: > > > > > > lastday() { > > > > > > date +%Y-%m-%d -d "$1 1 day ago + 1 month" > > > > > > } > > > > But the exact meaning of "month" seems undocumented, which ma

Re: Systemtap out of date and not working

Hi. On Sat, Dec 23, 2017 at 04:09:56PM -0500, Farhan Khan wrote: > Hi all, > > SystemTap on Debian is version 2.9/0.165. Not unless you're running pre-stretch testing. stretch's current is 3.1. >The current version is 3.2. Maybe. > SystemTap works by compiling a custom kernel module a

Systemtap out of date and not working

Hi all, SystemTap on Debian is version 2.9/0.165. The current version is 3.2. SystemTap works by compiling a custom kernel module against the source and installing it. However, the kernel structure has since updated and Systemtap 2.9 will not compile against newer kernels. As a result, SystemTap

Re: KDE Plasma Date & Time Format

On 09/19/2017 08:35 AM, Dominique Dumont wrote: On Monday, 18 September 2017 15:59:22 CEST Jimmy Johnson wrote: In KDE4 I use the long date with the short day: "Mon, September 19, 2017". Is there an easy way to do this in Plasma5? Even better would be long date with short day and s

Re: KDE Plasma Date & Time Format

On Monday, 18 September 2017 15:59:22 CEST Jimmy Johnson wrote: > In KDE4 I use the long date with the short day: "Mon, September 19, 2017". > Is there an easy way to do this in Plasma5? Even better would be long > date with short day and short month: "Mon, Sep 19, 2017&qu

KDE Plasma Date & Time Format

In KDE4 I use the long date with the short day: "Mon, September 19, 2017". Is there an easy way to do this in Plasma5? Even better would be long date with short day and short month: "Mon, Sep 19, 2017" Is there a config file I can edit? I have spent my day looking at

Re: How to change date and time format for quoting in Thunderbird?

Mario Castelán Castro wrote: > When replying to a message in Thunderbird as packaged in Debian 9, the > date and time is automatically placed before the quote, like this: “On > 22/08/17 17:31, $NAME wrote:”. How can I change the format used for the > date and time? http://kb.moz

Re: How to change date and time format for quoting in Thunderbird?

On 25/08/17 15:41, Byung-Hee HWANG (황병희, 黃炳熙) wrote: > "lambda.alex.chromebook" is my chromebook's system-name. The others is > https://raw.githubusercontent.com/soyeomul/Gnus/MaGnus/thanks-mid.rb.message-id I do not understand. -- Do not eat animals, respect them as you respect people. https://

Re: How to change date and time format for quoting in Thunderbird?

Dear Mario, In Article <71bb9099-1dac-7567-3aeb-4c1c0ecd8...@yandex.com>, Mario Castelán Castro writes: > I see you are using the “Message-id” field. This is not at all useful > for humans. "lambda.alex.chromebook" is my chromebook's system-name. The others is https://raw.githubusercontent.com

Re: How to change date and time format for quoting in Thunderbird?

On 25/08/17 07:36, Byung-Hee HWANG (황병희, 黃炳熙) wrote: > In Article <3af44f03-ebc9-473c-2d77-36961f66d...@yandex.com>, >> When replying to a message in Thunderbird as packaged in Debian 9, the >> date and time is automatically placed before the quote, like this: “On >>

Re: How to change date and time format for quoting in Thunderbird?

In Article <3af44f03-ebc9-473c-2d77-36961f66d...@yandex.com>, Mario Castelán Castro writes: > When replying to a message in Thunderbird as packaged in Debian 9, the > date and time is automatically placed before the quote, like this: “On > 22/08/17 17:31, $NAME wrote:”. How c

How to change date and time format for quoting in Thunderbird?

When replying to a message in Thunderbird as packaged in Debian 9, the date and time is automatically placed before the quote, like this: “On 22/08/17 17:31, $NAME wrote:”. How can I change the format used for the date and time? In addition, I want to change the format of $NAME to include his e

Re: Adding Date & Time to a script's output log

On Thu, 1 Jun 2017, Greg Wooledge wrote: On Thu, Jun 01, 2017 at 06:49:58PM +, david...@freevolt.org wrote: If you go this convenient-lexical-order route, note that %F is shorthand for %Y-%m-%d Not portable. See Whoa

Re: Adding Date & Time to a script's output log

ng list, but there's no compelling reason to use an obtuse %F option that you'd have to rewrite for other systems when it doesn't increase readability over %Y-%m-%d which everyone can easily understand. Fun with non-Debian systems: imadev:~$ date +%F June imadev:~$ gdate +%F 2

Re: Adding Date & Time to a script's output log

On Thu, 1 Jun 2017, Nicolas George wrote: Le tridi 13 prairial, an CCXXV, SUZANNE COBB a écrit : I try to capture the date and time into a variable named 'dt': dt= $(date '+%d/%m/%Y %H:%M:%S'); Note that %T is shorthand for %H:%M:%S [please see there is a space

Re: Adding Date & Time to a script's output log

On Thu, Jun 01, 2017 at 03:24:05PM +, Ron Leach wrote: > People are so generous with their time. > > I hadn't realised that spaces were sometimes semantically relevant. (And I > liked Nicolas's detox joke, well done.) > In all computer languages, the presence or absence of a space is usual

Re: Adding Date & Time to a script's output log

, not she. Many thanks, again, regards, Ron - Original Message - From: SUZANNE COBB To: Debian Users Sent: Thu, 01 Jun 2017 14:26:00 - (UTC) Subject: Adding Date & Time to a script's output log List, good afternoon, I am using a script to check and update a dynamic IP addres

Re: Adding Date & Time to a script's output log

On Thu, 01 Jun 2017, SUZANNE COBB wrote: > I try to capture the date and time into a variable named 'dt': > > dt= $(date '+%d/%m/%Y %H:%M:%S'); > > echo "%dt" "Changed ${DYN_DOMAIN} from ${registeredIp} to ${externalIp}" >>

Re: Adding Date & Time to a script's output log

Le tridi 13 prairial, an CCXXV, SUZANNE COBB a écrit : > I try to capture the date and time into a variable named 'dt': > > dt= $(date '+%d/%m/%Y %H:%M:%S'); > > [please see there is a space between = and $, and between Y and %] Well, fix it! This line execu

Re: Adding Date & Time to a script's output log

On Thu, Jun 01, 2017 at 02:26:00PM +, SUZANNE COBB wrote: > I try to capture the date and time into a variable named 'dt': > > dt= $(date '+%d/%m/%Y %H:%M:%S'); > > [please see there is a space between = and $, and between Y and %] The space after = is

Re: Adding Date & Time to a script's output log

On Thu 01 Jun 2017 at 14:26:00 (+), SUZANNE COBB wrote: > List, good afternoon, > > I am using a script to check and update a dynamic IP address in our DNS > records. I have tried to add a date and time output to a log file which > records IP address changes and updates - b

Adding Date & Time to a script's output log

List, good afternoon, I am using a script to check and update a dynamic IP address in our DNS records. I have tried to add a date and time output to a log file which records IP address changes and updates - but the change I inserted is not working. I think the problem is that I have not

RE: How to set ISO date/time with en_US.utf8 as system default?

eric system, etc to be United States locale? Changing the GNOME format changes EVERY variable to whatever that country is set to (not necessarily what that country uses, what that country's file is set to). I live in the United States, and wouldn't you know it, some of us use internati

RE: How to set ISO date/time with en_US.utf8 as system default?

7 18:22 To: debian-user@lists.debian.org Subject: Re: How to set ISO date/time with en_US.utf8 as system default? On 2017-05-30 08:46, Greg Wooledge wrote: > > Perhaps a GNOME-specific mailing list might have more options for you. > Maybe there's some way to tell GNOME not to touch t

Re: How to set ISO date/time with en_US.utf8 as system default?

On 2017-05-30 08:46, Greg Wooledge wrote: Perhaps a GNOME-specific mailing list might have more options for you. Maybe there's some way to tell GNOME not to touch the locale settings *at all*, and simply let them pass through from the underlying operating system. Yes, I have switched to taki

Re: How to set ISO date/time with en_US.utf8 as system default?

On Sat, May 27, 2017 at 08:33:16AM -0400, gwmf...@openmailbox.org wrote: > I want to make everything proper and swapping to all en_DK variables > fixes some things but not others. The only proper solution is to: > > 1) be able to change individual variables within Gnome (which I don't > think is

Re: How to set ISO date/time with en_US.utf8 as system default?

On Sat 27 May 2017 at 17:39:48 (+0200), Nicolas George wrote: > L'octidi 8 prairial, an CCXXV, gwmf...@openmailbox.org a écrit : > > […] > […] > In this matter, considerations such as "preserving local cultures" are > irrelevant. An astonishing juxtaposition! > Convenience sets a few rules. The

Re: How to set ISO date/time with en_US.utf8 as system default?

On 2017-05-27, Curt wrote: > On 2017-05-27, gwmf...@openmailbox.org wrote: >>> >>> Define "appears to not be working." Anyhow, I believe someone here can >>> help you with this if only they'll pipe up (and you stop top-posting). >>> >>> ;-) >> >> "Top-posting" is putting my writing above the qu

Re: How to set ISO date/time with en_US.utf8 as system default?

> "g" == gwmfms6 writes: g> You are correct. typing locale in the virtual (text) console produces g> LC_TIME=en_DK. So GNOME is overriding PAM's environment. g> Thank you so much for helping me discover this! I learned a lot in the g> process. Did you re-start gdm after editing the files i

Re: How to set ISO date/time with en_US.utf8 as system default?

On Saturday, May 27, 2017 11:39:03 AM Curt wrote: > Normally, you should "interleave" your responses, trimming the material > not pertinent to your reply. +1 > I say this because bottom-posting (like bottom-fishing--well, not > precisely) in which the poster quotes (following others of his ilk)

Re: How to set ISO date/time with en_US.utf8 as system default?

On 2017-05-27 11:39, Nicolas George wrote: L'octidi 8 prairial, an CCXXV, gwmf...@openmailbox.org a écrit : A lot of Europe does it, and it is wrong! It goes back quite a while to when it was fashionable to use a dot (.) as a symbol for multiplication. So Europe stopped using a dot to signal a

Re: How to set ISO date/time with en_US.utf8 as system default?

On Sat, 27 May 2017, at 16:24, gwmf...@openmailbox.org wrote: > A lot of Europe does it, and it is wrong! It goes back quite a while to > when it was fashionable to use a dot (.) as a symbol for multiplication. I don't think it's a straightforward as that. Mathematics (at university level) use

Re: How to set ISO date/time with en_US.utf8 as system default?

L'octidi 8 prairial, an CCXXV, gwmf...@openmailbox.org a écrit : > A lot of Europe does it, and it is wrong! It goes back quite a while to when > it was fashionable to use a dot (.) as a symbol for multiplication. So > Europe stopped using a dot to signal a decimal point to avoid confusion > (they

Re: How to set ISO date/time with en_US.utf8 as system default?

On 2017-05-27, gwmf...@openmailbox.org wrote: >> >> Define "appears to not be working." Anyhow, I believe someone here can >> help you with this if only they'll pipe up (and you stop top-posting). >> >> ;-) > > "Top-posting" is putting my writing above the quote? this is frowned > upon? (or you

<    1   2   3   4   5   6   7   8   9   10   >