Aaron Dill
Aaron Dill
With the merging of #60, you can now use `doas` *only* with `nopass` configured!
@WillPower3309 if you're still interested in fixing this, instead of piping commands to bash, you could set `awful.util.shell` to `bash`, which would force the `awful.spawn.*_with_shell` functions to spawn a bash...
multilineComments enables parsing block comments. Comments are still only marked line by line. Perhaps this option should be renamed, @aaron-bond. Many people seem to misunderstand it. Perhaps rename it to...
Are you saying you would rather: ```js /* ! this is red so is this this too! */ ``` instead of the current: ```js /* ! this is red this...
@aaron-bond, I’m wondering if you’ve noticed either of my recent pull requests(or their corresponding issues)? they each fix inconsistencies and allow for use of this extension in more areas without...
The behavior you are describing is because jsdoc comments (/**) are styled(and more importantly, detected) differently than normal block comments. My pull request should fix this issue, provided it gets...
Taking a quick look through [/src/parser.ts](https://github.com/aaron-bond/better-comments/tree/084a906e73a3ca96d5319441714be8e3a2a8c385/src/parse.ts), it seems like this line in `parser.SetRegex` is the issue. ```ts // parser.SetRegex; this.expression += "("; this.expression += characters.join("|"); this.expression += ")+(.*)"; ``` The...
Add this line to your settings.json: ```json "better-comments.highlightPlainText": true, ``` That will enable highlighting in any file without a defined comment. You simply type the tag as the first non-whitespace...
I suspect this may be because VSCode recognizes it as CSV and not plain text, then the extension rejects it because CSV is not supported. If you change the extension...
Because CSV has no comment syntax, the extension is not setup to allow that language and automatically rejects it. @aaron-bond perhaps a new setting, `forcePlainText`, that either is an array...