Have a look at http://awesome.naquadah.org/wiki/Autostart
>From the content of that wiki page I ended up having an autostart
module [1] and then in my rc.lua file I just invoke the applications
like this
autostart.run_once({
{command = "volwheel"},
{command = "chromium
--app-id=\"hbdpomandigafcibbmofojjchbcdagbl\""}, -- TweetDeck
{name = "dropbox", command = "dropboxd"},
{command = "parcellite"},
{command = "keepassx /home/antonio/Dropbox/kp.kdb -min -lock"},
{command = "trayfreq"},
{command = "urxvtd -q -o -f"},
{command = "wmname LG3D"},
{command = "setxkbmap es"},
{command = "emacs --daemon"},
{command = "ruby /home/antonio/.bin/dual-screen.rb"},
{command = 'git dude /home/antonio/.git-dude'},
{command = 'udiskie'},
{command = 'mpdscribble'},
})
[1] https://github.com/antonio/dotfiles/blob/master/awesome/autostart.lua
Cheers
On Thu, Dec 1, 2011 at 8:20 AM, Rémi Vanicat <[email protected]> wrote:
> Magnus Therning <[email protected]> writes:
>
>> There are a few things I currently start using os.execute from my
>> awesome config file. Is there some standard way of preventing a
>> second instance of each of those things is started when I restart
>> awesome (Mod4+Shift+r)?
>
> I've moved those to my ~/.xsessionrc, but before that I used debian's
> start-stop-daemon to only call them if they were not already running.
>
> You could also look at the run_or_raise function you can found there:
> http://awesome.naquadah.org/wiki/Run_or_raise
>
> --
> Rémi Vanicat
>
>
> --
> To unsubscribe, send mail to [email protected].
>
--
To unsubscribe, send mail to [email protected].
