Commit 17bc3c05 authored by Johan Sundström's avatar Johan Sundström
Browse files

Reverted bad kom-change-language prefix argument hack.

parent d5111bf8
......@@ -102,11 +102,6 @@
** The binding for kom-review-backward is now under the prefix for
review commands.
** kom-change-language now does not require a prefix argument to
change the key bindings as well as the language. The previous
behaviour of only affecting the text, and only in the current
session, is still available with a numeric prefix argument.
* New commands
......
2003-12-16 Johan Sundström <jhs@lysator.liu.se>
* commands2.el (kom-change-language): Reverted my improper prefix
argument hack from 2003-08-30.
2003-12-11 David Byers <byers@lysator.liu.se>
Fix bug 1233:
......
......@@ -2176,8 +2176,8 @@ the exception of the letterbox flag (which cannot be modified)."
(def-kom-command kom-change-language (&optional global)
"Change the current language in the current LysKOM session.
Also changes key bindings in all sessions, unless given an
integer prefix argument.
With a prefix argument, also make changes that would affect all
sessions, such as key bindings.
The selected language is not saved between sessions. To permanently
set and save language settings. use `kom-customize' instead.
......@@ -2185,7 +2185,7 @@ set and save language settings. use `kom-customize' instead.
See `kom-default-language'.
Lisp documentation:
If the optional argument GLOBAL is 0, the change will have a
The optional argument GLOBAL indicates that the change should have a
global effect, including changes to key binding."
(interactive "P")
(let* ((completion-ignore-case t)
......@@ -2199,7 +2199,7 @@ global effect, including changes to key binding."
'lyskom-language-history)))
(when (lyskom-string-assoc language table)
(lyskom-set-language (cdr (lyskom-string-assoc language table)) 'local)
(when (listp global)
(when global
(lyskom-set-language (cdr (lyskom-string-assoc language table)) 'global))
(lyskom-format-insert
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment