search

yiran29 / sunpinyin

Automatically exported from code.google.com/p/sunpinyin
0 stars 0 forks source link

xsunpinyin 如何自定义翻页键 #96

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
目前翻页只能靠page_down/page_up，没有找到相关文档介绍可以在
~/.sunpinyin/xim_config
里进行设置

What is the expected output? What do you see instead?
希望能够提供在xim_config里进行设置翻页键的选项，比方说用�
��,/.”来翻页。

What version of the product are you using? On what operating system?
git-latest

Choose a label in "Labels" for it to identify the area this issue belongs
to (like xim, macos, ibus, shuangpin, quanpin), so the appropriate
developer is assigned for your issue timely.
xsunpinyin

Original issue reported on code.google.com by ye.xu....@gmail.com on 15 Apr 2010 at 10:49

GoogleCodeExporter commented 8 years ago

Original comment by tchai...@gmail.com on 15 Apr 2010 at 1:03

GoogleCodeExporter commented 8 years ago 
-/=可以翻页。
但是暂时还没提供可配置功能。

Original comment by mikeandm...@gmail.com on 15 Apr 2010 at 4:50

GoogleCodeExporter commented 8 years ago 
我这里不能用-/=翻页，不知道是不是因为我用德文键盘布局��
�原因。

Original comment by ye.xu....@gmail.com on 15 Apr 2010 at 9:13

GoogleCodeExporter commented 8 years ago 
有可能。可是我手头没有德文键盘，恐怕无法重现。
我个人更觉得是键盘布局设置有问题。

Original comment by mikeandm...@gmail.com on 15 Apr 2010 at 9:58

GoogleCodeExporter commented 8 years ago 
在gentoo上折腾了xorg-server-1.8.0 
-hal，键盘驱动只用evdev，xorg.conf里对输入设备的定义也只含��
�如下4行，

 36 Section "InputClass"
 37         Identifier "evdev-catchall"
 38         Driver "evdev"
 39 EndSection   

不对键盘进行任何额外设置，-/=在德语键盘上确认还是无法��
�页。

Original comment by ye.xu....@gmail.com on 16 Apr 2010 at 10:03

GoogleCodeExporter commented 8 years ago 
其他的输入法呢-/=能翻页么？
话说我还是觉得是德文键盘的问题。

Original comment by mikeandm...@gmail.com on 16 Apr 2010 at 10:33

GoogleCodeExporter commented 8 years ago 
刚刚切换到英文布局，-/=工作完全正常，应该就是德文键盘��
�局的问题了。以前用fcitx都是用,/.来翻页的。

Original comment by ye.xu....@gmail.com on 16 Apr 2010 at 10:39

GoogleCodeExporter commented 8 years ago 
done within commit a6f92882ffe6ee660b8c.

Original comment by mikeandm...@gmail.com on 12 Jul 2010 at 1:05