-
-
Notifications
You must be signed in to change notification settings - Fork 972
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS: Dragging multiple files on the terminal does not separate them #4734
Comments
Also paths do not escape characters such as spaces, or use quotation marks. This also makes it difficult to use with multiple files. However I like the file path to remain as it is when dragging single file. ( without escaping ) I' m not sure if the style should be unified or treated differently. |
Line breaks will cause paths to be executed as commands in unsupported shells, or shells that cannot be integrated. Even in a text editor, it may be possible to run the built-in "terminal mode". Maybe space-separated is a better default. |
On Thu, Feb 24, 2022 at 09:55:06PM -0800, page-down wrote:
Line breaks will cause paths to be executed as commands in unsupported shells, or shells that cannot be integrated.
So what? Drag and drop is a highly intentional action, not something
easily triggered accidentally. I want multiple urls on different lines
when dropping anywhere except at a shell. Nowhere else would you want
multiple urls on a single line, and if you use space as a separator, it
is ambiguous since file paths can have spaces. (Technically they can
have line breaks as well, but that is almost never seen)
|
Oh an dmodern shells support bracketed paste, so unless they are badly configured, pasted newlines dont cause command execution. |
So command-line programs like busybox sh or others that do not support If some users have such special needs, they should use other terminals for these drag-and-drop tasks. Personally, I would never drag and drop content into these programs. |
Describe the bug
When I drag multiple files from the finder onto the terminal, the file paths are listed, but they are not separated with a space, thus rather unusable. I am unsure, but I'd say this has worked before and it certainly is the behaviour in other terminals.
To Reproduce
Steps to reproduce the behavior:
Environment details
Additional context
Try to reproduce the problem with
kitty --config NONE
: Same behaviour.The text was updated successfully, but these errors were encountered: