Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Naked variable markup #8

Open
tmedwards opened this issue Apr 18, 2020 · 1 comment
Open

Naked variable markup #8

tmedwards opened this issue Apr 18, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request investigate Information gathering is needed

Comments

@tmedwards
Copy link
Owner

Improve the naked variable markup's ability to match variable property chains.

@tmedwards tmedwards transferred this issue from another repository Aug 2, 2020
@tmedwards tmedwards self-assigned this Aug 2, 2020
@tmedwards tmedwards added enhancement New feature or request investigate Information gathering is needed labels Aug 2, 2020
@Uzume
Copy link

Uzume commented Oct 20, 2020

That would work better if the variables were denoted with more than just a leading sigil. For example in Bourne shells they use similar prefixes but also allow optional curly brace quoting to denote the begin and end allowing such variables to be abutted with other text without parsing issues.

Much like in #18 I would like to have a way to turn naked variables "off" (<<=>>, <<->> and <<print>> work just fine as does writing to output in <<script>>, etc.). Or even better yet have them default to "off" and have a config option to turn them "on". Regardless, when they are "on", improvements to the markup is welcome.

Might I recommend a syntax inspired by the newer Python and .NET (C#) string formatting work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request investigate Information gathering is needed
Projects
None yet
Development

No branches or pull requests

2 participants