Re: Cant type unicode in emacs any more

[Rusi]

On Friday, January 2, 2015 10:53:40 AM UTC+5:30, Rusi wrote:
> On Friday, January 2, 2015 8:40:07 AM UTC+5:30, Rusi wrote:
> > On Friday, January 2, 2015 8:27:50 AM UTC+5:30, Rusi wrote:
> > > On Wednesday, April 30, 2014 5:49:48 PM UTC+5:30, Stefan Monnier wrote:
> > > > > Why is emacs (effectively) looking into .XCompose?
> > > > 
> > > > Probably a bug somewhere.
> > > > 
> > > > > Because currently the behavior I am seeing is:
> > > > > - Other apps *add* contents of .XCompose to the builtin composeables
> > > > > - Emacs *replaces* builtins with .XCompose
> > > > 
> > > > Please report it via M-x report-emacs-bug.  But we fixed a problem in
> > > > this area since the last release, so please try it with the
> > > > 24.3.90 pretest, in case the problem is already solved.
> > > > 
> > > > 
> > > >         Stefan
> > > 
> > > Now with emacs 24.3.1 on ubuntu 14.10
> > > and now its not working at all.
> > > 
> > > Just for context
> > > Earlier after
> > > $ setxkbmap -variant altgr-intl -option compose:menu
> > > 
> > > I could use compose sequences.
> > > However it would stop working in emacs if there was a ~/.Xcompose file
> > > 
> > > Now compose is not working in emacs at all -- with or without file -- and 
> > > its 
> > > working elsewhere  - shell, python-idle etc
> > 
> > 
> > Just checked the Eric's unsetting XMODIFIERS method above worked
> 
> And then it stopped working
> 
> And then followed 
> http://askubuntu.com/questions/410499/make-setxkbmap-preferences-being-set-at-startup
> Go down to org -> desktop -> desktop -> input-sources
> And make xkb-options have value
> ['compose:menu']
> And now its working again

The need to unset XMODIFIERS is completely erratic
Sometimes needed, sometimes not.