You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've written a small package that ports vim's ci and ca functionality to Emacs; quoting from the readme, given a function like
function test() {
return "semantic| kill";
}
with | indicating the point:
change-inner " would kill the contents of the string, resulting in
function test() {
return "|";
}
change-inner-outer " would kill the entire string:
function test() {
return |;
}
change-inner { would kill the return-statement:
function test() {|}
change-inner-outer { would kill the entire block:
function test() |
Originally based on magnars/change-inner.el, the package now uses puni instead of expand-region for selecting the appropriate region of text.
In slotThe/change-inner#1 I was asked why this was not included upstream, and the only answer I could come up with is that puni generally seems to favour very general structural editing functions, and this is rather specific functionality. However, of course I don't actually know, so this issue exists to clarify that :)
The text was updated successfully, but these errors were encountered:
Hi,
I've written a small package that ports vim's
ci
andca
functionality to Emacs; quoting from the readme, given a function likewith
|
indicating the point:change-inner "
would kill the contents of the string, resulting inchange-inner-outer "
would kill the entire string:change-inner {
would kill the return-statement:change-inner-outer {
would kill the entire block:Originally based on magnars/change-inner.el, the package now uses puni instead of expand-region for selecting the appropriate region of text.
In slotThe/change-inner#1 I was asked why this was not included upstream, and the only answer I could come up with is that puni generally seems to favour very general structural editing functions, and this is rather specific functionality. However, of course I don't actually know, so this issue exists to clarify that :)
The text was updated successfully, but these errors were encountered: