From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: What were the Emacs versions with dates limited to 1970 .. 2037 year range? Date: Sun, 12 Jun 2022 12:22:48 +0300 Message-ID: <83wndmutg7.fsf@gnu.org> References: <8735gaqm6i.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3366"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 12 11:24:10 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o0JpJ-0000mM-Rb for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 11:24:10 +0200 Original-Received: from localhost ([::1]:59812 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o0JpI-0005GC-31 for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Jun 2022 05:24:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49904) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0JoG-0004Us-94 for emacs-devel@gnu.org; Sun, 12 Jun 2022 05:23:04 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:43832) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0JoF-0000ke-VN; Sun, 12 Jun 2022 05:23:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=zs4dSupd10EJ2R5e8+WMzoEsJdPQ/d8wwNT8rK2aTwc=; b=RcZjgu5zlHnf KitbvrU0lJ9dqGkKcaT2YFAi395WvsmH/M9wkS7uiJqQN/pkDH9J4iYqequDykjECvhrbNtkwJLT0 JywXARMLww9LTGppADISOi7U5WMMgC//aeYVGIzZKSOwml/oWhNnmK+bE95BE5pljQDRcFbvMCD8G K9vEKdlt9Tntr5viUddiCUYamnO+RU6sgq+SdYlcovLWIIfQGLwHfHcPvflpGHBAJzXV9ilc69eWd XGQ4OK1L4TncufaUhIT7/aDdpg5s2ZxNYqRaJ9FdYnUDPMggMMqkh/1GkFVqNqvmXnXi9B6l02IES eRpqHOUF+wwEmQxsmSi4rA==; Original-Received: from [87.69.77.57] (port=2858 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o0JoF-0002FE-DU; Sun, 12 Jun 2022 05:23:03 -0400 In-Reply-To: <8735gaqm6i.fsf@localhost> (message from Ihor Radchenko on Sun, 12 Jun 2022 17:13:25 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291083 Archived-At: > From: Ihor Radchenko > Date: Sun, 12 Jun 2022 17:13:25 +0800 > > Org mode currently supports an old workaround for 32-bit year range > limitation: > > org-read-date-force-compatible-dates docstring: > > > Should date/time prompt force dates that are guaranteed to work in Emacs? > > > > Depending on the system Emacs is running on, certain dates cannot > > be represented with the type used internally to represent time. > > Dates between 1970-1-1 and 2038-1-1 can always be represented > > correctly. Some systems allow for earlier dates, some for later, > > some for both. One way to find out is to insert any date into an > > Org buffer, putting the cursor on the year and hitting S-up and > > S-down to test the range. > > The workaround has been introduced about 11 years ago. > > Could anyone tell if this issue is still present in Emacs 25 or newer or > maybe on some OS? Any 32-bit build of Emacs is potentially prone to this problem, depending on what time-related APIs it is using. If time_t is a 32-bit type, this problem will still exist.