Slightly smarter date parsing?
ajswest at mindspring.com
Mon Jan 8 18:16:10 EST 2007
On Mon, Jan 08, 2007 at 06:04:12PM -0500, David Hampton wrote:
> On Mon, 2007-01-08 at 08:26 -0800, Andrew Sackville-West wrote:
> > On Sun, Jan 07, 2007 at 03:09:34PM -0800, Thomas Bushnell BSG wrote:
> > > On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote:
> > > > I was putting my receipts in for the last half month or so recently
> > > > and noticed that I had to be careful to notice the year that the
> > > > receipts were in. When putting in 12/23 or similar, I didn't get
> > > > December 23, 2006, but December 23, 2007. I thought this should be
> > > > different, so I dove into the gnucash code and changed qof_scan_date
> > > > slightly to choose the last year for December if the current month is
> > > > January. The patch is attached.
> > >
> > > This behavior has also always annoyed me.
> > me too! but it only crops up once a year. How long after 1/1 are
> > people still entering 12/xx items? Granted, I routinely enter 50+
> Why not just type "xx[" to get the date you want? I.E. For 12/27 you
> would type the three characters "27[". A single number is assumed to be
> a day in the current month, and then the left bracket character
> decrements the month by one.
good question. ummm... <sheepish> 'cuz I didn't know about it
</sheepish>. What, me read docs? heh.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20070108/b76b60eb/attachment.bin
More information about the gnucash-devel