On Thursday 06 November 2014 22:01:13 Jeremy Whiting wrote:
Hey all,
In kdelibs4 times one used to be able to put any script into
~/.kde/Autostart/ make it executable and when startkde ran it would
launch those scripts. In kf5/plasma next time ~/.config/autostart
should be able to do
Ok, from a bit more testing yesterday evening it seems all scripts put
into ~/.config/plasma-workspace/env/ work fine for startup, and in
~/.config/plasma-workspace/shutdown/ for shutdown. These are correctly
shown in the kcm and are sourced at startup and shutdown. With that
solution there's
On Freitag, 7. November 2014 21:28:15 CEST, Jeremy Whiting wrote:
The way I see it this should be documented well, and the kcm
needs to be adjusted to not show scripts from ~/.config/autostart
since kinit wont be starting those.
Thomas,
Yep, I see what $XDG_CONFIG_DIRS/autostart/*.desktop is for, my only
question is that if there are non .desktop files in there too, we are
showing them in the autostart kcm, yet we aren't autostarting them :)
I really need to get the kcm patch ready for review, not showing those
scripts
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121058/
---
Review request for kdelibs, Plasma and Luca Beltrame.
Repository:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121058/#review70018
---
kcms/autostart/autostart.cpp
Hi, we've added a new CHANGELOG: keyword to
https://techbase.kde.org/Policies/Commit_Policy#Special_keywords_in_GIT_and_SVN_log_messages
So that you highlight that that comit should end up in the release notes.
We still need something that parses it but step by step :)
Cheers,
Albert
El Divendres, 7 de novembre de 2014, a les 16:35:21, Thiago Macieira va
escriure:
On Saturday 08 November 2014 00:58:49 Albert Astals Cid wrote:
Hi, we've added a new CHANGELOG: keyword to
https://techbase.kde.org/Policies/Commit_Policy#Special_keywords_in_GIT_an
d_ SVN_log_messages
