Getting Started with Scrotwm?

finwin · 2011-10-07 19:05:05

gutterslob wrote:

^If you read my previous post explaining it, you'll understand that we're just overlaying dzen2 on top of a portion of your scrotwm panel. In your case, it looks like your dzen2's width/length is a tad long, hence the covering of the currently selected app's title name/class.
Try shortening the width of your dzen2 panel or adjusting its x-axis offset, or both (the numbers after the -w and -x options of the conky/dzen2 command in your scrotbar.sh

I already tried that but it only moves dzen panel

el_koraco · 2011-10-07 19:07:28

gutterslob wrote:

You're referring to usb automounting, right?
Most people usually start dbus with
eval `dbus-launch --sh-syntax --exit-with-session`
...in their ~/.xinitrc, but since you already mention dbus running, I'm not quite sure. For what it's worth, I tend to use mc or ranger and don't get usb automounting anyway. You might want to read up on kernel-based automounting via AutoFS. It's in your repos, Links: http://wiki.debian.org/AutoFs / https://wiki.archlinux.org/index.php/Autofs
Also, I tend to start scrot with just a plain "exec scrotwm", though I don't think that matters here.

I missed this one. Edit: deleting a bunch of nonsense.
And, it works!
Slobbers is tha man!

Last edited by el_koraco (2011-10-07 19:27:54)

gutterslob · 2011-10-09 16:37:06

finwin wrote:

I already tried that but it only moves dzen panel

Sorry for overlooking this, finwin.
Okay, your monitor width seems to be 1440pixels , and since your info isn't that long, why not make your dzen2 400 pixels long and give it an x-offset of 1040 pixels (400 + 1040 = 1440)try something like this in your scrotbar.sh

exec conky -d -c "$HOME/bin/conkyrc_colorcli" | dzen2 -fg "#a6a6a6" -bg "#000000" -ta right -w 400 -h 13 -x 1040 -y 1 -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* &
exit 0

You might need to make some tiny adjustments, but it should be close.

Hope this helps.

el_koraco wrote:

I missed this one. Edit: deleting a bunch of nonsense.
And, it works!
Slobbers is tha man!

Good to know. I'm curious about the "bunch of nonsense" you edited out. More often than not, this sorta "nonsense" has some degree of relevance, especially when troubleshooting someone else's problems (HAL related stuff, for example)

Last edited by gutterslob (2011-10-09 16:43:28)

el_koraco · 2011-10-09 16:50:19

Nah, the nonsense was entirely up to me. I was sure the problem was with the nature of archaic packages in Squeeze, since thunar-volman in Squeeze still depends on hal, unlike the XFCE 4.8 Thunar. I was launching dbus with --exit-with-session, but without the eval and syntax line, which was obviously not setting all the permissions right.

If I understood the whole new development correctly, systemd will soon take on the role of the session manager, so that should put a stop to the confusion as to the proper launching of ck, pk, dbus and gang in the session. Unless they tie everything down to the display managers, in which case either nothing will change, or stuff will be more complicated.

finwin · 2011-10-10 19:30:16

gutterslob wrote:

exec conky -d -c "$HOME/bin/conkyrc_colorcli" | dzen2 -fg "#a6a6a6" -bg "#000000" -ta right -w 400 -h 13 -x 1040 -y 1 -fn -*-profont-*-*-*-*-11-*-*-*-*-*-*-* &
exit 0

Thanks! big_smile

h8uthemost · 2011-10-12 22:21:51

Ok got a few questions here. The first is with conky. I set it to where it will autostart. But when I start up scrotwm there's a red outline around conky. So that means when I open another app like Chrome, the window splits. One window with conky and my desktop and the other window with Chrome. Instead of Chrome opening and taking up the whole window. Like it should.

Anyone come across this? What I put in my scrotwm.sh is conky &. Oh yeah, and conky is starting on the left side of the screen for some reason. I haven't touched my conky config that I use with OB, so I figured it would just start on the left side like I want it.

EDIT: When I killed conky and tried starting it from terminal, the app started, but I get this error in terminal:

Fatal Error: The Server Is Not Running

Second, how exactly can I replace the scrotwm bar with tint2? I'm not positive if I'm going to leave it this way, but I want to try this for a while. I kind of missing having a tray, and instead of using a tray app I thought I would just use tint2 instead.

And third, I'm inputting new keybinds into my scrotwm.conf, but they're not enabling. I'm used to OB, so I'm looking for something to Reconfigure scrotwm but can't find it(since this is what I would always do OB after inputting a new keybind to get it to show up). And even if I log out and back into scrotwm the keybind still won't work.

I'm just starting with a simple one, trying to get thunar to bind to a key. This is what I put in my scrotwm.conf:

#bind[thunar] = MOD+f

I tried it commented like it is and even un-commented. I even tried inputting a few other keybinds that I'm used to in OB, but they don't work either. The keybinds that came with scrotwm are working, so why aren't mine?

EDIT: According to this page, all I need to do is put this at the bottom of the scrotwm.conf and restart using Mod+q:

program[thunar] = thunar
bind[thunar] = MOD+f

But that doesn't work either.

Thanks for any help.

Last edited by h8uthemost (2011-10-12 23:09:36)

PackRat · 2011-10-13 01:45:48

Conky is opening as a window so it's getting tiled like the other apps. If you want conky in scrotwm, it needs to be in the status bar

in the ~/.scrotwm.conf

bar_action              = conky
bar_delay               = 5

and configure your .conkyrc like this:

out_to_x no
out_to_console yes
update_interval 1.0
total_run_times 0
use_spacer none
TEXT
<conky info in a single line>

That's from the Arch wiki; worth a read if you're new to scrotwm : https://wiki.archlinux.org/index.php/Scrotwm

Tint2 can't be substituted for the stausbar; the only way I have gotten a tray to work is to create a quirk for the tray program so that it always floats (FLOAT + ANYWHERE) and have it autostart; the man page and default .scrotwm.conf have examples of quirks I know this method works for tint2, but it's kind of annoying, If a tray app is a must, maybe window manager from scratch or awesome would be better.

What are you using for the Mod key? In the link to the other post, that user changed his mod key from the default (Alt) to the Super key - there is a line to do that in the .scrotwm.conf. If you haven't made a change, Alt-f should be starting thunar.

Last edited by PackRat (2011-10-13 01:49:49)

h8uthemost · 2011-10-13 02:02:54

Thanks a lot, packrat. Kinda sucks about conky and tint2 though. I mean conky on the bar is no big deal, but I really do having system tray. And according to you, and what I've been reading about it, it seems like a pain to get working.

I tried both Alt and Super key in the example I gave, but alas, no-go.

Ah well, guess I'll try a different wm. I was hoping to getting accustomed to Scrotwm since it has such an easy config file. Awesome and it's Lua is a nightmare. Guess I'll keep shopping around for a tiling wm that will fit me.

Thanks again.

EDIT: Actually wmfs is pretty great so far. The config file is moderately easy, and I'm loving the native status tray.

Looks like there's no wmfs thread here though. Guess I'll have to start one,

Thanks for the recommendation.

Last edited by h8uthemost (2011-10-13 02:49:30)

h8uthemost · 2011-10-13 19:02:20

Well, I'm switching backing to scrot as it definitely seems the fastest. But unfortunately it's the hardest(for me) to get keybinds to work.

I'm doing like I posted above, I'm putting this at the end of my scrotwm.conf:

program[thunar]         = thunar
bind[thunar]            = MOD+f

But still no-go. And I haven't changed anything else in my config, so the mod key hasn't been changed. Am I putting this in the right section of my config? I'm putting it at the very end of the file, after where it says:

# EXAMPLE: define firefox program and bind to key
# program[firefox]    = firefox http://scrotwm.org/
# bind[firefox]        = MOD+f

And is my scrotwm.conf in the wrong place? It's in my Home directory.

Grrr... From what I keep reading I'm doing everything correctly, but for some reason my keybinds are not working. Somebody here has to see what I'm doing wrong.

EDIT: I finally got keybinds working by editing the scrotwm.conf that's located in my /etc/. I mean...it works, but I would prefer to just edit the scrotwm.conf in my Home directory instead of opening /etc/ as root all the time.

Anyone happen to know why the scrotwm.conf in my directory isn't taking my keybinds?

Last edited by h8uthemost (2011-10-13 19:17:07)

PackRat · 2011-10-13 23:01:57

h8uthemost wrote:

Well, I'm switching backing to scrot as it definitely seems the fastest. But unfortunately it's the hardest(for me) to get keybinds to work.
I'm doing like I posted above, I'm putting this at the end of my scrotwm.conf:
program[thunar]         = thunar
bind[thunar]            = MOD+f
But still no-go. And I haven't changed anything else in my config, so the mod key hasn't been changed. Am I putting this in the right section of my config? I'm putting it at the very end of the file, after where it says:
# EXAMPLE: define firefox program and bind to key
# program[firefox]    = firefox http://scrotwm.org/
# bind[firefox]        = MOD+f
And is my scrotwm.conf in the wrong place? It's in my Home directory.
Grrr... From what I keep reading I'm doing everything correctly, but for some reason my keybinds are not working. Somebody here has to see what I'm doing wrong.
EDIT: I finally got keybinds working by editing the scrotwm.conf that's located in my /etc/. I mean...it works, but I would prefer to just edit the scrotwm.conf in my Home directory instead of opening /etc/ as root all the time.
Anyone happen to know why the scrotwm.conf in my directory isn't taking my keybinds?

The configuration file needs to be a hidden file in your home directory: ~/.scrotwm.conf
so don't forget the "."

Last edited by PackRat (2011-10-13 23:02:55)

h8uthemost · 2011-10-13 23:14:10

That definitely did it! Damn...it even shows the "." on the Scrotwm manpage. Can't believe I didn't catch that I've been searching and searching try to find what the problem could be.

Finally my headache can go away.:) Thank you very much, packrat.

