FEATURE: Put cursor in the beginning of line in normal mode

[luthfielaroeha]

Did you check the docs?

• I have read all the docs.

Is your feature request related to a problem? Please describe.

Most of the time, when renaming a file I just want to rename the filename without changing the extension. Currently the cursor placed in the end of line.

Describe the solution you'd like.

I think it would be better to put the cursor in the beginning of the line so we can just use cw or ct. to change the filename.

Describe alternatives you've considered.

No response

Additional Context

No response

[pysan3]

#602

[luthfielaroeha]

Sorry probably I'm missing something.
I'm aware that the normal mode exists, but when I want to rename the file, the cursor started in the end of the line.
Is there any other config to make the cursor in the beginning of the line instead?

[pysan3]

Oh I'm sorry.

[bwpge]

Just adding info for anyone looking to pick this up: you might have success getting the nui input/popup window ID (split.winid) and setting the cursor with vim.api.nvim_win_set_cursor().

[pysan3]

neo_tree_popup_input_ready event has been added with #1372.

Please read :h neo-tree-events for more information.

[uthmanmoh]

Not sure if this is the right place to ask this, but does anyone know if there's a way to control what happens based on the different input popups?
I want to be able to customize what happens when the input box for the move operation opens, and a different action when the input box for add opens

[uthmanmoh]

Also with this new suggested event:

{
  event = "neo_tree_popup_input_ready",
  ---@param input NuiInput
  handler = function(input)
    vim.cmd("stopinsert") -- Enter normal mode
  end,
}

I am unable to enter normal mode after manually entering insert mode with i, since pressing esc even in insert mode just closes the input. Is there a way to make it so that I need to press esc from within normal mode only to exit the input box, as I believe it used to be before?

[cseickel]

@uthmanmoh

Not sure if this is the right place to ask this, but does anyone know if there's a way to control what happens based on the different input popups? I want to be able to customize what happens when the input box for the move operation opens, and a different action when the input box for add opens

There's no simple way to do this, but it would be a nice feature. Someone could probably come up with a code snippet to inspect the title displayed in the wrapper window.

I am unable to enter normal mode after manually entering insert mode with i, since pressing esc even in insert mode just closes the input.

That's a bug, or at least an oversight. I made a separate issue out of that.

[pysan3]

Isn't it just up to the user to remap using input:map inside the event by themselves if they want this feature?

[cseickel]

Isn't it just up to the user to remap using input:map inside the event by themselves if they want this feature?

Maybe, but we make the mapping with Nui so I'm not sure how easy it is to unmap from the event.

[pysan3]

Wdym? There's input:unmap or do you mean something else?

[cseickel]

Wdym? There's input:unmap or do you mean something else?

input is a Nui object that is not available in the event and also not standard nvim api so I'm not sure its the best user experience even if we could provide a reference to that object.

[pysan3]

I'm sorry, I even put it in the docs but I forgot to pass input as an argument to fire_event. This is more of a bug I'd say.

I think we should pass it as either input or { input = input }.

Which one would you prefer? I'll make a PR later today.

[pysan3]

@uthmanmoh

I've created #1398. Do you think this method works for you?

It was my mistake in the previous PR. Thanks for pointing out.

[uthmanmoh]

Yup being able to control the mappings seems good. Thanks for the fix.

Although im thinking now with the complexity of this event handler increasing, it might have been a good idea to keep the boolean option enable_normal_mode_for_inputs which if set to 'true' would just create this handler. That makes sense as its own option since thats a basic functionality imo, and then the event handler would be there to customize the behaviour more.

Let me know if this makes sense, maybe I can create a separate ticket for it

[pysan3]

This is my opinion on that #1372 (comment)

I understand that it is complicated but I've seen many FR that are slightly different for everybody (normal by default, put cursor before extension but in insert mode, put cursor at front, ...) and it is hard to distinguish where we officially support and not.

Therefore imo I think it's better to say that we support one and only one feature (insert + maps for <esc>, q) and everyone that don't like this behavior, they can edit whatever they want.
If we go this route, users can share their handler in the wiki and everybody who copy that code will work because everybody is on the same starting point, regardless of any other config option.

[uthmanmoh]

That sounds alright to me. Thanks for clarifying