Another one unhappy with quickfill

John Layman john.layman at
Mon Jan 17 16:44:42 EST 2011

I run into this same problem with quickfill, but there IS a way to avoid
quickfill's autiomatic  reproduction of a split: do not tab out of the
description field!  Once quickfill completes the 'Description' field, simply
click directly on the 'Transfer' field and enter the account (or split) in
the normal fashion.

-----Original Message-----
From: gnucash-user-bounces at
[mailto:gnucash-user-bounces at] On Behalf Of TFC Mail Admin
Sent: Sunday, January 16, 2011 11:19 PM
To: gnucash-user at
Subject: Another one unhappy with quickfill

I've been using GnuCash for about 3 years - it is a great product, and
immeasurably superior to Quicken! However, I agree that while quirkfill (I
liked the Freudian slip) is generally useful, in certain cases it can be
more of a problem than a help.

My Gripe!
One of my most numerous transactions is the purchase of groceries. 
Occasionally (one a month?) I also pay a utility at the supermarket - so
then I have a split - but the other 99 transactions I capture for the
supermarket do not have a split!
So (unfortunately) 99 times out of a hundred I have to delete the split that
GnuCash has remembered (very conveniently - and I am not being sarcastic).
For the other 150+? types of transaction I enter, quickfill makes life very
easy & fast!

So, it would be nice if there was a way to 'lock' a transaction template in
quickfill, or be able to delete it's history.

Oweson Flynn
> Message: 1
> Date: Sun, 16 Jan 2011 12:37:16 -0500
> From: Paul Abrahams<abrahams at>
> Subject: Another one unhappy with quickfill
> To: gnucash-user at
> Message-ID:<201101161237.16714.abrahams at>
> Content-Type: text/plain;  charset="us-ascii"
> Derek asked, "What is it about quickfill that you don't like?"  Well, 
> sometimes it will create a split transaction because I once had one 
> but don't want one any longer.  And filling in a  split when it really 
> isn't one is a lot of unnecessary work.  Even making the split go away is
unnecessary labor.
> I can understand the arguments for quickfill, but what I don't 
> understand is why it isn't optional, given that many people dislike 
> it.  It shouldn't be that difficult to do.
> ------------------------------
> Message: 2
> Date: Sun, 16 Jan 2011 12:04:01 -0600
> From: "Linde B."<linde.brocato at>
> Subject: Re: Another one unhappy with quickfill
> To: gnucash-user at
> Message-ID:
> 	<AANLkTiniSyhaZrMZvAFUYEqcHa1Nmw9KvvVvFQyHidRs at>
> Content-Type: text/plain; charset=ISO-8859-1
> I agree that quick fill should be optional.  Mostly it annoys me, esp.
> when entering a transaction that shares initial letters or the first 
> word.  I suspect that such features for "ease" also make for mental 
> sloppiness and errors of another order.
> Linde

gnucash-user mailing list
gnucash-user at
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 mailing list