PackRat · 2011-10-17 13:23:17

el_koraco wrote:

gutterslob wrote:
You're referring to usb automounting, right?
Most people usually start dbus with
eval `dbus-launch --sh-syntax --exit-with-session`
...in their ~/.xinitrc, but since you already mention dbus running, I'm not quite sure. For what it's worth, I tend to use mc or ranger and don't get usb automounting anyway. You might want to read up on kernel-based automounting via AutoFS. It's in your repos, Links: http://wiki.debian.org/AutoFs / https://wiki.archlinux.org/index.php/Autofs
Also, I tend to start scrot with just a plain "exec scrotwm", though I don't think that matters here.
I missed this one. Edit: deleting a bunch of nonsense.
And, it works!
Slobbers is tha man!

How about posting your .xinitrc - I'd like to see how you did this.

gutterslob · 2011-10-17 14:02:34

PackRat wrote:

How about posting your .xinitrc - I'd like to see how you did this.

You asking me or el-koraco? .. and if it's me, how I did what, exactly? O_o

My ~/.xinitrc is pretty simplistic. I'm on the Arch partitionon of my netbook right now, but it's mostly the same on my GRML/Debian partition.

#!/bin/sh

# dbus
test -z "$DBUS_SESSION_BUS_ADDRESS" &&
eval `dbus-launch --sh-syntax --exit-with-session`

# power management
#xfce4-power-manager &

# encryption
eval `gpg-agent --daemon` &&
trap 'killall gpg-agent' EXIT

# keyboard map
setxkbmap us &

# appearance
xrdb ~/.Xdefaults

# synaptics multitouch touchpad
syndaemon -t -k -i 2 -d &
synclient HorizTwoFingerScroll=1 &
synclient VertTwoFingerScroll=1 &
synclient TapButton1=1 &

# xsetroot
xsetroot -cursor_name left_ptr 

# wallpaper
feh --bg-tile /home/geezer/images/wallpapers/retroswirls4.jpg &
#feh --bg-scale /home/geezer/images/wallpapers/cracked_concrete08.png &
#feh --bg-tile /home/geezer/images/wallpapers/graynoise01.jpg &
#xsetroot - solid "#2c2c2c" &

# thunar file manager daemon
#thunar --daemon &

# music player daemon
exec mpd &

# screensaver
xscreensaver -no-splash &

# rxvt-unicode daemon
urxvtd -q -o -f 

#exec cwm
exec scrotwm
#exec dwm

The one on my GRML/Debian session doesn't have the feh, synclient and "exec <window manager>" commands. I have it point to a .sh script (scrotwmstart.sh, for example) at the end that launches them separately, since I (used to) have different wallpapers and touchpad preferences for different window managers. Another reason is because I use CDM on that partition, and it doesn't work quite right if I use the "exec <window manager>" command (for some unknown reason).

