This has been fixed. Update, rebuild and try it again.
Thanks Nick, that fixes it. I should have tried updating before reporting
the bug.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest
A similar bug was fixed some days ago, make sure your CVS is up to date.
Jan D.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
> > Note that the yanked copy is different than the text we copied. It
> > shows up as a '?' character.
>
> I've tracked the bug down to 2 lines in lisp/term/x-win.el:
In GNU Emacs 22.0.91.4 (i686-pc-linux-gnu, GTK+ Version 2.8.20)
of 2006-11-19 on chrislap
2006-11-20 Jan Djärv <[EM
> Note that the yanked copy is different than the text we copied. It
> shows up as a '?' character.
I've tracked the bug down to 2 lines in lisp/term/x-win.el:
In x-select-text():
;; ICCCM says cut buffer always contain ISO-Latin-1
(encode-coding-string text 'iso-latin-1)
In x-cut-buffer-or
Prepare a file containing a Czech "e-with-a-hook" character (followed
by a newline) in Windows 1250 encoding:
$ printf "\354\n" > /tmp/file.txt
Ensure DISPLAY is set, and run Emacs:
$ emacs -Q
Tell Emacs to prefer the Windows 1250 coding system:
M-x eval-expression RET (prefer-coding-sys
