directoryfile-managerkeyboard shortcutsmkdir
In many file managers there is a shortcut/key to create a new folder. In Nautilus, Thunar, Panthon-Files, this is Ctrl+Shift+N, in Dolphin it is F10.
How does this shortcut work?
I imagine that behind it it's a mkdir command, but that would need a path (like discussed here). I can imagine that opening the file manager at a certain location and using the shortcut, this triggers the needed command: is this what happens? What command is that? Can a custom shortcut be used for the same purpose?
The idea is to already have the needed programs in the 'Open with' context-menu for a selected folder without the need to select "Other application".
Editing the line inode/directory= in /usr/share/applications/mimeinfo.cache is not useful because, as indicated in a comment by don_crissti, the problem re-appears after an update or a program install because of the command update-desktop-database.
In fact only some programs will take over the file manager role as indicated by the question, but those that do will in some cases take over directly, simply after their installation, and will do again after update-desktop-database.
As suggested here by the aforementioned user, you need to edit ~/.local/share/applications/mimeapps.list like:
[Default Applications]
inode/directory==nemo.desktop;audacious.desktop;deadbeef.desktop;vlc.desktop
In another system (Cinnamon Manjaro, where there is no mimeapps.list in usr/share/applications, only mimeinfo.cache and seems non-freedesktop-complient) the file to use is ~/.local/share/applications/mimeinfo.cache with a content like
[MIME Cache]
inode/directory==nemo.desktop;audacious.desktop;deadbeef.desktop;vlc.desktop
It is essential to put the file manager first and then the programs to add to the 'open with' context menu.
For example, the above will give
Sounds like a resolving issue around NMB. It's mentioned here in this thread titled: Nautilus doesn't see network computers... [SOLVED].
non-discovering resolve order# What naming service and in what order should we use to resolve host names
# to IP addresses
name resolve order = lmhosts host wins bcast
name resolve order = bcast lmhosts host wins
Be sure to restart NMB/SMB services once you've made this change.
Researching your issue further, I came across this tip in this AU Q&A titled: Nautilus fails to see shares in 18.04. The tip from there was to change the following:
$ more /etc/samba/smb.conf
workgroup = WORKGROUP
client max protocol = NT1
After making the above changes it's advised to reboot, not simply restart.
As part of this tip, make sure that avahi service is running:
$ sudo service avahi-daemon status
$ sudo service avahi-demon start
According to this askfedora.org article titled: fedora 27 network browsing doesnt't work. Why? it's suggested to try disabling firewalld. It may be inhibiting the ports 137-139 which are required for Samba's NMB/SMB services to function properly.
Continued searches led to this issue that's still listed as open. The issue, titled: Bug 1513394 - Applications using gvfs are unable to browse SMB shares. It has to do with the package gvfs-smb.
Applications using gvfs are unable to browse SMB shares
These steps can be used to see if the issue afflicts your system.
Steps to Reproduce:
1. nmblookup -M -- -
2. nmblookup -M workgroup
3. smbtree
4. gio list network://
5. gio list smb:///
6. gio list smb://workgroup
If things don't work the results from the steps above will look like this:
1. will return IP address for __MSBROWSE__ special name
2. will return IP address for workgroup master browser
3. will correctly list workgroup, workgroup members and their shares
4. returned items are missing workgroup members
5. will return empty
6. will return an error message "The specified location is not mounted"
If things are working the results will look like this:
1. OK
2. OK
3. OK
4. returned items should contain workgroup members
5. should contain workgroup name
6. should contain workgroup members
It should be noted that there doesn't appear to be a fix yet for this:
For the record, it doesn't work in Fedora 28 and Samba 4.8 either.
Read the comments on the issue to see the rest of the story.
Best Answer
The new folder is not created until you actually provide a name, normally by typing something in what looks like a directory/folder name in the currently open directory/folder in the manager. Once you enter that name and press return the actual call to
mkdir()is executed (not themkdircommandline command). And if you directly press Enter you often get some default name.The event that you press Ctrl+Shift+N triggers the routine that creates the box where you change the name for the new folder and that sets the whole thing rolling.