Currently, gVim desktop file (/usr/share/applications/gvim.desktop) Exec entry reads: Exec=gvim -f When using a file manager on which we assigned gvim to open a file, the file manager will not pass the selected file's location. gvim accepts URIs, so using %U is expected. Reproducible: Always Steps to Reproduce: 1. Assign a file type to gvim. 2. Open a file. Actual Results: gvim opens with no file. Expected Results: gvim should open the selected file.
Created attachment 129215 [details] corrected desktop file for gvim
$ desktop-file-validate gvim.desktop gvim.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated gvim.desktop: error: value "text/css;text/html;text/htmlh;text/plain;text/rss;text/sgml;text/x-adasrc;text/x-authors;text/x-c++hdr;text/x-c++src;text/x-copying;text/x-credits;text/x-csharp;text/x-csrc;text/x-dtd;text/x-fortran;text/x-gettext-translation-template;text/x-gettext-translation;text/x-gtkrc;text/x-haskell;text/x-idl;text/x-install;text/x-java;text/x-js;text/x-ksh;text/x-ksysv-log;text/x-literate-haskell;text/x-log;text/x-makefile;text/x-moc;text/x-msil;text/x-nemerle;text/x-objcsrc;text/x-pascal;text/x-patch;text/x-readme;text/x-scheme;text/x-setext;text/x-sql;text/x-tcl;text/x-tex;text/x-texinfo;text/x-troff-me;text/x-troff-mm;text/x-troff-ms;text/x-uil;text/x-vb;text/xml" for string list key "MimeType" in group "Desktop Entry" does not have a semicolon (';') as trailing character gvim.desktop: warning: value "Application;Development;" for key "Categories" in group "Desktop Entry" contains a deprecated value "Application" $
Created attachment 129239 [details] corrected desktop file for gvim (v2)
Well, I originately only added %U, but here is modified version which should address warnings and errors.
vim-7.1.123 which is in CVS uses a new gvim.desktop file. %U is known to have problems with unicode filenames[1] so I changed it to gvim -f %F Thanks for reporting ;) [1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406586 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426243
Strange, it works for me whatever strange Unicode characters I use (UTF-8 locale) and Enlightenment's integrated file manager. Anyway, it should not be a problem :)
