Adrien,

Who are you asking to provide an example?
My point was that the manual editing method that you suggested couldn't be
used if the existing descriptions must be kept.
In my data file that is often the case.
I agree that there is a lot of 'noise' in the drop down list of suggestions
caused by searching existing transactions to populate this list.

I think that such a list would best be populated from an independent table
which would be entirely new to GnuCash.  It could be called 'Payees' and it
should be independent for each account.



On Tue, Jun 6, 2023 at 10:07 AM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:

> How would you envision this would work in a case where you want to edit
> an existing transaction that has a description which you've removed from
> the list for new transactions? Since every transaction as it is being
> entered is a 'new' transaction, where does this cutoff happen?
>
> Maybe an example could illustrate this use case?
>
>
> Regards,
> Adrien
>
> On 6/6/23 9:32 AM, David Carlson wrote:
> > The problem with the solution that Adrien suggests is that there is a
> real
> > possibility that the existing descriptions may be correct for existing
> > transactions but inappropriate for new transactions.  I think there is no
> > solution as long as the current method is used to populate the list, so
> we
> > must live with it.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> 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.
>


-- 
David Carlson
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
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.

Reply via email to