Bug 75865 - Ctrl-o should not use for starting/ending-conversion
Summary: Ctrl-o should not use for starting/ending-conversion
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: Canna
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Bill Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-14 07:53 UTC by Takanori MATSUURA
Modified: 2007-04-18 16:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-04-21 12:19:47 UTC
Embargoed:


Attachments (Terms of Use)

Description Takanori MATSUURA 2002-10-14 07:53:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021014

Description of problem:
kinput2 uses the key bind "Ctrl-o" for starting/ending-conversion. But Ctrl-o is
used by many other programs (ie. GNOME applications for "File Open", (X)Emacs
for some functions).

So, the ley binding "Ctrl-o" should not use on kinput2.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:fo
1. push "Ctrl-o"

Actual Results:  File Open dialog opens (GNOME etc.).
can't use functions needed Ctrl-o ((X)Emacs).

Expected Results:  no effects against any other programs.

Comment 1 John Thacker 2002-10-20 08:41:48 UTC
This happened in 7.x as well; it's apparently a kinput2 issue.  It's easily
reproducible.  It's especially annoying because the Ctrl-o combination does not
appear in /usr/X11R6/lib/X11/app-defaults/Kinput2 in the resources that allows
one to add and remove new key combinations to start conversions.  It doesn't
appear in the file at all.  Thus, it's impossible to prevent Ctrl-o from
starting conversion.

This is very annoying, because it makes it impossible to access functions called
by ctrl-o.  (It's particularly annoying in Pine, as it makes Postpone unusable,
and pine does not have menus to click on, unlike other applications.)

Comment 2 Akira TAGOH 2003-04-21 08:40:11 UTC
It's Canna's configuration issue. this problem was already fixed. but it's in
skeleton canna configuration file. so if you don't have
(global-unbind-key-function 'japanese-mode) line in your .canna, you may still
see this problem.



Comment 3 Akira TAGOH 2003-04-21 12:19:47 UTC
fixed the source codes in 3.6-15


Note You need to log in before you can comment on or make changes to this bug.