In VS Code, the functionality for displaying markers in the minimap is implemented.
It would be nice to have a switch in the settings that would allow the MARK tag to be automatically inserted into the header comment.

Example:

/* -------------------------------------------------------------------------- */
/* MARK:                          Example text                                */
/* -------------------------------------------------------------------------- */

I'm currently working in Vuejs and Vue is divided to parts html/script/styles. I would liketo have more control over which section to comment, for example HTML instead of /* */

great extension!!!

The default comment style for C++ is:

/* -------------------------------------------------------------------------- */
/*                                 Main Header                                */
/* -------------------------------------------------------------------------- */

Is it possible to use:

// -------------------------------------------------------------------------- //
//                                 Main Header                                //
// -------------------------------------------------------------------------- //

or

/* --------------------------------------------------------------------------
                                   Main Header
-------------------------------------------------------------------------- */

I tried adding this to the settings.json file, but it's not working:
"comment-divider.languagesMap": { "liquid": ["{%- comment -%}", "{%- endcomment -%}"] }

Liquid files are commented with {%- comment -%} and {%- endcomment -%}

Preliminary note

<3 the extension.
Also, the source reads well.

Here's the bug

The 4 options pertaining to the subheader are documented in the README (and hence by proxy also in the in-app manual) as if "subheader" were two words. Here, the options are called subHeader<OptionName>, whereas the actual implementation is treating it as one word while parsing (i.e.looking for keys named subheader<OptionName>).

• package.json#L112
• package.json#L119
• package.json#L128
• package.json#L138
• README

I know we can set the line length for all dividers through the config, what I need is multiple lengths of divider at the same time, which doesn't seem to be possible at the moment, but this feature is very useful isn't it?

Another extension support this feature, but it has other drawbacks, it does not keep the length consistent.

Hi,

I have noticed recently that the extension is not working when comment-divider.languagesMap is used as Workspace setting.

Here an example of setting to reproduce the bug:

  "comment-divider.languagesMap": {
    "scss": ["//"]
  },

If I use comment-divider.languagesMap as User or Remote setting, the right comment character is used.

Extension version: v0.4.0

VSCode information:
Version: 1.62.3
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T08:00:36.721Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.4.0-91-generic snap

would be great to see .vue file support like
1). "" for template section
2) "//" for script section
3) / */ for style section

ALT+X can not be used ,when typed ,the warning "Running the contributed command: 'extension.add_chaos' failed." occurs in the lower-left corner of the vscode, help.

Today, "main" and "divider" are defined. I use a slightly deeper divider structure.

/* =======================
ALL CAPS
/* ======================= */

/* ---------------------------------------
Title Case
/* --------------------------------------- */

/* --------------- Title Case ------------ */

I can almost do this today, but I can't do the middle one because only one "main" style can be defined at a time.

Accomplishing this scheme also means a setting for each level indicating case conversion (ie, all caps, title case, unchanged). Title case isn't terribly important, but I'd need the option for a main-style header to not convert to all caps.

From the documentation of the Languages Configuration it does not become apparent how one would find the correct language ID, to change the style for a specific language / file type.

Maybe you could point to the respective VSC Language ID documentation, from which one can infer to press CTRL + K M (Change Language Mode) to list all languages.

I think this would be helpful.

Thank you for providing such a useful tool.

Do you have any plans to make this plug-in support visual studio??

I can't find a plug-in with similar functionality on visual studio

Make the line length be equal to the content length plus a few.

I am using commend-divider with Better Comments (to sometimes put, e.g., * to highlight the comment).

What I want is to automatically make

# *************************************************************************** #
# *                             MINMAX CLIPPING                             * #
# *************************************************************************** #

which will automatically be highlighted.

IMHO, an addition of the feature such as

"comment-divider.mainHeaderStarter": "*",
"comment-divider.mainHeaderEnder": "*",

can be useful. How do you think...?

It'd be nice if the tool could recognize two things:

1. Language-specific horizontal ruler-extension limits defined in the settings.json - file:

"[python]": {
        "editor.rulers": [
            80,
            120
        ]
    }

2. Indentation according to current code:
   Instead of heaving to tab it over and then accept that the ruler exceeds the vertical limits like so ...

# ------------------------------- Some function ------------------------------ #
def func():

    # ------------------------------- Sub-function ------------------------------- #
    def sub_func():
        pass

... it'd be awesome of the extension calculated automatically the difference between the indentation and the vertical right limit, which would lead to following result:

# ------------------------------- Some function ------------------------------ #
def func():

    # ----------------------------- Sub-function ----------------------------- #
    def sub_func():
        pass

First, I'd like to thank you for this fantastic plugin. It's little things like this that make coding so much easier and leave me with less to worry about.

It's a humble request, but I would love to be able to use the // comment indicator instead of the comment lines being wrapped in /*...*/.

For example, instead of:

/* Example ------------------------------------------------------------------ */

I would like to be able to change it to:

// Example --------------------------------------------------------------------

I know it's minor, but I never write vanilla CSS so I've become quite attached to my slashes. 😅

Cheers, and thank you again!