Last edited by gutterslob (2011-10-17 14:18:34)

el_koraco · 2011-10-17 14:09:22

Hya we go

#!/bin/sh
nitrogen --restore &
xsetroot -cursor_name  left_ptr
eval `dbus-launch --sh-syntax --exit-with-session`
sleep .2
exec ck-launch-session scrotwm

PackRat · 2011-10-17 15:34:19

el_koraco wrote:

Hya we go

#!/bin/sh
nitrogen --restore &
xsetroot -cursor_name  left_ptr
eval `dbus-launch --sh-syntax --exit-with-session`
sleep .2
exec ck-launch-session scrotwm

Interesting -

I loose auto-mounting if I have the dbus-launch line before the ck-launch; my last line has to be:

exec ck-launch-session dbus-launch --sh-syntax --exit-with-session scrotwm

Everything before that is pretty much what you have.

Edit: But your .xinitrc works flawlessly; my brain now hurts, I need whisky.

Last edited by PackRat (2011-10-17 15:40:41)

.not · 2011-10-17 18:08:25

Okay, I'm giving it up .. I am not able to design my ScrotWM like you in here did it. I was able to edit my terminal colors (.. bashrc is my friend, yeah!) but I was not able to create some color schemes, also the whole .Xinitrc-stuff does not get in my mind. I hate to ask for it, but would anybody mind giving me some hints or an entry point for my problems? I would be very grateful.

el_koraco · 2011-10-17 19:17:21

PackRat wrote:

Edit: But your .xinitrc works flawlessly; my brain now hurts, I need whisky.

Maybe it's the eval line.
@punktnot, you make your colorschemes in your .Xdefaults or .Xresources file, not in .bashrc. Check out this subforum, you'll find a thread dedicated to that point. Also, read this thread, you'll see both xinit models and scrotwm.desktop files if you're launching scrot via GDM.

Basically, you can start your X session with a display manager, like XDM, GDM, KDM, LXDM, LightDM, Slim, or with xinit. If you're starting it with xinit, you need to define the values for it, that's what the .xinitrc file is for. It only sounds ominous, all the DMs are controlled via text files as well, usually a bunch of them, and in Debian, a bunch of WMs have display manager integration in the postinstall scripts. Why don't you cp my .xinitrc, stop GDM from a tty with

sudo service GDM stop

launch startx and take it from there.

Last edited by el_koraco (2011-10-17 19:17:45)

gutterslob · 2011-10-17 19:29:17

@.not

I was able to edit my terminal colors (.. bashrc is my friend, yeah!) but I was not able to create some color schemes

This sentence kinda contradicts itself. You say you were able to edit your colors but couldn't get a colorscheme? O_o? ... I'm not sure I can answer until you elaborate on this a bit more.

I hate to ask for it, but would anybody mind giving me some hints or an entry point for my problems? I would be very grateful.

We'd be glad to help, but you're a bit vague here. It would be nice if you included the distro you're using, what you use to start your X-sessions and the version of Scrotwm you have installed.

Anyways, I'll answer your query with the assumption that you're on Crunchbang Statler, using the included GDM as your display manager, and have installed ScrotWM from the Debian repos... but... I must disclaim that I'm not the most eloquent chap and am more often than not completely useless at explaining stuff. Please bear with me.

Firstly, what I'm stating here is basically a repeat of what's been discussed in this thread already. I'm assuming you missed the details for one reason or another.

