SUMMARY I am the software developer and I need every day to create a new file in the development tree. In KDE4 I have just selected any existing file in the required directory, then I just opened a new file with the required name. And all is done in 2 steps. Now it becomes much more complicated. I have to 1. selected any existing file in the required directory 2. click "Open" 3. click "Cancel" 4. click "New" 5. click "Save" and enter the required name So 2.5 times more steps. Besides I can not avoid the creation of the backup copy since I have to save the file twice. STEPS TO REPRODUCE 1. Click "Open" 2. Fill the new name and click the button "Open" OBSERVED RESULT There is an alert "Can not open file" - "file not found" EXPECTED RESULT The window is closed and the new name is appeared in the file list. So when I press the button "save" the file is created. SOFTWARE/OS VERSIONS Operating System: Slackware-current KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.20 OS Type: 64-bit Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION If someone insists that the new behaviour is more user-friendly, please create a special setting that will allow the old behaviour.
I am sorry, but that is really intentional. Most open file dialogs behave that way. You want to avoid that people start to open new files, just because they mistype. You can create a new file even inside the dialog by right click and say "Create New -> ..." > If someone insists that the new behaviour is more user-friendly, please create a special setting that will allow the old behaviour. I insist on that, but I don't want to have an option for such a thing, that is really the normal behavior for "open file", you want to "open an existing" file.
> You can create a new file even inside the dialog by right click and say > "Create New -> ..." The problem with this method is I can not use an existing file as a pattern. For example, I have directory with files *_spec.js.coffee and I need to create a new file. Then I used to just in Open dialogue select any existing file, change the first type to the required value, for example, to "form_spec.js.coffee", click "Open" and vu'a la. Now it is impossible to do so simple. I have always to type the whole name or use the procedure described earlier. > > > If someone insists that the new behaviour is more user-friendly, please create a special setting that will allow the old behaviour. > > I insist on that, but I don't want to have an option for such a thing, that > is really the normal behavior for "open file", you want to "open an > existing" file. Please, understand that new behaviour really slows down my development process. And, I am sure, not only mine. I am sure that adding a check-box "Allow new file" in the Open dialogue will require less than half an hour for your to implement. ;-) But it will save a lot of time for me and for other programmers.
This indeed is by design and will not be changed. If you want a file X go to the built-in Terminal and type kate X.
I need the same behaviour as vim has in any case. The ability to open a new file. Make the setting to disallow it (as you implemented it now) for fools that want to see the error message opening inexistent file.
With the upcoming release creating a new file is more simple: Right click the directory where you want to create a new file and enter the name. This is available only for projects. Note that ahy folder can be loaded as a project by just doing "kate ." in the directory in the upcoming release. If you still don't have or want a project, the best way to create a new file from gui is by using the file system browser plugin. Enabling broken behavior to satisfy a use case is not an option. And yes, it *is* broken behavior and will not be supported even optionally.
Vim behavior is "vi file". This is already possible in kate. And you don't need to do it from outside, just use the Konsole plugin.
(In reply to Waqar Ahmed from comment #5) > Enabling broken behavior to satisfy a use case is not an option. And yes, it > *is* broken behavior and will not be supported even optionally. Why do you want at least me to say bad words about you every time a new file is required in a project? Tell me at least one reasonable argument, you've broken the behaviour? Do you think, there is at leas one person, that seeing the empty screen will not understand he/she had used the wrong name? WHAT IS THE REASON to break the behaviour?!!!!
The reason is simple, File->Open.. is meant to open existing files, not new files. I gave you three ways to create a new file which are more straightforward than what you suggested. I am unsure why you are so angry even though your question and wish is already being satisfied in multiple ways. If you think there is a better way, take your keyboard, write some code and create a merge request showing us the better way. But poor behavior and being snobby will make people ignore you regardless of how valid your wish is. Oh and, You can say all the bad words that you want if it makes you happier.
(In reply to Waqar Ahmed from comment #8) > The reason is simple, File->Open.. is meant to open existing files, not new > files. NO, for decades it meant to open any file, existing or new. > I gave you three ways to create a new file which are more straightforward > than what you suggested. All the ways require much more steps -> time. That makes them unacceptable. And right click on the directory has no option to add a file. See the attachment. > I am unsure why you are so angry even though your > question and wish is already being satisfied in multiple ways. > > If you think there is a better way, take your keyboard, write some code and > create a merge request showing us the better way. But poor behavior and > being snobby will make people ignore you regardless of how valid your wish > is. I'm living in the total Zeitnot, But if you give me the link to the code where File->Open is implemented, I'd try to fix the bug to save my time in future. > Oh and, You can say all the bad words that you want if it makes you happier. No, you've made me unhappy. While in 10-15 minutes you can make me happy again. I do not think you'll need more time to allow open a new file as well, as it was in the previous versions of Kate.
Created attachment 137399 [details] no create item
We use the proper: QFileDialog::getOpenFileUrls https://doc.qt.io/qt-5/qfiledialog.html#getOpenFileUrls That has not even an option for the behavior you wish. And there is no proper other function that gives you a native file dialog of the platform in Qt. Therefore, no, this is not a few minutes fix. If you want to have a different behavior, perhaps you need to raise this issue in Qt, they can "improve" that method in any way, Kate/KWrite/... just call that and then open all stuff returned by it. In any case, our current way to do stuff is as intended, we don't even try to tweak the behavior QFileDialog::getOpenFileUrls gives you, same for the save case, there we use QFileDialog::getSaveFileUrl.
> All the ways require much more steps Please try out before assuming it takes more steps. The konsole way for example takes less steps. > no create item With next release. 21.04. You can grab an appimage if it's not available for your distribution. However, the option is already available in the file system browser plugin.
Created attachment 137441 [details] What can be easiery to create a new file in the given place with the given name?
(In reply to Christoph Cullmann from comment #11) > If you want to have a different behavior, perhaps you need to raise this > issue in Qt, they can "improve" that method in any way, Kate/KWrite/... just > call that and then open all stuff returned by it. I am sure this is to be solved without QT changes. I need the same behaviour, as in the video. And you forget to send me the link to the corresponding code in Kate… P.S. Sorry for the delayed answer.
Hi, The workflow in the video does not seem very intuitive in my opinion... But there is one thing that I do think we could take out of this. I guess that what you want is to have an easy way to add a new file in the current project/directory? The default directory for saving the new file could be the directory of the last visited existing file, or maybe better, the directory of the file that was active when "New" was clicked?
(In reply to Kåre Särs from comment #15) > Hi, > > The workflow in the video does not seem very intuitive in my opinion... Probably, it is not too intuitive. But it is the way I have intuitively found 20 years ago and been using till now. > But there is one thing that I do think we could take out of this. I guess > that what you want is to have an easy way to add a new file in the current > project/directory? > > The default directory for saving the new file could be the directory of the > last visited existing file, or maybe better, the directory of the file that > was active when "New" was clicked? (y) Yes, it would be the solution, provided I can supply the name BERORE the file is first time saved. I do not like to create unneeded *~ files.
(In reply to Dmitri Koulikoff from comment #14) > (In reply to Christoph Cullmann from comment #11) > > > If you want to have a different behavior, perhaps you need to raise this > > issue in Qt, they can "improve" that method in any way, Kate/KWrite/... just > > call that and then open all stuff returned by it. > > I am sure this is to be solved without QT changes. > > I need the same behaviour, as in the video. > > And you forget to send me the link to the corresponding code in Kate… https://invent.kde.org/utilities/kate/-/blob/master/kate/kateviewmanager.cpp#L223 > > P.S. Sorry for the delayed answer.
A good idea is to block creating a backup file for empty content. And by the way your apporach requires one extra click ;-)
> > The default directory for saving the new file could be the directory of the > > last visited existing file, or maybe better, the directory of the file that > > was active when "New" was clicked? > > (y) > Yes, it would be the solution, provided I can supply the name BERORE the > file is first time saved. I do not like to create unneeded *~ files. It is not implemented. When I try to save a new file the default directory is NOT the previously used file was in. But better and much more simply would be to allow to open an inexisting file… ;-)
Closing again. As suggested earlier, opening a non existing file is not possible and we don't want to make it possible. Please use one of the many ways suggested above for creating a new file.
(In reply to Waqar Ahmed from comment #20) > Closing again. > > As suggested earlier, opening a non existing file is not possible and we > don't want to make it possible. Please use one of the many ways suggested > above for creating a new file. Please, send me a video like https://bugs.kde.org/attachment.cgi?id=137441 so that I can create a new file in a given directory, easier that it is shown there. Or at least not requiring to traverse the whole tree like in a new attachment.
Created attachment 145544 [details] trouble to add a new file to a directory
If you want this particular behavior, fix it in Qt like already suggested. I already gave you 3 ways to create a file. One of the ways requires 0 clicks. Reread the thread. I am sorry that we can't satisfy your wish. Please do not reopen this again.
(In reply to Waqar Ahmed from comment #23) > If you want this particular behavior, fix it in Qt like already suggested. > > I already gave you 3 ways to create a file. One of the ways requires 0 > clicks. Reread the thread. I have re-read the thread once more. I have found the following: 1. "Right click the directory where you want to create a new file and enter the name." -> does not work as I have no project 2. "system browser plugin." -> when I open this plugin, it shows not the folder with the current file rather my home directory, so I have to spend my time on the traversing it. Additionally, I can not use an existing filename as a pattern for a new file. 3. This way I can not find in your answers. Probably, it is to create a new file and then save it. But in this case I also have to spend my time on the traversing the directories. You have mentioned that if I try to save a new file the default directory is the one the last used file was in, but it is not true. Sorry but I *really* need a way to very quick add a new file to my projects, so I have to reopen the case. Please, provide the way. I understand that you and others may not like an idea of opening an inexistent file that was used in kde4. OK, then give a working alternative. For example, add a function "Open/Create new", that will open the directory of the current file and allow to select and then modify a filename.
File browser has a button on the toolbar to sync to the current document i.e., it will take you to the folder where that doc is and you can create a file there using context menu. Option 3 is using terminal. Type kate blahblah and it will create blahblah in current directory of the terminal. The terminal can sync to current opened directory so you can use an existing doc to jump to the location where you want to create the file. Or give full path when creating a file.
Sorry, there are multiple workaround for this issue that only create a bit more work for you. We don't introduce a new file action just for this use case. I for years just "save as" and remove the content. Please refrain from opening this again, it was clearly stated we will not add a way to do this for you. You might want to report a bug to the file dialog in Qt or frameworks integration that you want for the open existing files only case a nicer behavior for new file creation. But we will not do a fix on the editor level. If we start to add an action for every corner case wish somebody has, the file menu will be even more overfull as now, even now there are complaints it is too full, which is correct.
(In reply to Waqar Ahmed from comment #25) > File browser has a button on the toolbar to sync to the current document > i.e., it will take you to the folder where that doc is and you can create a > file there using context menu. Anyway, this way does not allow to use an existing filename as a pattern. > Option 3 is using terminal. Type kate blahblah and it will create blahblah > in current directory of the terminal. The terminal can sync to current > opened directory so you can use an existing doc to jump to the location > where you want to create the file. Or give full path when creating a file. This option too.
(In reply to Christoph Cullmann from comment #26) > Sorry, there are multiple workaround for this issue that only create a bit > more work for you. > > We don't introduce a new file action just for this use case. OK, should I create a new bug, that "save as" for a new file does not use the directory of the last used file as a default one?
> OK, should I create a new bug, that "save as" for a new file does not use the directory of the last used file as a default one? I guess that would be some welcome improvement. Yes.
> This option too. Terminals since 1970 complete text if you press the "tab" key. Try that and it will complete the name to some existing file, which you can modify to your liking. And it was what you said yourself (https://bugs.kde.org/show_bug.cgi?id=434065#c4): > I need the same behaviour as vim has in any case. That is the vim behaviour but you were quick to ignore it. Seems more to me that you were making this some ego issue. Try having some respect for people working for free on the software that you use, it helps.
(In reply to Waqar Ahmed from comment #30) > Try having some respect for people working for free on the software that you use, it helps. I do have the respect, of course. I contribute to open source projects too. Including KDE. Though it was log ago… And when I require something I am trying to make the new software to be not worse than earlier versions. Unfortunately, I have not time now to implement this ticket myself.