Bug 718089

Summary: Emacs no longer sees C-SPC
Product: [Fedora] Fedora Reporter: Jonathan Corbet <corbet>
Component: emacsAssignee: Karel Klíč <kklic>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jonathan.underwood, kklic, rvokal, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-06 15:41:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jonathan Corbet 2011-06-30 22:50:58 UTC
Description of problem:

I can no longer set the mark with C-SPC, leading to unhealthy levels of grumpiness.

Version-Release number of selected component (if applicable):
emacs-23.3-7.fc16.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Hit C-SPC
2. Watch nothing happen
3. Keep watching, nothing continues to happen
4. (one can keep that up for a while).
  
Actual results:

Nothing

Expected results:

Mark should be set.

Additional info:

xev sees control-space just fine, just like on an unaffected system:

KeyPress event, serial 32, synthetic NO, window 0x2400001,
    root 0x159, subw 0x0, time 122253050, (121,108), root:(1132,1071),
    state 0x4, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (00) ""
    XmbLookupString gives 1 bytes: (00) ""
    XFilterEvent returns: False

Emacs, instead, does not see the key event at all, as if somebody were filtering it out.

(Just checked, running "emacs -nw" in gnome-terminal gets the same result).

This all worked until quite recently.

Comment 1 Karel Klíč 2011-07-01 15:43:16 UTC
I tried emacs-23.3-7.fc16.x86_64 on Fedora 15 and C-SPC sets mark as usual.

I'm going to check it on Rawhide...

Comment 2 Akira TAGOH 2011-07-06 02:17:47 UTC
I guess because ibus is running on your machine?

Comment 3 Jonathan Corbet 2011-07-13 21:00:48 UTC
Was that last comment aimed at me?  I do have various ibus processes running, not through any explicit action on my part.  You're saying that ibus has something to do with the problem?

Comment 4 Akira TAGOH 2011-07-14 04:42:47 UTC
as you may know, C-SPC is used to be triggered to enable/disable IM. this is a well-known issue and not a bug at all. if you don't like that, you could simply disable XIM support in Emacs by adding "Emacs*useXIM: false" in .Xresources say. or you even have a workaround to set a mark with C-@.

Comment 5 Jonathan Corbet 2011-07-14 12:54:48 UTC
If emacs thinks that C-SPC is bound to set-mark, but it never actually sees the keystroke, that strikes me as a bug.  It happened recently - it's a regression.

I've tried adding the .Xresources line, but the behavior does not change.

C-@ works, but is a rather less convenient keystroke.  If it's really the case that C-SPC is no longer available, I guess I'll just bind set-mark to something else, but it doesn't seem like that should be necessary.

Comment 6 Akira TAGOH 2011-07-15 01:09:06 UTC
I'm not sure if it's still read automatically. try xrdb .Xresources and restart all of emacs processes then.

Comment 7 Jonathan Corbet 2011-10-06 15:34:18 UTC
Well, I have no clue what changed, but I noticed this morning that the problem has magically vanished.  Unless somebody else has problems (and it doesn't look that way) I think this one can probably be closed.

Comment 8 Karel Klíč 2011-10-06 15:41:28 UTC
Ok, thanks.