Re: bash syntax: incorrect highlighting of escaped double quote
Marvin Renich wrote:
The sh.vim syntax file does not recognize the escaped double quote
inside the double-quoted string in the following bash snippet:
---8<
#!/bin/bash
for r in $reqFields ; do
if [[ -z "${keys[$r]}" || "${keys[$r]}" == "\"\"" ]] ; then
missing="$missing $r"
fi
done
--->8
It looks like the shDoubleQuote region has a skip clause that is
supposed to handle this, but it isn't working for me. If you can't
reproduce this, I'll try to narrow it down more. b:is_bash is being set
correctly, and syntax list shDoubleQuote shows the expected contents.
How can you determine what syntax group is used for a particular
character?
Hello!
Please try v133 of syntax/sh.vim, available at my website:
http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH .
As for your question... I use my hilinks plugin (with :HLT!):
http://www.drchip.org/astronaut/vim/index.html#HILINKS .
Regards,
C Campbell
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: bash syntax: incorrect highlighting of escaped double quote
Peter Aronoff wrote: On Mon Oct 10/21/13 at 8:04, Ben Fritz wrote: On Monday, October 21, 2013 9:56:26 AM UTC-5, telemachus wrote: Can I ask what email you used to reach him? I've had luck in the past with the email address in the header of his plugins. But you need to remove the capital letters NOSPAM distributed through the email address to confuse email harvesters. Otherwise the address is not valid. When you said that, I thought "Oh, wow, how did I miss NOSPAM"? The good news is that I didn't. The bad news is that the maintainer for indent/sh.vim is not Dr. Chips. It's Nikolai Weibull. His email address doesn't have NOSPAM in it. Having said that, and I've asked this once before, what recourse do I have when nobody responds either here on the list or the maintainer? For what it's worth, here's my original mail and my question about contacting maintainers: https://groups.google.com/d/msg/vim_dev/WszUzmhaDGM/W31QcXPpKcMJ https://groups.google.com/d/msg/vim_dev/Q_KGrMevqW0/g2zLu-Set5AJ Try contacting Bram Moolenaar (:help moolenaar will give you his email). In the past in similar situations he's tried to contact the maintainer himself and then he's likely to ask you if you'd be willing to become the maintainer. Regards, C Campbell -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: bash syntax: incorrect highlighting of escaped double quote
On Mon Oct 10/21/13 at 8:04, Ben Fritz wrote: > On Monday, October 21, 2013 9:56:26 AM UTC-5, telemachus wrote: > > Can I ask what email you used to reach him? > > I've had luck in the past with the email address in the header of his > plugins. > > But you need to remove the capital letters NOSPAM distributed through the > email address to confuse email harvesters. Otherwise the address is not > valid. When you said that, I thought "Oh, wow, how did I miss NOSPAM"? The good news is that I didn't. The bad news is that the maintainer for indent/sh.vim is not Dr. Chips. It's Nikolai Weibull. His email address doesn't have NOSPAM in it. Having said that, and I've asked this once before, what recourse do I have when nobody responds either here on the list or the maintainer? For what it's worth, here's my original mail and my question about contacting maintainers: https://groups.google.com/d/msg/vim_dev/WszUzmhaDGM/W31QcXPpKcMJ https://groups.google.com/d/msg/vim_dev/Q_KGrMevqW0/g2zLu-Set5AJ Thanks, Peter -- We have not been faced with the need to satisfy someone else's requirements, and for this freedom we are grateful. Dennis Ritchie and Ken Thompson, The UNIX Time-Sharing System -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: bash syntax: incorrect highlighting of escaped double quote
On Mon Oct 10/21/13 at 10:29, Marvin Renich wrote: > Dr. Chip sent me an updated sh.vim that works. Thank you! Can I ask what email you used to reach him? I sent a patch here and to him a few months ago for sh.vim, but I haven't heard any response from anyone. (It concerns incorrect indendation for empty case statements.) Thanks, Peter -- We have not been faced with the need to satisfy someone else's requirements, and for this freedom we are grateful. Dennis Ritchie and Ken Thompson, The UNIX Time-Sharing System -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: bash syntax: incorrect highlighting of escaped double quote
On Monday, October 21, 2013 9:56:26 AM UTC-5, telemachus wrote: > On Mon Oct 10/21/13 at 10:29, Marvin Renich wrote: > > > Dr. Chip sent me an updated sh.vim that works. Thank you! > > > > Can I ask what email you used to reach him? I've had luck in the past with the email address in the header of his plugins. But you need to remove the capital letters NOSPAM distributed through the email address to confuse email harvesters. Otherwise the address is not valid. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: bash syntax: incorrect highlighting of escaped double quote
* Marvin Renich [131021 10:07]: > Thanks, Ben; that's exactly what I was looking for. Hopefully, Dr. Chip > can figure out why the highlighting is wrong. BTW, did you try to > reproduce the incorrect highlighting? I would like to at least know if > this is easily reproducible by others. Dr. Chip sent me an updated sh.vim that works. Thank you! ...Marvin -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: bash syntax: incorrect highlighting of escaped double quote
* Ben Fritz [131021 09:12]: > On Sunday, October 20, 2013 4:07:20 PM UTC-5, Marvin Renich wrote: > > > > How can you determine what syntax group is used for a particular character? > > > > http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor Thanks, Ben; that's exactly what I was looking for. Hopefully, Dr. Chip can figure out why the highlighting is wrong. BTW, did you try to reproduce the incorrect highlighting? I would like to at least know if this is easily reproducible by others. Thanks again...Marvin -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: bash syntax: incorrect highlighting of escaped double quote
On Sunday, October 20, 2013 4:07:20 PM UTC-5, Marvin Renich wrote: > > How can you determine what syntax group is used for a particular > > character? > http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
bash syntax: incorrect highlighting of escaped double quote
The sh.vim syntax file does not recognize the escaped double quote
inside the double-quoted string in the following bash snippet:
---8<
#!/bin/bash
for r in $reqFields ; do
if [[ -z "${keys[$r]}" || "${keys[$r]}" == "\"\"" ]] ; then
missing="$missing $r"
fi
done
--->8
It looks like the shDoubleQuote region has a skip clause that is
supposed to handle this, but it isn't working for me. If you can't
reproduce this, I'll try to narrow it down more. b:is_bash is being set
correctly, and syntax list shDoubleQuote shows the expected contents.
How can you determine what syntax group is used for a particular
character?
Thanks...Marvin
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
