[Feature request] No backspace if carriage in line begin about hungry-backspace HOT 9 CLOSED

Do you consider indentation as line beginning?

eg. ____|Hello world where _ marks space and | marks the cursor

Or should this only occur in cases like
|Hello world

from hungry-backspace.

@xdrop , yes, I need remove all spaces and tabs in line beginning, but no move carriage in previous lime. So I need this function.

Thanks.

from hungry-backspace.

@Kristinita
ATM, I've added an option for this

It would be nice, if you add command to run backspace command only if carriage is not in line beginning.

The backspace will not trigger if there is no text before the cursor but will erase any sort of spacing before the cursor.

I assume this will be implemented by your macro? (Delete all text to line begin)

If I have text before carriage, all text before carriage was deleted, carriage move to beginning of line.

Let me know if that's all so that I can merge the commit.

from hungry-backspace.

@xdrop, I'm sorry, how it's worked? I change my Hungry Backspace.sublime-settings and hungry_backspace.py files → I restart Sublime Text → but I have still behavior, if I press Ctrl+Shift+Backspace.

Thanks.

from hungry-backspace.

@Kristinita I'm not able to replicate the problem. Is your Ctrl+Shift+Backspace mapped to the hungry backspace or the default sublime backspace?

Also can you try to remove the Package Control version in case they are conflicting and use the files from db4d385 ?

from hungry-backspace.

@xdrop, I think, how disable_on_line_begin worked.

• If after line beginning I have a symbols, if i run hungry_backspace command, backspace disable for me. It is expected behavior.
• But if line is blank, if I run hungry_backspace command, carriage still move to previous line. It is not expected behavior.

Thanks.

from hungry-backspace.

@Kristinita Can you try again with 09974ad ?

from hungry-backspace.

@xdrop, thanks, it's work!

1. Request

May you add separate trigger for disabled_on_line_begin = true backspace?

2. Justification

Usually I don't need disabled_on_line_begin = true, it only hinders. By I need disabled_on_line_begin = true for my macros.

I want that I and others users of my macros can run my macros even if disabled_on_line_begin = false in our settings. I think, the best solution — is created separate trigger for disabled_on_line_begin = true.

3. Expected behavior

1. If I run hungry_backspace command, — Backspace by default — command run as disable_on_line_begin = false.
2. If I run hungry_backspace_disable_on_line_begin command — for example, Super+Backspace by default — command run as disable_on_line_begin = true.

Thanks.

from hungry-backspace.

@xdrop , actually.

Thanks.

from hungry-backspace.