1. 10 Apr, 2016 2 commits
    • Benno Schulenberg's avatar
      search: avoid saving and restoring placewewant when bracket matching · 023fccb9
      Benno Schulenberg authored
      Now that findnextstr() no longer sets placewewant, we can can make
      a copy of the old value just where needed: when a bracket is found.
      023fccb9
    • Benno Schulenberg's avatar
      search: don't set placewewant when we are just iterating · ea4e9b31
      Benno Schulenberg authored
      In the innermost search loop, don't set placewewant, because this loop
      is also used for replacing and spell fixing, when we don't really want
      to be there: we are just passing through.  Not setting placewewant means
      we don't need to save and restore it in those passing-through routines.
      
      The value of placewewant is only relevant when doing cursor movement,
      which doesn't happen during replacing nor spell checking, so there is
      no need to keep placewewant up to date -- it is set when it matters:
      at the end of go_looking().
      ea4e9b31
  2. 08 Apr, 2016 1 commit
    • Benno Schulenberg's avatar
      searching: don't keep track of current_y, but calculate it at the end · 7ba356a6
      Benno Schulenberg authored
      Stop keeping track of the vertical screen position when searching for
      something.  If nothing is found, current_y doesn't change, and all the
      incrementing/decrementing was a waste of time.  If something is found
      and it is onscreen, it is easy to calculate the new current_y.  And if
      something is found and it is offscreen, then current_y is irrelevant,
      because we will be either centering the found occurrence (searching)
      or putting it on the top or bottom line (bracket matching).
      
      (The above does not take softwrapping into account, but neither did
      the old code, so this doesn't introduce any new bugs.)
      
      (Also, when the search wraps, and the viewport is away from head or
      tail of the file, and the found occurrence is within the viewport,
      then the incremented/decremented current_y would be way wrong, but
      this didn't have any adverse effects as far as I could tell.  It
      seems that current_y is irrelevant in most cases.)
      7ba356a6
  3. 07 Apr, 2016 1 commit
  4. 05 Apr, 2016 8 commits
  5. 04 Apr, 2016 7 commits
  6. 31 Mar, 2016 2 commits
  7. 30 Mar, 2016 5 commits
  8. 29 Mar, 2016 6 commits
  9. 28 Mar, 2016 4 commits
  10. 23 Mar, 2016 4 commits