Brett Viren | 3 Dec 2011 19:50
Picon

Git tags and correlated versions

It seems that there are no tags in git for recent releases of sawfish,
librep and rep-gtk (I didn't check the pager).

The missing tags are:

librep: 0.92.1b, 0.92.2
rep-gtk: 0.90.8
sawfish: 1.8.91

Also, could the required versions of librep and rep-gtk for each
sawfish release be kept in some text file in the sawfish source?
Keeping it on the wiki is good but if it were in the sawfish source it
would help automate building new releases.

For the beta release and snapshot, which version of librep and rep-gtk
are needed?

Thanks for considering.

-Brett.

---
--
Sawfish ML

Brian | 4 Dec 2011 22:39
Picon

Re: Why does my configure file report Warning ?

On Fri, Nov 25, 2011 at 6:15 PM, z_axis <z_axis <at> 163.com> wrote:
>> cat ~/.sawfish/my-init.jl
<<snip>>
> (setq restart-menu
>    '(("ok" (system "sudo /sbin/shutdown -r now &"))
>      ("cancel" (no-operation))))
>
> (setq logout-menu
>    '(("ok" (quit)) ("cancel" (no-operation))))
>
> (setq quit-menu
>    '(("ok" (system "sudo /sbin/shutdown -p now &"))
>      ("cancel" (no-operation))))
>
> (setq main-menu
<<snip>>

>> sawfisawfish --batch -l compiler -f compile-batch my-init.jl
>
> my-init.jl:36: At top-level:
> my-init.jl:36: warning: referencing undeclared free variable `restart-menu'
> my-init.jl:40: warning: referencing undeclared free variable `logout-menu'
> my-init.jl:43: warning: referencing undeclared free variable `quit-menu'
> my-init.jl:52: warning: referencing undeclared free variable `main-menu'

You may want to read the section "Using global variables and
constants" in "Successful Lisp" at
http://www.psg.com/~dlamkins/sl/chapter04.html

In short, you need to use a (defvar ...) before you setq your global
(Continue reading)

janemba | 5 Dec 2011 12:47
Picon

Remove border for xterm

Hello,

I'd like to remove all the border for xterm window. So I add a window rule and I set
"Frame Type" to "none" into "Appareance" tab. But this doesn't work. Do you know
how can I do this ?

Regards

---
--
Sawfish ML

fuchur | 5 Dec 2011 13:02
X-Face
Face
Picon

Re: Remove border for xterm

Hi,

On Mon, 05 Dec 2011 12:47:37 +0100
wrote janemba <cap.janemba <at> gmail.com>:

>Hello,
>
>I'd like to remove all the border for xterm window. So I add a window rule and I set
>"Frame Type" to "none" into "Appareance" tab. But this doesn't work. Do you know
>how can I do this ?
>
>Regards
>
>
>---
>--
>Sawfish ML
>

Here i have no problems. I have add a screenshot by this mail with the
rule. Maybe you have a other rule after the Xterm rule and these rule
readd the border?

--

-- 
Regards,
Fuchur

GPG Fingerprint: CA3B 8204 5B3E 6D48 6D53  C116 E5BC 70D5 B8D7 B2B0
(Continue reading)

janemba | 5 Dec 2011 14:47
Picon

Re: Remove border for xterm

On 12/05/2011 01:02 PM, fuchur wrote:
> Hi,
>
> On Mon, 05 Dec 2011 12:47:37 +0100
> wrote janemba <cap.janemba <at> gmail.com>:
>
>> Hello,
>>
>> I'd like to remove all the border for xterm window. So I add a window rule and I set
>> "Frame Type" to "none" into "Appareance" tab. But this doesn't work. Do you know
>> how can I do this ?
>>
>> Regards
>>
>>
>> ---
>> --
>> Sawfish ML
>>
> Here i have no problems. I have add a screenshot by this mail with the
> rule. Maybe you have a other rule after the Xterm rule and these rule
> readd the border?
>
Hello,

Thx for your answer. Maybe you're right but I don't know what can
override this rule in sawfish. In "Appearance" menu I set "StyleTab"
theme. And here is my .Xdefaults on XTerm :

XTerm*scrollBar:        false
(Continue reading)

Michal Jaegermann | 5 Dec 2011 18:49

Re: Remove border for xterm

On Mon, Dec 05, 2011 at 12:47:37PM +0100, janemba wrote:
> 
> I'd like to remove all the border for xterm window. So I add a
> window rule and I set "Frame Type" to "none" into "Appareance"
> tab. But this doesn't work. Do you know how can I do this ?

How you are matching that window in your rule?  Some elements, like
name, are likely adjusted dynamically.  Check with 'xprop' (id you
can get by running 'xwininfo').

   Michal

---
--
Sawfish ML

janemba | 6 Dec 2011 10:00
Picon

Re: Remove border for xterm

On 12/05/2011 06:49 PM, Michal Jaegermann wrote:
> On Mon, Dec 05, 2011 at 12:47:37PM +0100, janemba wrote:
>> I'd like to remove all the border for xterm window. So I add a
>> window rule and I set "Frame Type" to "none" into "Appareance"
>> tab. But this doesn't work. Do you know how can I do this ?
> How you are matching that window in your rule?  Some elements, like
> name, are likely adjusted dynamically.  Check with 'xprop' (id you
> can get by running 'xwininfo').
>
>    Michal
>

Hello,

I've made a screenshot for the window rule, you can see it
in attachment. I used "Class" item to match my xterm window.

For 'xprop' I have the following value :
  $ xprop -id 0x240000d | grep -i class               
      WM_CLASS(STRING) = "xterm", "XTerm"

Regards,

Rafal Kolanski | 7 Dec 2011 01:51
Gravatar

Synthesizing events in 1.8.90 is glitchy for me

Hello Sawfish Users,

I have been using 1.8.90 on Ubuntu, first on 11.04 with the "Classic"
view, then on 11.10 with the "gnome fallback" and then migrated to XFCE.
However, since my upgrade to 11.10 I am having numerous problems with
synthesizing events.

Basically, I have a setup like this (GTK_IM_MODULE=xim , so I can use
~/.XCompose):

;; sending multiple events to the current input focus (for UTF-8 input
hacks)

(defun synthesize-event-input-focus (e)
  (synthesize-event e (input-focus)))
(defun events-input-focus (es) (mapcar synthesize-event-input-focus es))

;; polish bindings for ąćęłńóśżźĄĆĘŁÓŃŚŻŹ

(bind-keys window-keymap "Super-a"
  '(events-input-focus `("Multi_key" ";" "a")))
;; etc.

This means when I press my windows key and "a", sawfish sends out:
  Multi_key ; a
and the result of that I expect to be "ą".

Most of the time, I get the expected result. Except sometimes Super_L
and Super_R don't work reliably... then I hold in Super+a and get
something like:
(Continue reading)

Teika Kazura | 7 Dec 2011 13:48

Re: Synthesizing events in 1.8.90 is glitchy for me

Dzień dobry, Rafal Kolanski.

If you use that key only as Multi_key, never as Super, than I recommend
xmodmap instead of event synthesis, like this:

# 123 should be replaced appropriately. Use xev to know the keycode.
$ xmodmap -e "keycode 123 = Multi_key" 
# Usually mod4. use $ xmodmap -pm to know where Super is assigned to.
$ xmodmap -e "remove Mod4 = Super_L Super_R"

To be safe, disable autorepeat for the super key:
$ xset -r 123

Some years ago, this was necessary for my keyboard to work as expected,
although it seems to have gone:
$ xset r rate 200 50 # Read man xset for the meaning.

# I've never used Multi_key, but Wikipedia says it's released first
# unlike AltGr.

You know, there're many many variants of keyboards, and we always have
difficutly in communication. What's worse is that keyboard is (also) a
messy part of X, although most people can manage to live. ;)

See also:
http://hektor.umcs.lublin.pl/~mikosmul/computing/articles/custom-keyboard-layouts-xkb.html


Do widzenia. (I don't speak Polish, but Dzień dobry must mean "Day good.")
Teika (Teika kazura)
(Continue reading)

Teika Kazura | 7 Dec 2011 13:48

Re: Remove border for xterm

Hi, janemba.

Seems your configuration is right, but setting the rule to XTerm,
instead of ^XTerm/xterm$ may fix it. (But I don't think it's likely.)

Window rules are applied to *new* windows, so you have to set them
beforehand. Are you sure Sawfish is invoked *before* xterms? Does your
problem hold for xterms you invoke *after* Sawfish starts? Does
restarting Sawfish fix?

If all of my guess above fail, I'm clueless. X<

Regards,
Teika (Teika kazura)

---
--
Sawfish ML


Gmane