Probably worth sharing on the user ML as well for future reference, although R14.1.0 won't be out soon...
-------- Forwarded Message -------- Subject: R14.1.x new Kate session panel Date: Sat, 16 Sep 2017 00:29:11 +0900 From: Michele Calgaro michele.calgaro@yahoo.it To: TDE devel trinity-devel@lists.pearsoncomputing.net
Dear all, I have finally come around to push the new Kate session panel code to R14.1.x trunk. This adds a session panel to Kate to easy and enhance working with sessions. I have been using it for a couple of years, while slowly developing it. In future I envision more functionality added to it, although finding the time to develop that could be a serious challenge. Just three things to look out for:
1) the format of Kate's session files has changed, the new code will import all your session files and save them with some differences. So if you are just planning to test the new code to see how it works and then revert to an older version, it is recommended that you make a backup of your session files before you start and you restore them at the end of the process
2) with the new code, the "default" session is no longer hardcoded. You can rename it, delete it or do whatever you want.
3) a "read-only session" is a session where you can do whatever editing you want (and all the editing will be saved!). But when you close Kate or switch to another session, the session file will not be modified and the next time the session will open with the same GUI-state (same open files, same panel positions and so on...).
If you run into any problem, just report to the ML or preferably open a bug report in bugszilla.
Cheers Michele
Michele Calgaro wrote:
Probably worth sharing on the user ML as well for future reference, although R14.1.0 won't be out soon...
Can't we have an experimental or testing repo somewhere at least for debian?
I have build almost all the packages and have set up a local repository. As I am using it on daily bases, I can confirm that I have no problems so far at least on debian stretch.
The repo is ~3G for all debian flavors Debian$ ls buster jessie sid stretch Debian$ du -hs . 2.5G .
Would it be too much effort to maintain?
On 2017/09/16 07:16 PM, deloptes wrote:
Michele Calgaro wrote:
Probably worth sharing on the user ML as well for future reference, although R14.1.0 won't be out soon...
Can't we have an experimental or testing repo somewhere at least for debian?
I have build almost all the packages and have set up a local repository. As I am using it on daily bases, I can confirm that I have no problems so far at least on debian stretch.
The repo is ~3G for all debian flavors Debian$ ls buster jessie sid stretch Debian$ du -hs . 2.5G .
Would it be too much effort to maintain?
There are the nightly builds available, although access may be restricted and you may have to ask Tim to enable your account. I used that for reference initially, but over time I used that less and less and instead use my local repo for all. If I really want to test something out and I am unsure about it, I use a VM. Also there is the preliminary builds repo maintain by Slavek, but it builds R14.0.x branch instead of R14.1.x. Would be good to have a preliminary repo also for R14.1.x to easy testing. Slavek, do you think you could set up something like that as well? And do you have the server space?
Cheers Michele
Michele Calgaro wrote:
There are the nightly builds available, although access may be restricted and you may have to ask Tim to enable your account. I used that for reference initially, but over time I used that less and less and instead
It would have not worked for me anyway as some of the tdepim changes are still not in 14.1
use my local repo for all. If I really want to test something out and I am unsure about it, I use a VM. Also there is the preliminary builds repo maintain by Slavek, but it builds R14.0.x branch instead of R14.1.x. Would be good to have a preliminary repo also for R14.1.x to easy testing. Slavek, do you think you could set up something like that as well? And do you have the server space?
I was thinking of setting up repo on my public server account which is hosted in Germany. In general it is not a problem, only I don't know how to set up and build such public repo, but there is enough documentation AFAIK.
Anyway decisions might be taken individually as well.
Thank you for the extention to kate.
regards
-
deloptes -
Michele Calgaro