We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow removal of values from a cell formula in order to allow user to quickly correct a mistyped expense.
Example: cell contains =1+2+3 and 2 is to be removed; final result would be =1+3
=1+2+3
2
=1+3
This should also work with single value cells, of course - e.g. cell with value 3 should become empty if such expense is removed.
3
Whenever the value to be removed belongs to a product operation - e.g. value 3 in =1+2+3*2 - its multiples should be decremented i.e. =1+2+3*1
=1+2+3*2
=1+2+3*1
The text was updated successfully, but these errors were encountered:
In order for this feature to be successfully executed (and not confused with #8) it must use a new argument
e.g. add_expense --remove 3 99.99 should make formula =1+2+3+4+5+6+7+99.99 into =1+2+3+4+5+6+7
add_expense --remove 3 99.99
=1+2+3+4+5+6+7+99.99
=1+2+3+4+5+6+7
Also, for the sake of numeric comparison, all numbers should be properly compared to currency (2 decimal places)
e.g. add_expense --remove 1 3.00 should still make formula =1+2+3+4+5+6+7 into =1+2+4+5+6+7
add_expense --remove 1 3.00
=1+2+4+5+6+7
Sorry, something went wrong.
No branches or pull requests
Allow removal of values from a cell formula in order to allow user to quickly correct a mistyped expense.
Example: cell contains
=1+2+3
and2
is to be removed; final result would be=1+3
This should also work with single value cells, of course - e.g. cell with value
3
should become empty if such expense is removed.Whenever the value to be removed belongs to a product operation - e.g. value
3
in=1+2+3*2
- its multiples should be decremented i.e.=1+2+3*1
The text was updated successfully, but these errors were encountered: