Bernt Hansen <be...@norang.ca> writes: > Nick Dokos <nicholas.do...@hp.com> writes: > >> Bernt Hansen <be...@norang.ca> wrote: >> >>> git bisect identifies the following commit: >>> >>> 206257aa7eb83a0a62f297e7cf0e3a7c32ff6f05 is the first bad commit >>> commit 206257aa7eb83a0a62f297e7cf0e3a7c32ff6f05 >>> Author: Le Wang <le.w...@agworld.com.au> >>> Date: Sun Nov 18 13:39:51 2012 +0800 > > <snip> > >>> >>> Reverting this commit fixes it for me. >>> >> >> FWIW, I cannot reproduce this and I do have the commit you fingered in my >> tree. Could it be the emacs version that makes a difference here? >> >> Mine is >> >> GNU Emacs 24.2.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4) of >> 2012-09-21 >> >> Nick > > Possibly, but this happens for me at work as well which is Windows 23.3 > I think.
For the record, this is my emacs version at work with the same symptoms. GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600) of 2011-03-10 on 3249CTO Thanks, Bernt > > GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 > on raven, modified by Debian > > Bernt