If you're startinf ScrotWM from a tty via startx, refer to el_koraco's post above this one.
If you're starting your ScrotWM session via GDM, you technically do not need a ~/.xinitrc, since GDM looks for the session startup scripts in /usr/share/xsessions. In there, you should have a Scrotwm.desktop file (it might just be labeled Scrotwm). There is a way to tell GDM to look for you ~/.xinitrc file instead, but I can't recall how that's done since I've not used GDM in a long while. Anyways, if you want to start services, daemons, wallpapers... etc for ScrotWM without xinitrc, you can create a simple script and place it in your $PATH (for Crunchbang, /home/<yourusername>/bin) is usually a good place). You then fill it with the stuff you want started and name it whatever you want, eg: scrotwmstart.sh

As far as I know, GDM starts dbus automatically, so I don't think you need the dbus related command Packrat and el_koraco were talking about a couple of posts above yours. Here's an example I conjured up based on what I assume most Crunchbangers would need started. You'll need to edit it to fit yours, obviously, since I'm not sure if you need synclient commands for your touchpad or if you use mpd as your music player daemon. I do recommend you install urxvt (rxvt-unicode in Debian repos) and use it as your primary terminal emulator in ScrotWM, though. The lines with feh are for displaying wallpaper (requires you to install feh... available in repos), but using nitrogen works as well (refer to el-koraco's xinitrc above). You might also want to change your keyboard map (setxkbmap) if you're relying on a non-US keyboard layout. If it's a Crunchbang install, you can double-check the contents against that of your ~/.config/openbox/autostart.sh to see if there's anything missing.

bin/scrotwmstart.sh

#!/bin/bash

setxkbmap us &
xfce4-power-manager &
feh --bg-scale /home/<yourusername>/images/wallpapers/wallpaper.png &
#feh --bg-tile /home/<yourusername>/images/wallpapers/wallpaper.jpg &
#xsetroot -solid "#2c2c2c" &
thunar --daemon &
synclient TapButton1=1 &
synclient VertEdgeScroll=1 &
synclient VertTwoFingerScroll=1 &
synclient HorizTwoFingerScroll=1 &
mpd &
xscreensaver -no-splash &
urxvtd -q -o -f &
sleep .2
scrotwm

You need to make this script executable. Either use a terminal and cd into bin and do "chmod +x scrotwmstart.sh" or right click on it in your GUI file manager, go to "Properties", and then find a tab named "Permissions" and check the box that says something like "Allow to run as program".

Then you go to your /usr/share/xsessions/Scrotwm.desktop and edit it (as root), so that the "Exec" line points to the scrotwmstart.sh script. Something like this should suffice. (remember to change the path in "Exec" according to your username and location you put the script in.

[Desktop Entry]
Name=Scrotwm
Encoding=UTF-8
Comment=This session runs the scrotwm window manager
Exec=/home/<yourusername>/bin/scrotwmstart.sh
TryExec=scrotwm
Type=XSession

That should get you to start ScrotWM via GDM with all your desired daemons and "services" running. If you've entered all paths and variables correctly, you should get everything you need started.

I've also included an old ~/.scrotwm.conf I have from an older version (the same version you're using if you installed from Debian repos), which you can use for reference: http://crunchbanglinux.org/pastebin/1254
Note: If you're really unsure, just use this one. It's sets the Mod/Meta key to Mod4 (windows logo key) and is configured to start the urxvt client as your preferred terminal emulator (assuming you installed urxvt). I've also included quiks to float the Thunar and Mplayer windows. Just add bindings and quirks for to that if you need to.

Lastly, included a simple ~/.Xdefaults setup which you can cross-reference with, just in case.
http://crunchbanglinux.org/pastebin/1255

I hope this helps. Tried my best to explain as simplistically as possible.

P.S
1. I apologize for any typos. It's a long post and I'm sleepy.
2. If all I've stated is redundant to you, let me know so that I can remove this long, lethargic post and save face.

Last edited by gutterslob (2011-10-17 19:31:44)

gutterslob · 2011-10-17 19:34:00

PackRat wrote:

Edit: But your .xinitrc works flawlessly; my brain now hurts, I need whisky.

That's a bad excuse man!! ... Whisky/Whiskey should be consumed at all times (except when driving or handling children), not just when your brain aches. tongue

.not · 2011-10-17 19:49:55

Thank you guys for your help, I really appreciate that you made efforts to explain it to me very clear and simple. (Although I know how to make a script executable .. just kidding. *grin*) I'm sorry that - in my upcoming panic and frustration - I forgot to include some important informations. I'm using Debian 6.0.2 (x86), I don't have any login manager installed and start my scrotwm (V0.9.20 - from the official stable repositories.) directly from tty via startx.

So I guess, my file would be xinitrc (.. I found an explanation about it in the archwiki.) - which helps me a lot because my brain starts understanding some things that were very unclear at the beginning. I will work through this thread, the wiki and will find out as much as I can to solve my problems. I hope not, but if there would be anything I don't understand I'll ask here. Thanks again, if there will be a #!-meeting I owe you guys a beer/whisky/coffee.

PS: Sorry for grammatical mistakes or typos .. as you said, it's late.

el_koraco · 2011-10-17 19:54:02

.not wrote:

So I guess, my file would be xinitrc (.. I found an explanation about it in the archwiki.) - which helps me a lot because my brain starts understanding some things that were very unclear at the beginning.

Then you literally need to cp my xinitrc from a few posts above. I'm also on Squeeze and everything works with that setup. You can also add the synclient command that slobbers posted (nice one, slob, I totally forgot about adding synaptics to my setup, since I hate hate hate touchpads), if you use the touchpad of course.

Would you like my .Xdefaults file as well, for some colors?

.not · 2011-10-17 19:57:49

Would be nice to see it, even if I really do not want to copy it because I want to understand things instead of copypasting 'em. smile

el_koraco · 2011-10-17 20:06:12

I'll make you some comments, and check out the thread

#.Xdefaults for punktnot's understanding

#Making some applications not have ugly fonts, because they're not built to enable system cairo, which is 
#another one of Debian's antique settings. Can be changed in accordance with your .fonts.conf

Xft.autohint: 0
Xft.antialias: 1
Xft.hinting: true
Xft.hintstyle: hintslight
Xft*dpi: 96
Xft.rgba: rgb
Xft.lcdfilter: lcddefault

Xcursor.theme:    Vanilla-DMZ-AA  #self-explanatory

!color scheme: #stuff prefixed with a ! is not read, like the stuff prefixed with #
#I'm also not defining urxvt specifically, since this way it can be read by xterm as well

*background: #151515
*foreground: #6BC3C5

*colorUL: #4E4FFF

!black
*color0:  #151515
*color8:  #777070
!red
*color1:               #7221FB
*color9:               #923EFF

!green
*color2:               #34D4CC
*color10:              #12B2B8

!yellow
*color3:               #54E72D
*color11:              #6BBF59

!blue 
*color4:               #3472D9
*color12:              #3875A2

!magenta
*color5:               #4E4FFF
*color13:              #774Ad8

!cyan
*color6:               #0EA5C8
*color14:              #058FAF

!white
*color7:  #6bc3c5
*color15: #7fdcc4

#You get the long values of fonts, such as here, by running xfontsel
#The xft values are like the ones in your lxappearance, but the size is calculated differently
!urxvt fonts: 
!URxvt*font: -*-tamsyn-medium-*-*-*-*-*-*-*-*-*-*-*
URxvt*font: xft:terminus:pixelsize=8
#URxvt*font: xft:snap:pixelsize=8
!URxvt*boldFont: -*-tamsyn-bold-*-*-*-*-*-*-*-*-*-*-*
URxvt*boldFont: xft:terminus:bold:pixelsize=8
#URxvt*boldFont: xft:snap:bold:pixelsize=8

#I pretty much just cp-d these ones from the .Xdef thread, check for link
!urxvt extensions:

URxvt.perl-ext-common:  default,matcher,tabbedex

!enabling clickable links:
URxvt.urlLauncher:      /usr/bin/firefox
URxvt.matcher.button:   1 

!urxvt scrolling options and cursor style:

URxvt*saveLines: 12000
URxvt*scrollstyle:plain
URxvt*scrollBar: false
URxvt*cursorBlink: false
URxvt*cursorUnderline: false

Last edited by el_koraco (2011-10-17 20:06:35)

h8uthemost · 2011-10-21 07:36:04

What exactly would I put in my config file to bind volume to Mod+Up/Down keys? According to this page you would use this to bind volume:

program[VolumeUp] = amixer sset Master,0 1+
bind[VolumeUp]    = XF86AudioRaiseVolume

But I don't exactly understand this as usually after bind[program] = you would put your keybind. And I tried Mod+Up after the = sign but the volume isn't raising.

el_koraco · 2011-10-21 10:13:07

h8uthemost wrote:

program[VolumeUp] = amixer sset Master,0 1+
bind[VolumeUp]    = XF86AudioRaiseVolume
But I don't exactly understand this as usually after bind[program] = you would put your keybind. And I tried Mod+Up after the = sign but the volume isn't raising.

program[program name] determines how scrotum identifies the program. Say program[bla] = chromium-browser would make scrot identify chromium as "bla". To identify your media keys, look at your keyboard and see where the symbols in blue are, with stuff for prevous, next and so on. Then open a terminal and work with xev, follow this hint - here

Check out how I did my audio controls, this is with mpd and some other programs:

program[firefox]        = firefox
bind[firefox]           = MOD+w
program[thunar]         = thunar
bind[thunar]            = MOD+f
program[lowriter]       = lowriter
bind[lowriter]          = MOD+o
program[synaptic]       = gksu -w synaptic
bind[synaptic]          = MOD+s
program[VolumeUp] = amixer sset Master,0 1+
bind[VolumeUp]    = XF86AudioRaiseVolume
program[VolumeDown] = amixer sset Master,0 3-
bind[VolumeDown]    = XF86AudioLowerVolume
program[Play]    = mpc play
bind[Play]    = XF86AudioPlay
program[Next] = mpc next
bind[Next]  = XF86AudioNext
program[Prev] = mpc prev
bind[Prev]  = XF86AudioPrev
program[Stop] = mpc stop
bind[Stop]  = XF86AudioStop

Last edited by el_koraco (2011-10-21 10:14:29)

CrunchBang Linux

SEARCH

#76 2011-10-07 19:05:05

Re: Getting Started with Scrotwm?

#77 2011-10-07 19:07:28

Re: Getting Started with Scrotwm?

#78 2011-10-09 16:37:06

Re: Getting Started with Scrotwm?

#79 2011-10-09 16:50:19

Re: Getting Started with Scrotwm?

#80 2011-10-10 19:30:16

Re: Getting Started with Scrotwm?

#81 2011-10-12 22:21:51

Re: Getting Started with Scrotwm?

#82 2011-10-13 01:45:48

Re: Getting Started with Scrotwm?

#83 2011-10-13 02:02:54

Re: Getting Started with Scrotwm?

#84 2011-10-13 19:02:20

Re: Getting Started with Scrotwm?

#85 2011-10-13 23:01:57

Re: Getting Started with Scrotwm?

#86 2011-10-13 23:14:10

Re: Getting Started with Scrotwm?

#87 2011-10-17 13:23:17

Re: Getting Started with Scrotwm?

#88 2011-10-17 14:02:34

Re: Getting Started with Scrotwm?

#89 2011-10-17 14:09:22

Re: Getting Started with Scrotwm?

#90 2011-10-17 15:34:19

Re: Getting Started with Scrotwm?

#91 2011-10-17 18:08:25

Re: Getting Started with Scrotwm?

#92 2011-10-17 19:17:21

Re: Getting Started with Scrotwm?

#93 2011-10-17 19:29:17

Re: Getting Started with Scrotwm?

#94 2011-10-17 19:34:00

Re: Getting Started with Scrotwm?

#95 2011-10-17 19:49:55

Re: Getting Started with Scrotwm?

#96 2011-10-17 19:54:02

Re: Getting Started with Scrotwm?

#97 2011-10-17 19:57:49

Re: Getting Started with Scrotwm?

#98 2011-10-17 20:06:12

Re: Getting Started with Scrotwm?

#99 2011-10-21 07:36:04

Re: Getting Started with Scrotwm?

#100 2011-10-21 10:13:07

Re: Getting Started with Scrotwm?

Board footer