Bug 138963

Summary:	iiimf conflicts with cscope_maps.vim plugin for vim
Product:	[Fedora] Fedora	Reporter:	Luke Huang <lukelittlepig>
Component:	im-sdk	Assignee:	Yu Shao <yshao>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	eng-i18n-bugs, lukelittlepig, wtogami
Target Milestone:	---	Keywords:	i18n
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 19:06:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	125997

Description Luke Huang 2004-11-12 06:36:59 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7)
Gecko/20040616 Firefox/0.9

Description of problem:
using cscope_maps.vim plugin in coding c program, the developer can
find all references to the token under cursor by hitting "CTRL-\ s",
but in Fedora Core 3, if the iiim server was started, hitting "CTRL-\
s" will invoke Chinese pinyin input method instead of show the
references to the token under cursor. I tried run /etc/init.d/iiimf
stop, the finding function of cscope_maps.vim worked again, and
/etc/init.d/iiimf start, the function of cscopt_maps.vim failed. 

BTW: my locale is Chinese UTF-8

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


How reproducible:
Always

Steps to Reproduce:
1./etc/init.d/iiimf start
2. edit any c file under vim with cscope_maps.vim plugin
3. move cursor to one token
4. press CTRL-\ s, the chinese input method will be invoked 
5. /etc/init.d/iiimf stop
6. edit any c file under vim with cscope_maps.vim plugin
7. move cursor to one token
8. press CTRL-\ s , all reference to this toke will be shown at the
bottom of vim

Additional info:

Comment 1 Luke Huang 2004-11-12 06:40:14 UTC

If you don't think it is a bug, could you please tell me how to solve
under my environment. Thanx a lot

Comment 2 Leon Ho 2005-02-23 01:37:05 UTC

Same problem as #118023. Please look at that bug's comment #8 and see
if it helps.

*** This bug has been marked as a duplicate of 118023 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:06:57 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.