Is there a reason for "delete-buffer"?

Hello,
I am new to kakoune, coming from vim. I just wanted to know, why the “buffer” commands are inverted. We have “buffer-next” and “buffer-previous”. But we also have “delete-buffer”. This last one seems to me, to go against the kakoune philosophy of first selecting and then acting. Furthermore, I want to write “buffer-…” and then need to correct this.
The question, I guess, is: Why is it “delete-buffer” and not “buffer-delete”?

P.S.: I like the “selection first” mentality. It has a very 2016 kind of vibe :stuck_out_tongue: I also very
much like the regex mechanism. It comes much more naturaly to me than the vim-counterpart.
P.P.S.: I am in favor of the whole “Duck”-Issue

1 Like

Hello

Have a look at these related GitHub issues / commits for some historic background on this topic:

Why db to delete buffer instead of bd
https://github.com/mawww/kakoune/issues/1094

Buffer Delete vs Delete Buffer
https://github.com/mawww/kakoune/issues/806

Rename commands to fit a more consistent naming scheme
https://github.com/mawww/kakoune/pull/827

3 Likes

Hi Delapouite,

thank you for the informative reply.
I understand the problems now, arising from old naming schemes.
IMHO a consistent verbose object-verb format with custom alias would have been a great choice for kakoune.
Since kak already diverges from konventions, consistency would have been a great asset.
Having said that, I think the commands have a great format.

Many greetings from a fellow Mouilleur