You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! First of all just want to say thanks for this plugin, it's been extremely helpful.
I'm currently building out a beancount file, and I'm interested in organizing my sections via indentation using org mode style headers. I've noticed some strange behavior in vs code related to the interplay between syntax highlighting and indentation. I've included two images here which showcase the issue.
This first image shows the issue with syntax highlighting when there is there is a newline + a tab separating the two option directives:
The second image shows that syntax highlighting works correctly when you add in one (or more) newlines between the option directives:
Has anyone else experienced the same issue? Or could this possibly be due to some local misconfiguration on my part?
The text was updated successfully, but these errors were encountered:
bam4564
changed the title
Region Folding Via Indentation Only Works With Extra Newlines
[bug] Region Folding Via Indentation Only Works With Extra Newlines
Oct 1, 2021
currently, an option directive must be followed by an empty newline, or a line starting with non-whitespace characters.
It is not hard to add syntax highlighting support to the code style in your first image, but beancount itself requires option directive lines start with no whitespaces. As I tested, bean-report complains syntax error, unexpected INDENT when there are spaces in front of option. Did you see similar errors?
As I tested, bean-report complains syntax error, unexpected INDENT when there are spaces in front of option. Did you see similar errors?
(not the original poster but...) Agreed I see the same error: syntax error, unexpected INDENT
That being said, as far as I can tell, this syntax error is the only thing that is broken from beancount. It's still able to parse the file and generate reports.
I'm curious whether those people controlling folding via indents (e.g. #15) have ignored these bean-check errors?
Hello! First of all just want to say thanks for this plugin, it's been extremely helpful.
I'm currently building out a beancount file, and I'm interested in organizing my sections via indentation using org mode style headers. I've noticed some strange behavior in vs code related to the interplay between syntax highlighting and indentation. I've included two images here which showcase the issue.
This first image shows the issue with syntax highlighting when there is there is a newline + a tab separating the two option directives:
The second image shows that syntax highlighting works correctly when you add in one (or more) newlines between the option directives:
Has anyone else experienced the same issue? Or could this possibly be due to some local misconfiguration on my part?
The text was updated successfully, but these errors were encountered: