Skip to content
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

.desktop files that are configured as a link to a folder are not sorted as folders themselves #3524

Open
TaliBytes opened this issue Feb 4, 2025 · 2 comments

Comments

@TaliBytes
Copy link

Distribution

22.1 Xia

Package version

6.4.3

Frequency

Always

Bug description

Nemo has an option (default) to sort folders before files. However, on occasion users may create .desktop files that behave as folders (essentially opening a new nemo window as a shortcut). These .desktop files are sorted with the rest of the files despite appearing as folders.

Steps to reproduce

Create a file named shortcut.desktop. nano /path/to/shortcut.desktop:

[Desktop Entry]
Version=1.0
Name=Folder Shortcut
Commnet=None
Exec=nemo "/path/to/destination/folder"
Icon=folder
Terminal=false
Type=Application

Put the shortcut.desktop folder in a directory that contains both sub-folders and files.

Expected behavior

Because the Icon is "folder" I expected these kinds of "files" to be treated as folders for continuity.

Additional information

No response

@Jeremy7701
Copy link
Contributor

Why not just use the nemo "Make Link" on your chosen folder, then move the link to some convenient location.

The link to the folder will display amongst the folders; selecting the link won't start a new version of nemo, but it will follow the link and open the destination folder in the normal way.

Choosing an icon name in a desktop file doesn't determine the mime type (file type).

@TaliBytes
Copy link
Author

Why not just use the nemo "Make Link" on your chosen folder, then move the link to some convenient location.

Good question. I failed to mention I tried this and it might actually be something more important to address than my issue... Using this method doesn't open the remote folder (mounted via samba). Nano simply states the link is broken, even though I can manually navigate into the remote.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants