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

Wrong cursor-position after new-line (ENTER) #4

Closed
Lunardis opened this issue Dec 27, 2017 · 3 comments
Closed

Wrong cursor-position after new-line (ENTER) #4

Lunardis opened this issue Dec 27, 2017 · 3 comments

Comments

@Lunardis
Copy link

Lunardis commented Dec 27, 2017

Hello again,

my indention-style is K & R, and it works when it comes to autocompletions. But something odd happens when I press the ENTER for the new line. Instead of being indented with 4 characters it suddenly doesn't indent and is on the same level as the parent.

I thought it is because the indention-styles and changed to others, but it seems not related with this selection.

How can I recover the default behavior again?

Expected behavior (see cursor)

default {
    if(x) { // <- Press ENTER
        |
    }
}

Actual behavior (see cursor)

default {
    if(x) { // <- Press ENTER_
    |
    }
}

Steps to reproduce

Press Enter on the position where the comment starts with the // characters in an LSL document.

Environment

=BB= LSL:
    version: 1.4.1
    installed via Package Control: True

Sublime Text:
    channel: stable
    build: 3143
    portable: False
    platform: MacOS Sierra ( 10.12.6 )
    architecture: x64
@buildersbrewery
Copy link
Owner

will be fixed in the next release

@buildersbrewery
Copy link
Owner

buildersbrewery commented Dec 30, 2017

@Lunardis As a temporary work-around you can manually edit Packages/=BB= LSL/.sublime/metadata/LSL General.tmPreferences and adjust settings there accordingly.

image

@buildersbrewery
Copy link
Owner

buildersbrewery commented Dec 30, 2017

Sneak Preview

requires Build 3154+

indent_styles

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants