X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 X-Received: by 10.49.81.240 with SMTP id d16mr2792739qey.26.1363260691738; Thu, 14 Mar 2013 04:31:31 -0700 (PDT) In-Reply-To: <51419398.9080200@wmc.eu> References: <51419398 DOT 9080200 AT wmc DOT eu> Date: Thu, 14 Mar 2013 07:31:31 -0400 Message-ID: Subject: Re: [closed] Intel FORTRAN time_and_date function returns UTC instead of local time From: Earnie Boyd To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, Mar 14, 2013 at 5:08 AM, Marten Jan de Ruiter wrote: > Today, the problems with the date_and_time function were gone. I have no > clue what solved the issue. I did not install upgrades from Cygwin. I did > not recompile the program. > Maybe a time shift issue? a.k.a. Daylight Savings Time > What I did differently, is that I have used the Cygwin Bash shell, the > Cygwin terminal and the Cygwin-X W-win server, and played around with the > options of the Cygwin Terminal. There is configuration page for Text > containing a font field, a field for font options, and a field for the > locale and character set. I have played a bit with the locale. Afterwards, I > noticed that my program now issues the correct time, even when the option is > restored to the (Default) setting it was in originally. I assume that this > playing around corrected the glitch, but the details escape me. > Maybe a coincidental effect of DST? > Still, a month ago, I also played around with setting the locale on the > command line in the Cygwin Bash login, and that did not resolve the issue; > so "playing around with the locale" is not the entire story. > > I am a bit unsatisfied that I do not know what clicked right under the hood > of Cygwin, but pragmatical enough to enjoy that the issue is gone. > Or maybe just hiding until November? -- Earnie -- https://sites.google.com/site/earnieboyd -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple