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
In other programming modes, beginning-of-defun and end-of-defun will move the point to the start of the nearest function, sexp, method, subroutine or other analogous constructs.
However, in kotlin-mode, beginning-of-defun moves the point to the beginning of the buffer.
Small example:
packagecom.example.myAppclassMyClass() {
funmyFun1() {
return"myFun1"
}
funmyFun2() {
// when calling `beginning-of-defun` with the point anywhere in this function,// the point should move to the `fun` two lines above,// but it moves to the `package` at the beginning of the buffer instead.return"myFun2"
}
}
Versions:
kotlin-mode version: 20230123.1859
emacs version: 29.0.60
OS: macOS Ventura 13.3 on M1 Pro
(in any case, thanks for the amazing work on this, or otherwise I would not have been able to use Emacs for my Kotlin-related work 👍 )
The text was updated successfully, but these errors were encountered:
In other programming modes,
beginning-of-defun
andend-of-defun
will move the point to the start of the nearest function, sexp, method, subroutine or other analogous constructs.However, in kotlin-mode,
beginning-of-defun
moves the point to the beginning of the buffer.Small example:
Versions:
(in any case, thanks for the amazing work on this, or otherwise I would not have been able to use Emacs for my Kotlin-related work 👍 )
The text was updated successfully, but these errors were encountered: