From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: weird bug with `Russian-computer'?
Date: Mon, 04 Jul 2005 03:44:33 +0300 [thread overview]
Message-ID: <87fyuvtgox.fsf@jurta.org> (raw)
In-Reply-To: <200507040027.59478.pogonyshev@gmx.net> (Paul Pogonyshev's message of "Mon, 4 Jul 2005 00:27:59 +0300")
> With the `Russian-computer' input method, S-/ combination produces a comma
> (instead of a question mark with standard English.) That is OK and the
> way it should be.
Perhaps you have a US keyboard layout with `?' on the same key as `/'.
Finnish keyboards have quite a different layout where `?' is on the
same key as `+', and it is produced by `S-+'. Other keyboards have
other layouts, but anyhow I understand how to reproduce the problem.
What is essential here is to press shift with the `?' key, because the
`russian-computer' input method maps `?' to `,'.
> However, when I start incremental search, the key works as in
> English, while the rest of the keyboard keeps producing Russian
> letters etc.
The root of the problem is in `isearch-mode-map' which binds `?' to
`isearch-*-char'. When you type a key corresponding to `?' with
the input method, `isearch-*-char' intercepts it and interprets as
the regexp special character `?'.
The following patch fixes this problem by sending the input character
to `isearch-process-search-char' which takes care of processing the
character according to the current input method. Also a new condition
was added before processing a regexp character. If an input method is
active, it processes a regexp character only if a typed character is
the same with and without an input method, so that all input methods
that don't redefine regexp characters won't be affected.
Index: lisp/isearch.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/isearch.el,v
retrieving revision 1.263
diff -c -r1.263 isearch.el
*** lisp/isearch.el 23 Apr 2005 15:38:07 -0000 1.263
--- lisp/isearch.el 4 Jul 2005 00:35:07 -0000
***************
*** 1413,1420 ****
If optional TO-BARRIER non-nil, ignore previous matches and go exactly to the
barrier."
;; (eq (not a) (not b)) makes all non-nil values equivalent
! (when (and isearch-regexp (eq (not (isearch-backslash isearch-string))
! (not want-backslash))
;; We have to check 2 stack frames because the last might be
;; invalid just because of a backslash.
(or (not isearch-error)
--- 1423,1435 ----
If optional TO-BARRIER non-nil, ignore previous matches and go exactly to the
barrier."
;; (eq (not a) (not b)) makes all non-nil values equivalent
! (when (and isearch-regexp
! (or (not current-input-method)
! (let ((qchar (quail-find-key last-command-char)))
! (or (eq qchar t)
! (equal (car-safe qchar) (string last-command-char)))))
! (eq (not (isearch-backslash isearch-string))
! (not want-backslash))
;; We have to check 2 stack frames because the last might be
;; invalid just because of a backslash.
(or (not isearch-error)
***************
*** 1458,1464 ****
(max last-other-end isearch-barrier)
(min last-other-end isearch-barrier)))
(setq isearch-adjusted t))))))
! (isearch-process-search-char last-command-char))
;; * and ? are special when not preceded by \.
(defun isearch-*-char ()
--- 1473,1479 ----
(max last-other-end isearch-barrier)
(min last-other-end isearch-barrier)))
(setq isearch-adjusted t))))))
! (isearch-printing-char))
;; * and ? are special when not preceded by \.
(defun isearch-*-char ()
Index: lisp/international/isearch-x.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/international/isearch-x.el,v
retrieving revision 1.19
diff -c -r1.19 isearch-x.el
*** lisp/international/isearch-x.el 13 May 2005 06:03:45 -0000 1.19
--- lisp/international/isearch-x.el 4 Jul 2005 00:35:19 -0000
***************
*** 96,104 ****
;;;###autoload
(defun isearch-process-search-multibyte-characters (last-char)
! (if (eq this-command 'isearch-printing-char)
(let ((overriding-terminal-local-map nil)
! (prompt (concat (isearch-message-prefix)))
(minibuffer-local-map isearch-minibuffer-local-map)
str)
(if isearch-input-method-function
--- 96,105 ----
;;;###autoload
(defun isearch-process-search-multibyte-characters (last-char)
! (if (memq this-command '(isearch-printing-char
! isearch-*-char isearch-}-char isearch-|-char))
(let ((overriding-terminal-local-map nil)
! (prompt (isearch-message-prefix))
(minibuffer-local-map isearch-minibuffer-local-map)
str)
(if isearch-input-method-function
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-07-04 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 21:27 weird bug with `Russian-computer'? Paul Pogonyshev
2005-07-04 0:03 ` Miles Bader
2005-07-04 0:44 ` Juri Linkov [this message]
2005-07-04 16:03 ` Paul Pogonyshev
2005-07-05 5:27 ` Juri Linkov
2005-07-11 21:47 ` Paul Pogonyshev
2005-07-12 6:56 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fyuvtgox.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).