selinger at mathstat.dal.ca
Thu Jan 6 12:32:50 EST 2011
Yes, it looks like that is not going to break in 2100. It seems that
GnuCash interprets 1/1/62 as 01/01/1962, and 12/31/61 as 12/31/2061.
So it probably has a rule to go at most 50 years into the future (from
the end of the current year), and else into the past. I imagine this
window slies by 1 year every year.
What I am looking for is a similar sliding rule for months within the
year, e.g., if the year is not specified, go up to 4 months into the
future or 8 month into the past. (I am more likely to enter past
transactions than future ones).
If it doesn't exist yet, I'd be happy to attempt a patch. -- Peter
Bob Plantz wrote:
> One of the things I've learned is that you can enter just the last two
> digits of the year (10 or 11), which saves a little effort. I'm not
> worried about this possibly breaking in 2100. :-)
> On 1/5/2011 4:31 PM, Peter Selinger wrote:
> > A question I always mean to ask this time of year: is there a way to
> > change the default date completion behavior of GnuCash?
> > Today is January 5, 2011. If I enter a transaction with an incomplete
> > date, such as 12/30, GnuCash automatically enters this as 12/30/2011,
> > which is what I want in 0% of cases.
> > Conversely, last week, when I entered the date 1/5 last week, GnuCash
> > recorded this as 01/05/2010.
> > As a result, around the turn of the year, I constantly have to enter
> > full dates, which is inconvenient.
> > I checked the preferences and could not find a setting for changing
> > this behavior. Is there one?
> > Thanks, -- Peter
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
More information about the gnucash-user