diff options
| author | Lukas Fleischer <calcurse@cryptocrack.de> | 2012-01-21 22:31:47 +0100 |
|---|---|---|
| committer | Lukas Fleischer <calcurse@cryptocrack.de> | 2012-01-21 23:06:12 +0100 |
| commit | 7a230fa76a5a0f5ada7b6afd2c42b2f99a549569 (patch) | |
| tree | 8656ff9e3d6dfa4368dff857589f2c0bfe765bff /test/Makefile.am%2525253fid%2525253d31b4c71eb2610471cb0598338f510633f407477f%25253fid%25253dd34e6502e91e9a301ce6b1c023adc881dbfe889c%253fid%253d9cba56ac0ae9d8e6d58b8d5d645dfbca58321e0b%3fid%3de66e2d4277998094ee58ebd7c9455507df303939?id=7a230fa76a5a0f5ada7b6afd2c42b2f99a549569 | |
| parent | a79a33e8f4da016e4ae42b061db8400337d5a580 (diff) | |
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/Makefile.am%2525253fid%2525253d31b4c71eb2610471cb0598338f510633f407477f%25253fid%25253dd34e6502e91e9a301ce6b1c023adc881dbfe889c%253fid%253d9cba56ac0ae9d8e6d58b8d5d645dfbca58321e0b%3fid%3de66e2d4277998094ee58ebd7c9455507df303939?id=7a230fa76a5a0f5ada7b6afd2c42b2f99a549569')
0 files changed, 0 insertions, 0 deletions