This works in Dolphin/KDE too, actually same workflow as on Windows. I just find it very strange to do that, but as you are saying that, I suppose as on Unix everything is a file, copying a file to a location that cant handle the file is just like copying the filepath!
Boom, blew my silly KDE mind. I think you are right, in most situations you can just copy-paste the actual file, as you only need file paths where the file cannot be pasted anyways.
This might work sometimes, but some other times you are dealing with a program that deals in files and text and you want the path itself, for example, to send the path of a file in a shared mounted disk to a colleague/friend through slack /discord/telegram/teams. All of those will try to send the file itself instead of the path I would want to send.
Furthermore, idk how that interacts within a VM environment, for example when you have a work computer and you need to connect into a gnome based remote desktop environment, will the shared clipboard act nicely? That’s way too many variables and prone to errors, an option to copy path is just simpler.
If for some reason you paste a file in telegram/slack/discord/teams, it tries to send the file, so I have no way of sending the path to the file (which might be on a shared device) to someone unless I paste it in a text editor first and then copy the text.
Yay, basic features needing weird workarounds!
Edit: it seems like it, but we were wrong. You dont need a filepath, you can literally copy the file and paste it to a
Can someone give me a situation where you cant paste a file and it inserts the filepath instead?
I’m on KDE, how does KDE do it better?
On dolphin, you right click on it and than there is “copy path to file” button
How is it better if you are going to paste it anyway? I mean, on GNOME you would have to just copy the file, instead of the two clicks on KDE.
Am I missing something?
This works in Dolphin/KDE too, actually same workflow as on Windows. I just find it very strange to do that, but as you are saying that, I suppose as on Unix everything is a file, copying a file to a location that cant handle the file is just like copying the filepath!
Boom, blew my silly KDE mind. I think you are right, in most situations you can just copy-paste the actual file, as you only need file paths where the file cannot be pasted anyways.
This might work sometimes, but some other times you are dealing with a program that deals in files and text and you want the path itself, for example, to send the path of a file in a shared mounted disk to a colleague/friend through slack /discord/telegram/teams. All of those will try to send the file itself instead of the path I would want to send.
Furthermore, idk how that interacts within a VM environment, for example when you have a work computer and you need to connect into a gnome based remote desktop environment, will the shared clipboard act nicely? That’s way too many variables and prone to errors, an option to copy path is just simpler.
True. I suppose this is a useful feature
If for some reason you paste a file in telegram/slack/discord/teams, it tries to send the file, so I have no way of sending the path to the file (which might be on a shared device) to someone unless I paste it in a text editor first and then copy the text.
That’s a very logical use case. Are there any keyboard modifiers you could use? Maybe pasting with CTRL+SHIFT+V for example?