From: Eshel Yaron Date: Tue, 16 Jul 2024 17:53:54 +0000 (+0200) Subject: refactor.el: Fix typos X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=1b17bdf688de36e8231450b24f4a65eb8d39d93e;p=emacs.git refactor.el: Fix typos --- diff --git a/lisp/progmodes/refactor.el b/lisp/progmodes/refactor.el index 43203c34da7..108f98432ef 100644 --- a/lisp/progmodes/refactor.el +++ b/lisp/progmodes/refactor.el @@ -65,7 +65,7 @@ value is a string, it may include the following `%'-constructs: `%o' is the old identifier name, `%n' is the new identifier name, and `%s' is the scope of the renaming operation. -The default value is the string \"Renaming \\\"%o\\\" to \\\"n\\\" in %s.\"" +The default value is the string \"Renaming \\\"%o\\\" to \\\"%n\\\" in %s.\"" :type '(choice (string :tag "Format string") (const :tag "Disable" nil))) @@ -147,14 +147,14 @@ operations that BACKEND supports.") Return a cons cell (IDENT . SCOPE), where IDENT is the identifier to operate on and SCOPE is the scope of application. The meaning of both IDENT and SCOPE are BACKEND-specific, but SCOPE is conventionally one of -`expression', `defun', `file' or `project'." +`expression', `defun', `buffer' or `project'." (when-let ((sym (symbol-at-point))) (cons (symbol-name sym) (if (project-current) 'project 'buffer)))) (cl-defgeneric refactor-backend-invalid-replacement (_backend _old _new _scope) "Check if NEW is a valid replacement for OLD in SCOPE according to BACKEND. -If it is invalid, for example if NEW is in conflict an identifier that +If it is invalid, for example if NEW conflicts with an identifier that is already in use, return a string to display as feedback to the user. Otherwise, if the replacement is valid, return nil." nil)