Hi David,
> Where would you use it? Why not just drop 12-hour times?
> I don't think I've ever formatted a 12-hour time on a computer (unless you
> want to count the example quoted below).
>
Yup, pretty much when we "send" time info to some when it is not life
foce-to-face using a 12-hour clock
> And the only solution to Zeno's Paradox that I've been able to identify
> relies on the notion that space and time are not infinitely
> subdivisible.
Really? I thought the solution is that while the distance is divided at
each step, the time between each step is also divided, so you end up
perf
>> >> It seems intuitively obvious to me that between 11:59 Ante-Meridiem and
>> >> 12:01 Post-Meridiem must lie 12:00 Meridiem. (Though 12:00:01 - one
>> >> second later - would be Post-Meridiem again.)
In my interpretation of this part of the world, it's never exactly noon
nor exactly midnight:
On 2019-09-13 at 12:05, Greg Wooledge wrote:
> On Fri, Sep 13, 2019 at 10:44:42AM -0500, David Wright wrote:
>
>> But time is continuous.
>
> Maybe. Quantum mechanics still holds some secrets we haven't
> learned.
And the only solution to Zeno's Paradox that I've been able to identify
relies o
On 2019-09-13 at 11:50, David Wright wrote:
> On Thu 12 Sep 2019 at 23:14:52 (-0400), The Wanderer wrote:
>
>> On 2019-09-12 at 21:49, David Wright wrote:
>>> I don't see a need for a one-letter abbreviation for midnight, nor the
>>> wisdom in introducing one that's already used in the same conte
On Fri, Sep 13, 2019 at 10:44:42AM -0500, David Wright wrote:
> But time is continuous.
Maybe. Quantum mechanics still holds some secrets we haven't learned.
On Thu 12 Sep 2019 at 23:14:52 (-0400), The Wanderer wrote:
> On 2019-09-12 at 21:49, David Wright wrote:
> > On Thu 12 Sep 2019 at 12:42:01 (-0400), The Wanderer wrote:
> >> On 2019-09-12 at 12:03, David Wright wrote:
>
> >>> It might be ambiguous if m were also an abbreviation for midnight,
> >>
On Thu 12 Sep 2019 at 22:16:45 (-0500), John Hasler wrote:
> David Wright writes:
> > Odd that they decided to employ that logic in the 21st century after
> > (most) clocks had ceased to tick.
>
> All clocks tick. "Tick" no longer means "emit a noise once per second"
> in modern chronometry.
Th
The Wanderer writes:
>Why do people abbreviate "AM" and "PM" when speaking out loud?
They don't know what AM and PM are abbreviations of. They think of AM
and PM as words. But I'm referring to abreviations for "noon" and
"midnight", which take less time to say than "12 PM" and "12 AM", or
even "
John Hasler wrote:
> All clocks tick. "Tick" no longer means "emit a noise once per second"
> in modern chronometry.
+1
The clock frequency is produced by oscillator at 32.768kHz which means that
15 flops at this frequency produce 1sec. This is one tick.
On 2019-09-12 at 23:20, John Hasler wrote:
> The Wanderer writes:
>
>> Wherever you need to specify midnight in a form where specifying any
>> other time would get the "AM"/"PM"/"M"(eridiem) abbreviation.
>
>> To have a two-letter abbreviation for midnight but a one-letter one
>> for noon might b
The Wanderer writes:
> Wherever you need to specify midnight in a form where specifying any
> other time would get the "AM"/"PM"/"M"(eridiem) abbreviation.
> To have a two-letter abbreviation for midnight but a one-letter one
> for noon might be acceptable, although it would feel lopsided to me,
>
David Wright writes:
> Odd that they decided to employ that logic in the 21st century after
> (most) clocks had ceased to tick.
All clocks tick. "Tick" no longer means "emit a noise once per second"
in modern chronometry.
> But it is remarkable to use logic to prove a contradiction...
What con
On 2019-09-12 at 21:49, David Wright wrote:
> On Thu 12 Sep 2019 at 12:42:01 (-0400), The Wanderer wrote:
>
>> On 2019-09-12 at 12:03, David Wright wrote:
>>> It might be ambiguous if m were also an abbreviation for midnight,
>>> which I've never come across.
>>
>> Neither have I, but I also hav
On Thu 12 Sep 2019 at 14:13:19 (-0500), John Hasler wrote:
> rhkramer writes:
> > If 12:01 pm is two minutes after 11:59 am, then 12:00 is AM.
>
> AM means "before the meridian", that is, before the Sun crosses the
> meridian[1]. PM means after the meridian. Time is the ordering of
> events. Th
On Thu 12 Sep 2019 at 12:42:01 (-0400), The Wanderer wrote:
> On 2019-09-12 at 12:03, David Wright wrote:
> > On Thu 12 Sep 2019 at 09:42:03 (-0400), The Wanderer wrote:
> >> On 2019-09-12 at 06:30, Dan Ritter wrote:
>
> >>> There is only one sensible interpretation:
> >>>
> >>> If 11:59 AM is tw
rhkramer writes:
> If 12:01 pm is two minutes after 11:59 am, then 12:00 is AM.
AM means "before the meridian", that is, before the Sun crosses the
meridian[1]. PM means after the meridian. Time is the ordering of
events. The Sun crossing the meridian is an event which we call noon:
everything
On 2019-09-12 at 12:03, David Wright wrote:
> On Thu 12 Sep 2019 at 09:42:03 (-0400), The Wanderer wrote:
>
>> On 2019-09-12 at 06:30, Dan Ritter wrote:
>>> There is only one sensible interpretation:
>>>
>>> If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.
>>>
>>> If 11:59 PM is tw
On Thursday, September 12, 2019 08:26:23 AM Nate Bargmann wrote:
> Not all Walmarts are like that. ;-)
>
> The one in Beatrice, NE is as you describe, at least the north most
> entrance. The ones in Marysviile, KS and Fairbury, NE are "normal",
> i.e. ingress on the right when outside the store
On Thursday, September 12, 2019 08:09:18 AM Michael Stone wrote:
> The railroads solved this more than a century ago: you just never use
> 12:00 and stick with 11:59 or 12:01. Sometimes communicating clearly is
> more important than being right.
I like that (but getting everyone to adhere to that
On Thu 12 Sep 2019 at 09:42:03 (-0400), The Wanderer wrote:
> 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 ei
On Thu 12 Sep 2019 at 13:48:07 (-), Curt wrote:
> 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
>
On Thu, Sep 12, 2019 at 01:48:07PM -, Curt wrote:
> 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
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
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
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
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
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]
* 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
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,
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
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
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
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
> >>
> >> As an example:
> >>
> >> Tue Sep 10 19:5
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
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
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
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 a script
> is relying
Am Mittwoch, 11. September 2019, 13:57:37 CEST schrieb Michael Stone:
> 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
On 2019-09-11 at 07:57, Michael Stone wrote:
> 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:
>>> https://www.mail-archive.com/debian-user@lists.debian.org/msg741032.html
>>
>> Many thanks for all the
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
>
> As an
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
>>>
>>> As an example:
>>>
>>> Tue Sep 10 19:50:26 CEST 2019 (stre
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:26 CEST 2019 (stretch)
>> Tue 10 Sep 2019 09:26:33 PM CEST
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:
> >
> > Tue Sep 10 19:50:26 CEST 2019 (stre
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)
>
> I am just wondering if this is a k
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 is
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 i
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
48 matches
Mail list logo
