Code block syntax for editor plugin

[mathiasbredholt]

I started working on a sapf plugin for neovim, that works in a similar manner as scnvim.

The plugin spawns sapf in the background and allows evaluating the current selection in a vim buffer.

I came across a question which is, what defines the start and end of a code block that should be evaluated? In SC we have the (). But is there an equivalent in sapf?

Should such a plugin evaluate the innermost function only or perhaps search outwards until we find a line that doesn't begin with \[ or ]?

My initial implementation uses the indentation to detect blocks but it would be better to use the language syntax.

[salkin-mada]

I am using _- and -_ for now in my plugin. Have also been using ( and ) which actually worked fine for "block" evaluation. And been thru <` >` and other variants :-)

[mathiasbredholt]

I am using _- and -_ for now in my plugin. Have also been using ( and ) which actually worked fine for "block" evaluation. And been thru <` >` and other variants :-)

Cool, are they part of the sapf syntax or are you just ignoring those symbols before passing to sapf?

Would be nice to agree on something that also works for the examples.

[lfnoise]

The REPL evaluates line by line unless you are inside of a string, parentheses, a lambda, an array, or a form.
I would use parens for a selectable code group, but the examples file does not put parens around the examples. That could be done though.

[mathiasbredholt]

The REPL evaluates line by line unless you are inside of a string, parentheses, a lambda, an array, or a form.
I would use parens for a selectable code group, but the examples file does not put parens around the examples. That could be done though.

Parentheses then! Would be nice if the examples used parentheses IMHO.

[mathiasbredholt]

The REPL evaluates line by line unless you are inside of a string, parentheses, a lambda, an array, or a form.
I would use parens for a selectable code group, but the examples file does not put parens around the examples. That could be done though.

Parentheses then! Would be nice if the examples used parentheses IMHO.

Or I could just accept both parentheses and functions (with no indentation) as blocks in my plugin. Parentheses around functions doesn't really help readability IMO.