Skip to content
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

fix 'g:NERDAllowAnyVisualDelims' behavior #479

Merged
merged 1 commit into from
Sep 2, 2021
Merged

fix 'g:NERDAllowAnyVisualDelims' behavior #479

merged 1 commit into from
Sep 2, 2021

Commits on Sep 2, 2021

  1. fix 'g:NERDAllowAnyVisualDelims' action

    fix 'g:NERDAllowAnyVisualDelims' action.
    
                                                        *'NERDAllowAnyVisualDelims'*
    Values: 0 or 1.
    Default: 1.
    
    If set to 1 then, when doing a visual or visual-block comment (but not a
    visual-line comment), the script will choose the right delimiters to use for
    the comment. This means either using the current delimiters if they are
    multipart or using the alternative delimiters if THEY are multipart.  For
    example if we are editing the following java code: >
        float foo = 1221;
        float bar = 324;
        System.out.println(foo * bar);
    <
    If we are using // comments and select the "foo" and "bar" in visual-block
    mode, as shown left below (where '|'s are used to represent the visual-block
    boundary), and comment it then the script will use the alternative delimiters
    as shown on the right: >
    
        float |foo| = 1221;                   float /*foo*/ = 1221;
        float |bar| = 324;                    float /*bar*/ = 324;
        System.out.println(foo * bar);        System.out.println(foo * bar);
    <
    jiaobuzuji committed Sep 2, 2021
    Configuration menu
    Copy the full SHA
    9d5c12e View commit details
    Browse the repository at this point in the history