Org-Mode dates are limited to dates from 1970 to 2037 why is that?

Just noticed, when adding a timestamp of the time my mother was born that org-mode wouldn't let me insert a date prior to 1970. Why is that? Also, should I be worried that org-mode dates will end at 2037? Is Emacs going to end? What will happen to the world in 2037?

the global warming will destroy us u.u that's the end of the world

the global warming will destroy us u.u that's the end of the world

Must be using a 32-bit integer. A signed 32-bit integer holds up to 2^31 - 1 If you start time then in 1970 as unix time and you store time as seconds since 1970, then your 32-bit integer overflows in 2037.

You have to run M-x-stop-ww3 from the extinction package on melpa and it should work for years after 2037

Funny enough, `M-x stop-ww3` is an alias for `M-x start-civilwar2`

From the manual: Not all dates can be represented in a given Emacs implementation. By default Org mode forces dates into the compatibility range 1970–2037 which works on all Emacs implementations. If you want to use dates outside of this range, read the docstring of the variable ‘org-read-date-force-compatible-dates’.

https://en.wikipedia.org/wiki/Year_2038_problem

I just use (setq ussr-implodes t)

The Unix epoch starts in 1970 and time is calculated as an integer offset from there. The climate change will probably kill us all before 2037 so there shouldn't be a problem.

According to **M-x doctor**: >Should I be worried that org-mode dates will end at 2037? > >Are you worried often?

Yeah, I remember having a hard time when I tried to use timestamps for historical documents for a research. I'm sure there was some way to fix it, but I couldn't stop what I was doing, so I ended up saving the data outside of emacs (the horror!)

At least you aren't hearing about the y2k bug

Solution- https://blog.emacsos.com/org-mode-schedule-a-date-after-2038.html

This is Y2K all over again

Frightening thing is this is only 15 years away. Closer than we are now to Y2K.