https://bugs.kde.org/show_bug.cgi?id=403956
Valdo <gnu4e...@netc.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gnu4e...@netc.eu
--- Comment #3 from Valdo <gnu4e...@netc.eu> ---
To complete jg's request, I also have "complaints" to share regarding Kate's
default save directory:
1. Why not offer a "Default Save Directory" option users could customize to
their will? I totally share jg's opinion: it can be a real pain having to start
from the home directory (location decided by s.o. else than the user), over and
over for each new file to save. For e.g. a major part of my text files are
located on a dedicated disk partition. I would like to be offered (for each new
file) to save in a given directory on that partition.
2. Why not offer a "Remember Last Save Location" option, that would override
the "Default Save Directory" option I suggested at section 1., that users could
check (radio button)? Some people prefer to have this kind of default save
behaviour.
3. Another (additional) save option could be jg's suggestion: "Remember Last
Opened File Directory", that would override options I suggested at sections 1.
and 2., that users could check (radio button)?
4. I'm adding another wish, a bit different in nature, but still linked to new
file "saving": please _bypass_ the "File Close Confirmation" dialog box, when
a) file's _current_ content is empty (whether or not users had added some text
at some point in the past) _and_ b) file has never been saved to disk.
Explanation: I often use Kate as a _temporary_ text editing tool, to
copy/paste/rearrange some text from application A to application B. The new
file I created with Kate is not meant to be saved to disk. So once emptied by
me, I would like to close this temporary file without having to _confirm_ that
it shouldn't be saved to disk. This is for e.g. the default behaviour of
Notepad++ (very practical).
Please tell me if I should open a new bug (features request) for my
suggestions.
- If not needed, can we change Kate's version of this bug (403956) to version
19.12.3 (since my suggestions are not implemented in version 19.12.3 - I can't
tell for sure about jg's initial suggestion)? And possibly rephrase bug's title
to a more generic features request?
- If recommended to open a new bug (features request), can KDE team do
something about this bug (403956)? I mean, take a position regarding jg's
suggestion, to avoid keeping this bug open for too long (as much as possible).
Thank you very much for reading, I remain available for any subsequent steps
I'd have to take (just tell me).
--
You are receiving this mail because:
You are watching all bug changes.
