ibus.el

ibus.el 0.2.1

  1. Series 0.2
  2. 0.2.1

Milestone information

Project:
ibus.el
Series:
0.2
Version:
0.2.1
Released:
 
Registrant:
IRIE Shinsuke
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon ibus-el-0.2.1.tar.gz (md5, sig) Version 0.2.1 936
last downloaded 8 weeks ago
Total downloads: 936

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

* Added support for vim-mode
* Added libexec directories to search paths for `ibus-agent-file-name'
* Changed to execute fallback command in latin mode to simulate original behavior for the key event (IBus issue #1058)
* Modified custom types of `ibus-kana-onbiki-x-keysym' and `ibus-kana-onbiki-key-symbol' so that they can be disabled
* Modified to reset cursor color in consideration of color themes
* Modified not to unnecessarily set cursor color for non-X frame
* Modified not to unnecessarily check current buffer while command is running
* Fixed bug: Keymap might not be updated when switching input focus from non-X frame to X frame
* Fixed bug: ibus-mode is abnormally exited when automatically turning off monitor for power saving
* Fixed bug: If starting emacs-w3m in one of multiple frames, ibus-mode's keymaps are incorrectly disabled in one of the other buffers
* Fixed problem (maybe): ibus-el-agent crashes if failing to connect to X display when ibus-mode starts or display is changed (RH bug #627358)

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.