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

Minor commenting bug #1563

Closed
mattreecebentley opened this Issue Feb 25, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@mattreecebentley

mattreecebentley commented Feb 25, 2017

Selecting two lines of code with shift-down and then hitting shift-'/' also comments/uncomments out the line below the two lines selected.

Ver 10.02-10.04 x64, non-self-compiled, Win7 Sp1

@mattreecebentley

This comment has been minimized.

Show comment
Hide comment
@mattreecebentley

mattreecebentley Apr 5, 2017

ps. Did not occur with versions prior to 10. Maybe a side effect of the resolution of this bug? : #1419

mattreecebentley commented Apr 5, 2017

ps. Did not occur with versions prior to 10. Maybe a side effect of the resolution of this bug? : #1419

@mattreecebentley

This comment has been minimized.

Show comment
Hide comment
@mattreecebentley

mattreecebentley May 13, 2017

This has actually become my no. 1 issue at present - I have to adjust my thinking to accomodate the fact that codelite won't comment/uncomment my code the way it indicates it will.

mattreecebentley commented May 13, 2017

This has actually become my no. 1 issue at present - I have to adjust my thinking to accomodate the fact that codelite won't comment/uncomment my code the way it indicates it will.

@bergfi

This comment has been minimized.

Show comment
Hide comment
@bergfi

bergfi Jun 2, 2017

Contributor

I too am having this issue in version 10.0.4, Arch Linux. Like mattreecebentley, it is also my number one issue as it is quite annoying to keep this in mind.

Contributor

bergfi commented Jun 2, 2017

I too am having this issue in version 10.0.4, Arch Linux. Like mattreecebentley, it is also my number one issue as it is quite annoying to keep this in mind.

@bergfi

This comment has been minimized.

Show comment
Hide comment
@bergfi

bergfi Jun 2, 2017

Contributor

Having a look at the diff (a8f30e7), it seems this part might be what provided that logic, but I am not quite familiar with all functions:

    if(LineFromPosition(PositionBefore(end)) != LineFromPosition(end)) {
        end = wxMax(start, PositionBefore(end));
    }
Contributor

bergfi commented Jun 2, 2017

Having a look at the diff (a8f30e7), it seems this part might be what provided that logic, but I am not quite familiar with all functions:

    if(LineFromPosition(PositionBefore(end)) != LineFromPosition(end)) {
        end = wxMax(start, PositionBefore(end));
    }
@mattreecebentley

This comment has been minimized.

Show comment
Hide comment
@mattreecebentley

mattreecebentley Jun 16, 2017

Still unfixed 10.05

mattreecebentley commented Jun 16, 2017

Still unfixed 10.05

@eranif eranif closed this in 4df68b9 Jun 20, 2017

@bergfi

This comment has been minimized.

Show comment
Hide comment
@bergfi

bergfi Jun 20, 2017

Contributor

Thanks! That fixed it for me.

Contributor

bergfi commented Jun 20, 2017

Thanks! That fixed it for me.

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