https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #31 from Dmitri Koulikoff ---
(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
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #30 from Waqar Ahmed ---
> 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
--- Comment #29 from Christoph Cullmann ---
> 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.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #28 from Dmitri Koulikoff ---
(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 cas
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #27 from Dmitri Koulikoff ---
(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 us
https://bugs.kde.org/show_bug.cgi?id=434065
Christoph Cullmann changed:
What|Removed |Added
Resolution|FIXED |NOT A BUG
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=434065
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #25 from Waqar Ahmed ---
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 ka
https://bugs.kde.org/show_bug.cgi?id=434065
Dmitri Koulikoff changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=434065
Waqar Ahmed changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #22 from Dmitri Koulikoff ---
Created attachment 145544
--> https://bugs.kde.org/attachment.cgi?id=145544&action=edit
trouble to add a new file to a directory
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434065
Dmitri Koulikoff changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=434065
Waqar Ahmed changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=434065
Dmitri Koulikoff changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INTENTIONAL
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #18 from Dmitri Koulikoff ---
A good idea is to block creating a backup file for empty content.
And by the way your apporach requires one extra click ;-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #17 from Christoph Cullmann ---
(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 "im
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #16 from Dmitri Koulikoff ---
(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 yea
https://bugs.kde.org/show_bug.cgi?id=434065
Kåre Särs changed:
What|Removed |Added
CC||kare.s...@iki.fi
--- Comment #15 from Kåre Särs --
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #14 from Dmitri Koulikoff ---
(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
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #13 from Dmitri Koulikoff ---
Created attachment 137441
--> https://bugs.kde.org/attachment.cgi?id=137441&action=edit
What can be easiery to create a new file in the given place with the given
name?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #12 from Waqar Ahmed ---
> 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
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #11 from Christoph Cullmann ---
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 giv
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #10 from Dmitri Koulikoff ---
Created attachment 137399
--> https://bugs.kde.org/attachment.cgi?id=137399&action=edit
no create item
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #9 from Dmitri Koulikoff ---
(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
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #8 from Waqar Ahmed ---
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
https://bugs.kde.org/show_bug.cgi?id=434065
--- Comment #7 from Dmitri Koulikoff ---
(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
https://bugs.kde.org/show_bug.cgi?id=434065
Waqar Ahmed changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=434065
Waqar Ahmed changed:
What|Removed |Added
CC||waqar@gmail.com
--- Comment #5 from Waqar Ahm
https://bugs.kde.org/show_bug.cgi?id=434065
Dmitri Koulikoff changed:
What|Removed |Added
Resolution|INTENTIONAL |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=434065
Dominik Haumann changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=434065
Dmitri Koulikoff changed:
What|Removed |Added
Resolution|INTENTIONAL |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=434065
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
CC|
32 matches
Mail list logo
