-
Notifications
You must be signed in to change notification settings - Fork 14
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
[BUG]: The comment_string of some filetypes will contain trailing space #26
Comments
I obtain the same results as yours. I use the built-in For your suggestion to configure the number of spaces between the start of the box and the comment (am I understanding correctly?) I will look into it. Thanks for your feedback! |
…between various filetypes (issue #26)
Just found a workaround while working on another issue (I just had to trim the I close this issue but I keep in mind your suggestion. Thanks again for your feedback! |
Lines still have redundant spaces. In the python file: # ────────────────────────────────────────────────────────────
# ╭──────────────────────────────────────────────────────────╮
# │ test │
# ╰──────────────────────────────────────────────────────────╯
# ──────────────────────────────────────────────────────────── |
You're right in both cases! Should be fixed now. Thank you! |
Take the
CBllbox
command as an example.In the
python
file,before:
# test
after:
The comment_string is
#
.In the
lua
file,before:
-- test
after:
The comment_string is
--
.In the
rust
file,before:
// test
after:
The comment_string is
//
, and does not contain space.It can be seen that some filetypes are separated by 2 spaces, and some are separated by 1 space.
In the former, I found that it contains space by printing
comment_string
, such as#
in Python.Is there something wrong with my configuration?
Also, I think this can be used as a configuration item, that is, the number of spaces between comment and box.
0 means no spaces, etc.
The text was updated successfully, but these errors were encountered: