I think the issue is that we call
g_find_program_in_path ("mc")
for finding out whether midnight commander is available as the menu items are generated. This call causes disk I/O.
However, I'd also like to allow users to install midnight commander at run-time without requiring them to re-start Nautilus. I wonder how a proper caching stratgy could look like. An alternative strategy would be to open a dialog offering to install MC if it hasn't been installed yet. I think I'll ask in my blog.
Good catch, thanks for your bug report!
I think the issue is that we call program_ in_path ("mc")
g_find_
for finding out whether midnight commander is available as the menu items are generated. This call causes disk I/O.
However, I'd also like to allow users to install midnight commander at run-time without requiring them to re-start Nautilus. I wonder how a proper caching stratgy could look like. An alternative strategy would be to open a dialog offering to install MC if it hasn't been installed yet. I think I'll ask in my blog.