Bug 532620 - xemacs ediff says Invalid state: Bogus value for 'coding-system-for-read', emacs-internal
Summary: xemacs ediff says Invalid state: Bogus value for 'coding-system-for-read', em...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xemacs-packages-extra
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-03 04:32 UTC by Tim Taiwanese Liim
Modified: 2009-11-19 04:42 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-12 01:34:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tim Taiwanese Liim 2009-11-03 04:32:26 UTC
Description of problem:
    When using ediff-buffers, ediff says
        Invalid state: Bogus value for 'coding-system-for-read', emacs-internal
    This was working fine in F10, but never worked in F11.  Maybe it's
    just a misconfiguration on my F11; if so, please point out the fix.

Version-Release number of selected component (if applicable):
    xemacs-21.5.29-4.fc11.x86_64
    xemacs-packages-extra-20090217-2.fc11.noarch

How reproducible:
    always

Steps to Reproduce:
    1. remove all xemacs packages from an F11 sysem.
    2. yum install xemacs xemacs-packages-extra
    3. run xemacs
    4. M-x ediff-buffers, select 2 buffers

Actual results:
    ediff says
        Invalid state: Bogus value for 'coding-system-for-read', emacs-internal

Expected results:
    ediff should proceed with the usual ediff session.

Additional info:
    n/a

Comment 1 Jerry James 2009-11-03 16:19:50 UTC
This is a known upstream bug, which was fixed with this patch:

http://calypso.tux.org/pipermail/xemacs-cvs/2009-August/005512.html

I'll include that patch the next time I roll out a package.  In the meantime, though, you can work around the problem like this:

M-x customize-variable ediff-coding-system-for-write

... and set the value to escape-quoted.  Yes, the warning you are getting is about the coding system for *read*, and I'm having you customize the one for *write*.  That's because ediff-coding-system-for-read is bound to the value of ediff-coding-system-for-write just before encountering the error.

Comment 2 Tim Taiwanese Liim 2009-11-03 17:26:01 UTC
Jerry,
Thanks for fast response!  The work around is good for me.

Comment 3 Fedora Update System 2009-11-11 15:03:16 UTC
xemacs-packages-extra-20090217-4.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Tim Taiwanese Liim 2009-11-12 01:34:05 UTC
Yes!  It works as advertised!  I'll close this bug.

Comment 5 Tim Taiwanese Liim 2009-11-14 04:50:04 UTC
Was this fix ported to F12 or rawhide?  On my F12 beta I have
    xemacs-packages-extra-20090217-4.fc12.noarch
and I see this msg
    Invalid state: Bogus value for 'coding-system-for-read', emacs-internal

Thanks!

Comment 6 Jerry James 2009-11-16 15:55:40 UTC
Yes, it's been in Rawhide since Nov. 3.  The F-12 update will be available as a 0-day update.

Comment 7 Tim Taiwanese Liim 2009-11-16 17:21:50 UTC
Understand now.  Thank you for your hard work!

Comment 8 Tim Taiwanese Liim 2009-11-18 17:51:19 UTC
Jerry,
Could you double check the existence of the patch in F12?  In my F12 I
did an update just now, and I still have
    xemacs-packages-extra-el-20090217-4.fc12.noarch
which has the bogus value error.
Thanks!

Comment 9 Jerry James 2009-11-18 20:09:07 UTC
-4.fc12 has the problem; -5.fc12 is the fixed version.  I don't see any notes here from the Fedora Update System saying that that version has been pushed to stable.  I'd better go see if I forgot to push a button...

No, my updates page shows that -5.fc12 is in stable.  Maybe we need one more compose before it hits the repository?  Sorry, I thought I got this in on time to be a 0-day update, but apparently not.

Comment 10 Tim Taiwanese Liim 2009-11-18 23:12:15 UTC
Jerry,
Thanks for your effort!  I'll wait a few days and see how it goes.

Comment 11 Tim Taiwanese Liim 2009-11-19 04:42:44 UTC
I see the -5.fc12 just now, and it worked as advertised.  We can now
leave this bug RIP.

Jerry, thanks!


Note You need to log in before you can comment on or make changes to this bug.