On Sat, Jan 15, 2022 at 1:25 PM Doug Kearns <[email protected]> wrote:
>
> On Thu, 13 Jan 2022 at 04:55, Manuel Ortega <[email protected]> wrote:
>
> > Ah, it seems I misremembered the details. But my point remains pretty much
> > the same. I'd said it was unexpected for the comment char of vim9script to
> > be '#<space>'; it's at least as unexpected for it to be '<space>#', and
> > even more unexpected for it to be "'<space>#', unless it's the start of the
> > line". That makes things worse than the old way, not better.
>
> Is this a practical problem?
>
> A quick search of my system suggests that tail comments are very
> rarely used without leading whitespace. The primary counter example
> being the idiomatic use of ;# in Tcl.
>
> Most, maybe all, of the other cases I came across are exceptions to
> the predominant style of the file.
I agree. Also, at least in bash [1] a leading space is required in
most if not all cases (apart from start of line), i.e. just as in
vim9script. As a practical example of why that is (or what that
enables), the cURL CLI has a progress bar option called -# [2]:
$ curl -# -O https://example.com/coolfile.tar.gz
All the best,
Niklas
[1]: https://tldp.org/LDP/abs/html/special-chars.html
[2]: https://daniel.haxx.se/blog/2018/01/22/a-flying-curl-progress-bar/
--
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/CADjV5jd%2B5exNoUF%3Du-d024At06rBusFftgWdJ83h2b_cCAHUtw%40mail.gmail.com.
