How to quickly delete the entire method?

[yaoqiangpersonal]

like this title, I want to find a way that can quickly delete the entire method. But I didn't find it in the end. Can anyone tell me?

[lippfi]

You can create some clever vim mapping to do this.
e.g. if you place your caret at the first line of function definition nnoremap dm Va{%d would do the job for functions like this:

fun name(args): Int {
  ....
}

or even better nnoremap dk V/{<CR>%d would also work for functions where arguments occupy multiple lines:

fun name(arg1,
arg2) {
  ...
}

[yaoqiangpersonal]

thanks a million. I use the way that it is like you supply.

[Sebastian-Nielsen]

@magidc's solution is better as it allows you to delete the method when executing the command from wherever inside the target method.
This solution only works if the closest enclosed curly-brackets surrounding the caret are the curly brackets of the function.

[lippfi]

@Sebastian-Nielsen you are right
by the way the issue is related to https://youtrack.jetbrains.com/issue/VIM-480/Add-text-objects-for-code-constructs-like-a-method-and-a-class . You can upvote the ticket or follow it's progress if you want (the more upvotes ticket has the more chances it will be implemented soon)

[magidc]

This is my solution:
nnoremap dam :action MethodUp<cr>v0Of{%d
It is based on a remap but it uses and action from Intellij. With this approach you can be in any position inside a method and still will do the job.

[magidc]

I have added a small modification to the mappings that allows to copy, delete or change methods (whole or just body) from any position of the method body or declaration:

nnoremap yim j:action MethodUp<cr>f{vi{y
nnoremap dim j:action MethodUp<cr>f{vi{d
nnoremap cim j:action MethodUp<cr>f{vi{c
nnoremap yam j:action MethodUp<cr>v0Of{%y
nnoremap dam j:action MethodUp<cr>v0Of{%d
nnoremap cam j:action MethodUp<cr>v0Of{%c

You can find my complete .ideavim config file here

[victorivanov]

Wow, somehow I missed that we have access to Intellij commands in ex, the, at is a game changer for me! Thanks for sharing the solutions above. I wrote my own variations, which are more general but with the trade-off of i ones not working with multi-line method declarations (I have a feeling there is a solution for that somewhere though...).

Those don't rely on curly braces so work for more languages and contexts, instead using the vim-standard ]m motion). Note that I switched m to f as that's what I'm used to from the nvim plugin I'm used to.

nnoremap Vaf :action MethodUp<cr>V]M
nnoremap vaf :action MethodUp<cr>V]M

nnoremap Vif :action MethodUp<cr>jV]Mk
nnoremap vif :action MethodUp<cr>jV]Mk

nnoremap daf :action MethodUp<cr>V]Md
nnoremap dif :action MethodUp<cr>jV]Mkd

nnoremap yaf :action MethodUp<cr>V]My
nnoremap yif :action MethodUp<cr>jV]Mky

nnoremap caf :action MethodUp<cr>V]Mc
nnoremap cif :action MethodUp<cr>jV]Mkc

Until today I was using the indent text objects provided by michaeljsmith/vim-indent-object (still a good workaround for those i/multi-line signatures)

[megawubs]

My experience thus far is not that good with the above mapping. For example, when i'm at the line of a method declaration, it goes one method up and deletes that one. It also does not delete the doc blocks when they are present.

Ideally I would like a way to just describe text-objects based on language semantics as is possible with nvim-tree-sitter-textobjects.

[magidc]

Hi, my mappings cover the situation you has just described, when you are at the line of a method declaration. That's why there is "j" before every MethodUp action, basically it makes sure you are always under the desclaration so the MethodUp action moves to the declaration of the current method.
I could not solve the doc blocks issue though...

nnoremap vam j:action MethodUp<cr>0v]M
nnoremap vim j:action MethodUp<cr>]m<cr>v]M<bs>
nnoremap dam j:action MethodUp<cr>0v]M"_d
nnoremap dim j:action MethodUp<cr>]m<cr>v]M<bs>"_d
nnoremap yam j:action MethodUp<cr>0v]My
nnoremap yim j:action MethodUp<cr>]m<cr>v]M<bs>y
nnoremap cam j:action MethodUp<cr>0v]M"_c
nnoremap cim j:action MethodUp<cr>]m<cr>v]M<bs>"_c

[lippfi]

@megawubs > Ideally I would like a way to just describe text-objects based on language semantics as is possible with nvim-tree-sitter-textobjects
It's doable (utilizing IJ Platform PSI); however, IdeaVim team is focused on other tasks, and there are no resources to implement and maintain this functionality. It sounds like a good idea for an IDE plugin that could be downloaded from marketplaces and used along with IdeaVim.
Implementing this in a separate plugin may still require changes to IdeaVim, and your PRs are always welcome.

[megawubs]

I do want to look into writing a plugin. But java/kotlin are not my primary languages and it feels a bit daunting to start something big like this.

[magidc]

@megawubs I feel the same. It would be awesome to have a treesitter like plugin to manage all kinds of text objects but I don't feel in mood to accomplish such a complex development. By the moment, I am staying with keymapping hacks to deal with it