Difference between revisions of "WindowMaker"

From Hugo Villeneuve
Jump to: navigation, search
(Truc pour Microsoft Teams)
Line 141: Line 141:
   
   
  +
=Truc pour applications qui ne sauvegardent pas correctement leur configuration=
=Truc pour Microsoft Teams=
 
   
 
Window attributes not set persistently
 
Window attributes not set persistently

Revision as of 16:23, 22 February 2022

Running multiple instances of xterm

Go to the Attributes menu -> Application Specific and select "No application icon" for XTerm.

Then right-click on the docked appicon and select settings. Change the Application Path with arguments section to:

   /bin/sh -c "exec xterm &"

Or:

   /bin/sh -c "exec gnome-terminal &"

Note:

Avec WindowMaker 0.95.4, ça ne semble plus être nécessaire. Il suffit de lancer:

 uxterm


Pour faire capturer un script par le dock

Exemple avec script Kermit

   gnome-terminal --geometry=160x53+380+10 --disable-factory --profile=kermit --title="Kermit   /dev/ttyS0   115200" --name=kermitTerm -e "kermit ~/serial-115200.kermrc"

Exemple connection SSH

   gnome-terminal --disable-factory --name=ssh-hugovil -e "ssh hugo@hugovil.dyndns.org"

Gnome settings

Create the following file if it doesn't exist and change it's permissions:

 chmod 755 ~/GNUstep/Library/WindowMaker/autostart

Content:

#!/bin/sh

gnome-settings-daemon

hvclock

Go to the Attributes menu -> Application Specific and select "Start Hidden".

Emacs

Pour que Emacs lise les valeurs contenues dans ~/.Xdefaults:

 $> xrdb ~/.Xdefaults

Pour prendre en compte les valeurs contenues dans ~/.Xresources:

 $> xrdb ~/.Xresources

Économiseur d'écran

1. Installer xscreensaver

2. Ajouter une entrée dans ~/GNUstep/Defaults/WMRootMenu:

 (Lock, SHORTCUT, "Shift+Delete", EXEC, "xscreensaver-command -lock"),

3. Ajouter une entrée dans ~/GNUstep/Library/WindowMaker/autostart:

 xscreensaver -no-splash &


Themes

Dans le fichier:

   ~/GNUstep/Defaults/WMRootMenu

Remplacer /usr/local/share/WindowMaker par /usr/share/WindowMaker et redémarrer WindowMaker

Raccourcis clavier

Le menu se trouve dans ~/GNUstep/Defaults/WMRootMenu et a une syntaxe simple ; voici pour exemple :

(
Applications,
(Run..., SHORTCUT, F2, EXEC, "%a(Run,Type command to run)"),
(XTerm, SHORTCUT, F3, EXEC, "xterm -sb -sl 2000"),
("Hide All", HIDE_OTHERS),
("Show All", SHOW_ALL),
(Appearance, OPEN_MENU,
"~/GNUstep/Library/WindowMaker/appearance.menu"),
("Gaffe!", (Reboot, EXEC, "sudo reboot"), (Halt, EXEC, "sudo halt")),
("xvnc", EXEC, "xterm -e xvncviewer %a(Enter Host)"),
(Lock, SHORTCUT, "Shift+Delete", EXEC, "xscreensaver-command -lock"),
("Exit Window Maker", SHORTCUT, "Control+Shift+Delete", EXIT)


Comment avoir un icone pour une application qu n'en n'a pas

Utile afin de pouvoir "docker" une application qui ne produit pas d'icône.

1. Right click on the title bar

2. Click Attributes

3. Select Advanced Options from the pull down menu

4. Select Emulate Application Icon

5. Click Save


Configuration du clavier

Sous Debian, les changements dans /etc/default/keyboard ne sont pas pris en compte dans WindowMaker:

IBus can also sometimes override settings from /etc/default/keyboard. The keyboard setup dialog in GNOME 3 will modify IBus's configuration directly, but for users of other X environments, you can use the ibus-setup command to modify the settings for IBus. To force it to defer to the settings from /etc/default/keyboard, run ibus-setup, go to the Advanced tab, and check Use system keyboard layout.

Source: https://wiki.debian.org/Keyboard


Comment redimensionner une fenêtre

David Reviejo <dreviejo@arrakis.es> best summed up this answer:

   Alt+Left click and drag
   to move the window.
   Alt+Right click and drag
   to resize (by moving the nearest window corner)

Another move/resize tip: while you are moving or resizing a window, you can change the move/resize mode by pressing the SHIFT key."

Source: http://www.windowmaker.org/docs/FAQ.html

Commande pour éteindre (power off)

The ConsoleKit commands in slacklock should work. (Someone please verify this.) However, there is a simpler way: use systemctl. For example, systemctl poweroff issues an immediate power off. Systemd will check authorizations in much the same way ConsoleKit checks them on my system.

Source: https://github-wiki-see.page/m/linuxcsuf/linuxcsuf/wiki/Window-Maker-Howto


Truc pour applications qui ne sauvegardent pas correctement leur configuration

Window attributes not set persistently

If you find that window attributes that you have saved for a certain window are not persistent, this is probably because you are trying to override hints set by the application itself that change the way the window manager treats the window. For instance, a window might set a Motif hint requesting that the window manager does not decorate the window with a titlebar. However, when you untick the Disable titlebar option and hit Save in Window Attributes you find that the window does not have a titlebar when it is next launched.

This problem arises because Window Maker will only write window settings to the settings file that it considers to be non-default. However, Window Maker will not update what it considers to be a default setting to take into account window hints. So for a window that has no titlebar, hitting the Save button after unticking Disable titlebar will do nothing because Window Maker incorrectly considers that to already be the default setting.

To work around this, open the Window Attributes dialogue for the window in question and, without making any changes whatsoever, hit the Save button. This will write the hint set settings that Window Maker considers to be non-default to file. Then, open ~/GNUstep/Defaults/WMWindowAttributes in a text editor and you should find the settings in question for that window written there. You can now change them to your preferred values, for instance: change NoTitlebar = Yes; to NoTitlebar = No;

xsessionrc

Ajouter à ${HOME}/.xsessionrc:

   # Load resources
   xrdb ${HOME}/.Xresources

.xsessionrc n'a pas besoin d'être éxécutable (mode 644 suffit).


~/.xinitrc is only read when you start a GUI session with startx (or otherwise calling xinit) after logging in in text mode. So that won't help you.
Whether ~/.bash_profile, ~/.profile, ~/.xprofile and ~/.xsessionrc are read when logging in with a display manager depends on how the display manager is configured and what session type you select when logging in. As far as I can tell, at least on Debian jessie (I haven't looked if this has changed since then):
   /usr/share/lightdm/lightdm.conf.d/01_debian.conf tells Lightdm to use /etc/X11/Xsession as the session startup script.
   /etc/X11/Xsession (via /etc/X11/Xsession.d/40x11-common_xsessionrc) loads $USERXSESSIONRC which is ~/.xsessionrc.
So ~/.xsessionrc should work, at least on Debian jessie.

System settings

Lancer la commande:

 gnome-control-center