Autostart scripts (ksmserver problem)

[Jeremy Whiting]

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

On Tue, Aug 19, 2014 at 1:59 AM, Martin Yrjölä <martin.yrjola at gmail.com> wrote:
>
>
>
> On Wed, Aug 13, 2014 at 11:01 PM, Martin Yrjölä <martin.yrjola at gmail.com>
> wrote:
>>>
>>>
>>> hmm, so it seems the best option is to Add support for scripts in kinit?
>>>
>>
>> I submitted a patch to kinit in https://git.reviewboard.kde.org/r/119773/.
>>
> David Faure commented that this issue should be solved in the workspace. As
> the xdg autostart standard only mentions desktop-files, should we make the
> "Add script"-button in the  Autostart KCM generate a desktop-file for the
> given script in the autostart-folder? Then we would only need to make
> changes to the Autostart KCM. The downside is that then we don't support
> console users that used to symlink their scripts to the autostart directory.
> I'm willing to provide a patch if we can settle on a solution. There's also
> a bug report for this: https://bugs.kde.org/show_bug.cgi?id=338242
>
> -Martin Yrjölä
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>