1 Jun 2005 08:55
8 Jun 2005 08:19
ion-3ds-20050607
(Retry) This release mostly features minor bugfixes and other improvements. The most visible non-bugfix changes are: * Faster "fontset" filling kludge: only -misc-fixed-* fonts are tried. Ion should now load faster in UTF-8 environments, and usually with no less fonts in the fontset than before. (UTF-8 string drawing still does not fully utilise these fonts under XFree86, but it does under XOrg.) * Experimental auto-show-completions support, which is also on by default now. In this mode the Tab key can be used to cycle forward through the completions, and Shift+Tab backwards. Modify the settings seen in the new mod_query.lua to get normal Tab-completion, or change the completion delay. * The release scripts do not run automatically autoconf anymore so maybe a few more people would look into the README first. -- -- Tuomo
8 Jun 2005 17:37
A question..
I am trying ion2/3 under Mepis(Debian based distribution). The wm was installed with apt-get (did not compile form sources). Under ion2 any function key prodices the following error also: (gnome-terminal:8117): Gdk-CRITICAL **: gdk_gc_get_colormap: assertion `GDK_IS_GC (gc)' failed is there a way to fix it? -ishwar
8 Jun 2005 17:43
ion3 question
If I run ion3 (Mepis + debian based linux distribution), I see also see the error messages: ion3: Encoding in LC_CTYPE (en_US) and encoding reported by nl_langinfo(CODESET) (ISO-8859-1) do not match. ion3: Reverting locale settings to "C". /usr/lib/ion3/ion-statusd: statusd_mail.lua:73: assertion failed! (gnome-terminal:8338): Gdk-CRITICAL **: gdk_gc_get_colormap: assertion `GDK_IS_GC (gc)' failed Any pointers will be appreciated. -ishwar
8 Jun 2005 19:20
Re: A question..
On 2005-06-08, Ishwar Rattan <ishwar@...> wrote: > (gnome-terminal:8117): Gdk-CRITICAL **: gdk_gc_get_colormap: assertion > `GDK_IS_GC (gc)' failed Not an ion problem. > is there a way to fix it? Don't use gnome cruft. -- -- Tuomo
8 Jun 2005 19:24
Re: ion3 question
On 2005-06-08, Ishwar Rattan <ishwar@...> wrote: > If I run ion3 (Mepis + debian based linux distribution), I see > also see the error messages: > > ion3: Encoding in LC_CTYPE (en_US) and encoding reported by > nl_langinfo(CODESET) (ISO-8859-1) do not match. LC_CTYPE should be of the form foo_BAR.encoding, e.g. en_US.ISO-8859-1 in your case. Otherwise X may become confused with the encoding to use. > /usr/lib/ion3/ion-statusd: statusd_mail.lua:73: assertion failed! *Sigh*. Another system with the MAIL environment variable unset... -- -- Tuomo
8 Jun 2005 21:16
Re: Incorrect key binding handling for `similar' bindings defined for different window types
Tuomo Valkonen <tuomov@...> writes: > On 2005-05-31, Jeremy Maitin-Shepard <jbms@...> wrote: >> When I press "Mod4+K" followed by "Mod4+n", WFrame.switch_next is >> called, rather than ionws_move_current. > That's how it should work. Please explain why. Note that the switch_next command is bound to "Mod4+K n"; the ionws_move_current command is bound to "Mod4+K Mod4+n". Thus, when I type "Mod4+K Mod4+n", I expect the ionws_move_current command to be triggered, rather than the switch_next command. -- -- Jeremy Maitin-Shepard
8 Jun 2005 21:53
Re: Incorrect key binding handling for `similar' bindings defined for different window types
Tuomo Valkonen <tuomov@...> writes: > Submaps default to "AnyModifier" pseudo-modifier and thus catch anything. > Since the frame is inside the workspace in the region hierarchy, the frame > bindmap has precedence over the workspace bindmap, and this binding gets > called. If you want only "n" with no modifiers set be catched, use > "NoModifier+n". Thanks. -- -- Jeremy Maitin-Shepard
8 Jun 2005 21:35
Re: Incorrect key binding handling for `similar' bindings defined for different window types
On 2005-06-08, Jeremy Maitin-Shepard <jbms@...> wrote: > Tuomo Valkonen <tuomov@...> writes: > >> On 2005-05-31, Jeremy Maitin-Shepard <jbms@...> wrote: >>> When I press "Mod4+K" followed by "Mod4+n", WFrame.switch_next is >>> called, rather than ionws_move_current. > >> That's how it should work. > > Please explain why. Note that the switch_next command is bound to > "Mod4+K n"; the ionws_move_current command is bound to "Mod4+K Mod4+n". > Thus, when I type "Mod4+K Mod4+n", I expect the ionws_move_current > command to be triggered, rather than the switch_next command. Submaps default to "AnyModifier" pseudo-modifier and thus catch anything. Since the frame is inside the workspace in the region hierarchy, the frame bindmap has precedence over the workspace bindmap, and this binding gets called. If you want only "n" with no modifiers set be catched, use "NoModifier+n". -- -- Tuomo
9 Jun 2005 12:59
Re: ion3 question
On Wednesday 08 Jun 2005 18:24, Tuomo Valkonen wrote: > > > /usr/lib/ion3/ion-statusd: statusd_mail.lua:73: assertion failed! > > *Sigh*. Another system with the MAIL environment variable unset... Perhaps the error message should read "MAIL variable unset"? -- --
RSS Feed