Author Topic: Cursor moved to end of file after choosing compatible function parameter  (Read 1055 times)

rowbearto

  • Senior Community Member
  • Posts: 1620
  • Hero Points: 119
Look for compatible_auto.tar.gz on support.

Follow instructions in the README file.

It reproduced with a clean config.

Used RC2, Linux x64, CentOS 7.2

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1252
  • Hero Points: 119
Re: Cursor moved to end of file after choosing compatible function parameter
« Reply #1 on: October 18, 2018, 07:05:32 pm »
This is fixed for the next build/first hotfix.

rowbearto

  • Senior Community Member
  • Posts: 1620
  • Hero Points: 119
Re: Cursor moved to end of file after choosing compatible function parameter
« Reply #2 on: October 18, 2018, 07:09:00 pm »
Wow, that was fast! Was it already fixed by the time I reported it?

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1252
  • Hero Points: 119
Re: Cursor moved to end of file after choosing compatible function parameter
« Reply #3 on: October 18, 2018, 07:19:58 pm »
Yes.  It's actually the same root cause as the dynamic surround/completion problem.  Essentially, a recent change causes us to feed invalid source ranges to the beautifier for completion/syntax expansion.  Most of the time this is harmless, beyond forcing the beautifier to process more source than is necessary for a given source snippet.  But some ranges violate some beautifier invariants for snippets, causing it to miscalculate new positions for the stream markers used by hotspots, dynamic surround, auto bracket, and also the cursor.