getCurrentBlockRange issues

[pfitzseb]

Most of this is technically correct behaviour, but still unexpected in the context of inline evaluation. It's possible we need two versions of this, one for inline evaluation and one that's actually "correct".

---

1+1;| returns an empty range but should give 1+1; instead.

---

|1+1

returns [[0,0], [1,0]] instead of [[1,0], [1,3]], but only when 1+1 is the first expr in the file.

---

|  1+1

returns an empty range but should instead give the whole line.

[jkrumbiegel]

I just recently found out that this is the reason why sometimes way more than I thought is executed with alt+enter. In Juno placing the cursor at the end of a block works, in VSCode it just takes the whole page

[pfitzseb]

That particular issue is fixed in 0.16.7, afaict.

[jkrumbiegel]

Oh that's nice, it seems you're right

[pfitzseb]

It would also be nice to return the next expression, even if there's no current expression. Not sure how feasible that is though.

[ZacLN]

So the additions sought are:

1. Return preceding expression when the cursor is on a semicolon
2. Return current expression when at the front of the first character (bug)
3. Return the next expression when in whitespace at the start of a line
   ?

[pfitzseb]

Yes.
3. is tricky though because it should only happen when we didn't find any other valid expression (like an indented block).