kui
kui copied to clipboard
kubernetes-sigs
Save Feature or Folder for Markdown Files in Windows
I want to save my edited notebook. It looks like there used to be a "Save" button in the file menu- but there is not any more.
I've tried using File -> Open to load a markdown file, but nothing happens.
It would be great if there was a folder I could save my markdown files in and they would be loaded into the system. (Like another option in the "Guidebooks" menu.
kui-shell says we should be able to save markdown files in a notebooks folder- but I can not find any such folder in the pre-built windows program.
Could this folder be left exposed after an electron build is created?
If so, that would allow people to easily add notebooks without having to build the entire thing from source.
I agree with Josh. What will prevent me from using KUI is that it currently doesn't save my workspace and I have to start from scratch the next time I run the program. I'm also on Windows.
I thought I was too stupid to use the tool, but I'm glad I'm not the only one going through this.
It's impossible to save anything it seems. Even though in this video the guy saves it easily (without telling/showing now).
So sad, because it's cool tool, but unusable if one cannot create their own notebooks.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale