Martin,
After further testing yesterday evening it seems placing scripts
(executable files) in ~/.config/plasma-workspace/env/ works fine.
These also correctly appear in the autostart kcm. The only confusion
left that I see is that scripts placed into ~/.config/autostart appear
in the kcm, but we
On Fri, Nov 7, 2014 at 8:48 AM, Jeremy Whiting 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 sh
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 scri
On Wed, Aug 13, 2014 at 11:01 PM, Martin Yrjölä
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.
A
>
>
> 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/.
As I'm unfamiliar with the process, I'm asking you if I should add
kde-frameworks-de...@kde.org to this thread? Or should the discussion be
h
On Wednesday 13 August 2014 19:34:16 Luca Beltrame wrote:
> - Re-enable autostart for everything but desktop files in ksmserver;
> - Add support for scripts in kinit (does it even make sense? - from what
> Sune said, probably not);
> - Drop autostart scripts, tell users to make .desktop files
>
>
Hello,
commit f913e251fe66e22606c380a8cc0ddc8c69e3c07d in plasma-workspace removed
autostart support in ksmserver because it caused .desktop files to be
autostarted twice (one for kinit, and one for ksmserver).
I just noticed that it causes a regression in behavior from 4.x times, as
user scri
