Bug 78234 - x11/eterm invalids compose character definition
Summary: x11/eterm invalids compose character definition
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Jimmy Olgeni
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-01 10:20 UTC by Frank Altpeter
Modified: 2006-03-21 00:11 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Altpeter 2005-03-01 10:20:04 UTC 
        After upgrading the port x11/eterm to the current 0.9.3
        revision, a previously working compose character definition
        doesn't work anymore.
        Doing a downgrade to 0.9.2 brings back the feature, so in my
        understanding this proves to be a problem within Eterm.

Fix: 

Downgrade to version 0.9.2 - I tried to contact the
        "developers" through the recommended way of speaking in the IRC
        channel, but nothing happened. Contacted maintainer per email,
        awaiting reply. I suggest either marking the port as BROKEN or
        revert the port to 0.9.2 until this gets fixed, since i don't
        know if there are more things broken in the 0.9.3 release, but
        if someone does rely on compose keys for typing special
        characters, this is quite bad.
How-To-Repeat:         # Define RIGHT_ALT as compose character
        echo 'keycode 113 = Multi_key' >$HOME/.xmodmap
        xmodmap $HOME/.xmodmap
        # Start a new Eterm here
        # Press RIGHT_ALT + u + " and you get u" instead of ü
Comment 1 Volker Stolz freebsd_committer freebsd_triage 2005-03-01 16:31:20 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->olgeni

Over to maintainer
Comment 2 Jimmy Olgeni freebsd_committer freebsd_triage 2006-03-21 00:10:45 UTC 
State Changed
From-To: open->closed

The port was fixed.