You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2022. It is now read-only.
Gabriel Boorse
The "Copy Row as Text" (Alt + C) option does not properly copy the names of folders but instead adds a bunch of semicolons on the end. Notice that file names are copied properly with info about the file listed between semicolons. This issue is probably caused because folders don't have attributes other columns in the list view. I have a screenshot attached of when I tried to copy the row of a folder into another text box.
Teknomancer
I think this is the expected behaviour with copying text in the CSV (comma-separated values) format.. I don't remember why I originally needed to copy stuff in CSV format but this was what it was meant for and thus for missing columns it shows empty values with ';' separators.
I will look into it if it makes sense to have this (probably does help a lot) or if I can make it less obscure.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Gabriel Boorse
The "Copy Row as Text" (Alt + C) option does not properly copy the names of folders but instead adds a bunch of semicolons on the end. Notice that file names are copied properly with info about the file listed between semicolons. This issue is probably caused because folders don't have attributes other columns in the list view. I have a screenshot attached of when I tried to copy the row of a folder into another text box.
Teknomancer
I think this is the expected behaviour with copying text in the CSV (comma-separated values) format.. I don't remember why I originally needed to copy stuff in CSV format but this was what it was meant for and thus for missing columns it shows empty values with ';' separators.
I will look into it if it makes sense to have this (probably does help a lot) or if I can make it less obscure.
The text was updated successfully, but these errors were encountered: