You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users will sometimes fat-finger entering an account, or prematurely press enter to accept the suggestion when categorizing bigger amounts of transactions. This experience is quite painful — remember which transaction was wrongly categorized and fix it in the output file as soon as it’s written.
This could be alleviated and be more user-friendly if there would be a way to [b]ack to last transaction input.
As I find this project immensely useful — thanks to all collaborators! — I’d really love to see this improvement.
The text was updated successfully, but these errors were encountered:
This is a good idea, I've done this several times myself and have gone the
route of manually editing my ledger file after the fact.
But being able to do it in reckon directly makes more sense.
I'll start looking at this.
Thanks
On Sat, Aug 14, 2021, 1:40 PM Dario Ernst ***@***.***> wrote:
Users will sometimes fat-finger entering an account, or prematurely press
enter to accept the suggestion when categorizing bigger amounts of
transactions. This experience is quite painful — remember which transaction
was wrongly categorized and fix it in the output file as soon as it’s
written.
This could be alleviated and be more user-friendly if there would be a way
to [b]ack to last transaction input.
As I find this project immensely useful — thanks to all collaborators! —
I’d really love to see this improvement.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#115>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAJHV6VZ77C7PF7MHFAK5DT43IERANCNFSM5CFNWDYA>
.
Users will sometimes fat-finger entering an account, or prematurely press enter to accept the suggestion when categorizing bigger amounts of transactions. This experience is quite painful — remember which transaction was wrongly categorized and fix it in the output file as soon as it’s written.
This could be alleviated and be more user-friendly if there would be a way to
[b]ack to last transaction
input.As I find this project immensely useful — thanks to all collaborators! — I’d really love to see this improvement.
The text was updated successfully, but these errors were encountered: