On Fri, Nov 7, 2014 at 8:48 AM, Jeremy Whiting <jpwhit...@kde.org> wrote: > IMO we have two problems here. > > 1. the autostart kcm is showing scripts from ~/.config/autostart which > kinit doesn't start. since ~/.config/autostart is an xdg path that is > only meant to start .desktop files we probably shouldn't be showing > scripts in the kcm that we don't start. > 2. Users with scripts in ~/.kde/Autostart will want a place to > drop/move their scripts when moving to plasma-next. One solution to > this would be to loudly document that each script needs a .desktop > file created to actually launch it (easily done in the autostart kcm). > Another probably better solution would be to define a place where > ksmserver would look and execute or source scripts such as > ~/.config/ksmserver-autostart or something. > > I'll work up a patch for 1 tomorrow, as that shouldn't be hard to not > show those files. > > Thoughts? > Jeremy >
Hi Jeremy! There's a ticket about this were I'm assigned https://bugs.kde.org/show_bug.cgi?id=338242 I haven't made big strides on this issue as I have been terribly busy. It would be wonderful if you can come up with a patch to solve the issue. The proposed solutions in the ticket is to move all autostart functionality from kinit to ksmserver and after that add support for scripts. However I also like your solution of introducing a ~/.config/ksmserver-autostart directory that is managed by the autostart kcm and then the scripts are launched at the appropriate time in plasma-workspace/ksmserver/startup.cpp. Do you want to step up and get the ticket assigned to you Jeremy? Best regards, Martin Yrjölä _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
