Bash ANSI-C quoting highlighting #2436

Activity

1. smhmd

   added

   language-definitions

   on Jun 27, 2020
2. RunDevelopment commented on Jun 27, 2020

   

   RunDevelopment

   on Jun 27, 2020

   Last edited by RunDevelopment

   Member

   More actions

   The \ns aren't a problem, but the single quotes around 'eslint:recommended' are. I've also never seen $'something' before. Edit. Should have read the doc. First point stands tho.
3. RunDevelopment commented on Mar 7, 2021

   

   RunDevelopment

   on Mar 7, 2021

   Last edited by RunDevelopment

   Member

   More actions

   Prism's highlighting is (mostly) correct.

   

   In your example, you echo multiple strings that are concatenated and not one long string. As per spec:

   Enclosing characters in single quotes (‘'’) preserves the literal value of each character within the quotes. A single quote may not occur between single quotes, even when preceded by a backslash.

   Here is the output of the echo command on my machine:

   micha@DESKTOP-DCVE9I0:/mnt/c/Users/micha$ echo $'module.exports = {\n  extends: [\n    // add more generic rulesets here, such as:\n    // 'eslint:recommended',\n    "plugin:vue/vue3-recommended",\n    "prettier",\n    "prettier/vue",\n  ],\n  rules: {\n    // override/add rules settings here, such as:\n    // 'vue/no-unused-vars': 'error'\n  },\n};'
   echo $'module.exports = {\n  extends: [\n    // add more generic rulesets here, such as:\n    // 'eslint:recommended',\n    "plugin:vue/vue3-recommended",\n    "prettier",\n    "prettier/vue",\n  ],\n  rules: {\n    // override/add rules settings here, such as:\n    // 'vue/no-unused-vars': 'error'\n  },\n};'
   module.exports = {
     extends: [
       // add more generic rulesets here, such as:
       // eslint:recommended,\n    "plugin:vue/vue3-recommended",\n    "prettier",\n    "prettier/vue",\n  ],\n  rules: {\n    // override/add rules settings here, such as:\n    // vue/no-unused-vars: error\n  },\n};

   That being said, I'll add support for ANSI-C Quoting.
4. smhmd commented on Mar 7, 2021

   

   smhmd

   on Mar 7, 2021

   Author

   More actions

   I see. So, ANSI-C quotes behave differently in bash and zsh.
   
5. RunDevelopment commented on Mar 7, 2021

   

   RunDevelopment

   on Mar 7, 2021

   Member

   More actions

   That's interesting. zsh docs says this:

   A string enclosed between ‘$’’ and ‘’’ is processed the same way as the string arguments of the print builtin, and the resulting string is considered to be entirely quoted. A literal ‘’’ character can be included in the string by using the ‘\’’ escape.

   Luckily, the doc for print doesn't mention how string arguments are processed... At least, I couldn't find it. If I had to guess, then zsh requires a space (or the end of the command/line) after the second ' for it to be the closing quote.

   Anyway, the zsh behavior is incompatible with bash and won't be supported in the bash language.
6. RunDevelopment

   closed this as completedin #2792on Mar 17, 2021