is it possible to use opt + x subHeader in tsx or react ? I have tried to modify it on JSON setting but it's not working.
comment-divider.languagesMap": {
".tsx": ["{/", "/}"],
".jsx":["{/", "/}"],
".typescript": ["{/", "/}"],
".js": ["{/", "/}"],
".react": ["{/", "/}"],
".javascript": ["{/", "/}"],
".javaScript": ["{/", "/}"],
".html": ["{/", "/}"],
"toml": ["#", "#"],
"scss": ["//"]
},
thank you

This is a good, clean and convenient extension, but it seems doesn't support .svelte file yet.
// doesn't work
/* doesn't work neither */
<!-- THIS WORKS -->

It'll be great if you can fix this in the next release. Thanks a lot!

In R files, the presence of a hash symbol at the end of the section line prevents it from showing up on the VSC breadcrumbs row:

Removing it makes the section render correctly

I've tried a similar approach on different languages (HTML, Python, C++). In these cases, I couldn't even get the section to appear on the breadcrumb at all (and that may be a topic for a different discussion), but at least for R that's the deal.

I can also understand that hard-coding a different final character might break the extension for other languages, so perhaps the safest option here is to allow the user to custimoze the final character, either in general or, ideally, on a per-language basis.

When using tabs for indentation, setting "comment-divider.shouldLengthIncludeIndent": false doesn't properly respect the length defined by comment-divider.length. In my tests, the overflow varies from 1 extra character (when tab =< 4 spaces) to 3 extra characters (when tab = 4 spaces).

I would like to change the filter characters on a per language basis.

This extension is working with JS but not JSX

OS: Microsoft Windows [Version 10.0.18363.476]
VS code version: 1.40.2
Extension version: 0.2.1

When I type a text with indent like this.

After using Alt + X Indent is gone.

Hi, could it be possible to request the banner to start at the indent level of the code but end at the same column width?

Thanks

/* -------------------------------------------------------------------------- */
/*                              Actual behaviour                              */
/* -------------------------------------------------------------------------- */
    code being indented
    /* ---------------------------------------------------------------------- */
    /*                         New Optional Behaviour                         */
    /* ---------------------------------------------------------------------- */

Please add simple instructions on how to edit the default confirguation! I am fairly new to VS Code. I've spent a lot of time trying to find out how to do it. I suspect there is file somewhere to edit, but unable to locate even after searching online. There seems to be no easy way to access the file in VSCode.

This is a great extension, and it works well with English comments.
But with Chinese or Japanese, I press Shift + Alt + X and find that the second line is not aligned

This is the test sentences: 中文测试.

hi
how to Configure Laravel Blade?

The configuration docs say that you can set a "text transform style" for the headers (eg comment-divider.mainHeaderTransform) but they don't explain what that means or what the options are. (From transforms.ts it looks like the options are lowercase, uppercase, titlecase, and none, but it'd be nice for them to be listed and explained in the README.)

This is probably a good #firstIssue for someone 😄

Thanks for an awesome extension!

An option comment-divider.languagesLengthMap should precise the line length for a particular language:

"comment-divider.languagesLengthMap": {
      "toml": 80,
      "scss": 120
}

This option should have the priority over the comment-divider.length option.
If a language is not present in the new option comment-divider.languagesLengthMap, then the default given by comment-divider.length is applied.

Have tried this:

  "comment-divider.languagesMap": {
    "typescript": ["//",],
    "typescriptreact": ["//"],
    "javascript": ["//"],
    "javascriptreact": ["//"]
  },

doesn't have any effect.

I am getting:
Comment Divider: Line contains comment characters!
and I want to surpass that configuration, how could I config that? I combine 'comment divider' with 'better comments' extension and I want to be able to create the dividers from comments, currently I do it manually when I get the error.
Like this:

The align from the below settings do not work.

"comment-divider.subHeaderFiller": "-",
"comment-divider.subHeaderHeight": "line",
"comment-divider.subHeaderTransform": "none",
"comment-divider.subHeaderAlign": "left",

It gives

# --------------------------------- comment --------------------------------- #

in python, where I expected

# comment ------------------------------------------------------------------- #

Is this an intended behavior?

Description

After installing the extension, I noticed that the Alt+X shortcut doesn't work.

This is what appears in the bottom bar of VSCode:

Environment

• [email protected]
• [email protected]

Currently the comment dividers look like this:
# ################################## Example ################################# #

I was wondering if there could be a setting e.g. comment-divider.seamless that would make the comments remove the whitespaces just after the start and just before the end of the string e.g.:
#################################### Example ###################################

Cheers

I guess extension comment style depends on page extension. So, when I comment some js code which is included in the html page, the extension gives the html style comment which is wrong.

index.html

<script>
<!-- ---------------------------- example line ----------------------------- -->
function hello(){
}
</script>

However, VSCode is commenting fine so see if that can help.

Center-aligned comment words are hard to read in comparison to when comment words are aligned at the left, close to the beginning of the line.

Also, another cool feature would be making a small one line comment (without any extra decoration) as writing even simple comments in HTML and CSS can be made easier this way.

Can you please add an option to update a comment line's length to a changed comment text (happens very often, you know)? Like implemented in the similar add-on https://marketplace.visualstudio.com/items?itemName=slysherz.comment-box

?

Would be great, thanks!

Would be nice when selected a comment block and pressed ALT+SHIFT+X it would convert it into original text

It should remove comment characters from the line:

// this is a comment

support padding option to have something like this:

padding: 0

// comment ==========

padding: 3

// === comment ======