diff options
src/calendar.c: Fix range check in calendar_move()
We added count prefix support to motion commands in commit
59e006e56d9f893506af56a4ca114fe53b537e49 but obviously forgot to check
whether the range checks in calendar_move() still work correctly.
Refactor out range checks and replace them by a single check that is
performed *after* the new date is computed, but before we assign the new
value to the actual selected date. This ensures we won't have to bother
about these again when changing/adding functionality in/to
calendar_move(), while keeping performance (date_change() is pretty
cheap and range violations are corner cases anyway).
Signed-off-by: Lukas Fleischer <calcurse@cryptocrack.de>
Diffstat (limited to 'test%252525252525253fid%252525252525253d9cba56ac0ae9d8e6d58b8d5d645dfbca58321e0b%2525252525253fid%2525252525253de66e2d4277998094ee58ebd7c9455507df303939%25252525253fid%25252525253de66e2d4277998094ee58ebd7c9455507df303939%252525253fid%252525253de66e2d4277998094ee58ebd7c9455507df303939%2525253fid%2525253de66e2d4277998094ee58ebd7c9455507df303939%25253fid%25253de66e2d4277998094ee58ebd7c9455507df303939%253fid%253de66e2d4277998094ee58ebd7c9455507df303939&id2%253d7a230fa76a5a0f5ada7b6afd2c42b2f99a549569%3fid%3de66e2d4277998094ee58ebd7c9455507df303939?id=7a230fa76a5a0f5ada7b6afd2c42b2f99a549569')
0 files changed, 0 insertions, 0 deletions