Section: User Contributed Perl Documentation (3pm)
my $entry = File::DesktopEntry->new('firefox');
This module is used to work with .desktop files. The format of these files is specified by the freedesktop ``Desktop Entry'' specification. This module can parse these files but also knows how to run the applications defined by these files.
For this module version 1.0 of the specification was used.
This module was written to support File::MimeInfo::Applications.
$File::DesktopEntry::VERBOSE. If set the module print a warning every time a command gets executed. The global variable
$File::DesktopEntry::LOCALEtells you what the default locale being used is. However, changing it will not change the default locale.
"get(KEY)"where key is the autoloaded method name.
"\"' or '
"."') a lookup is done using File::BaseDir. If the file found in this lookup is not writable or if no file was found, the XDG_DATA_HOME path will be used when writing.
The child process fails when this is not a Desktop Entry of type Application or if the Exec key is missing or invalid.If the desktop entry specifies that the program needs to be executed in a terminal the
$TERMINALenvironment variable is used. If this variable is not set
"xterm -e"is used as default.
(On Windows this method returns a Win32::Process object.)
"run()"but using the
"system()"system call. It only return after the application has ended.:
"run()"but using the
"exec()"system call. This method is expected not to return but to replace the current process with the application you try to run.
"fork()"emulation on this platform. Try using
It supports the following fields:
%f single file %F multiple files %u single url %U multiple urls %i Icon field prefixed by --icon %c Name field, possibly translated %k location of this .desktop file %% literal '%'
If necessary this method tries to convert between paths and URLs but this is not perfect.
Fields that are deprecated, but (still) supported by this module:
%d single directory %D multiple directoriesThe fields
%mare deprecated and will cause a warning if
$VERBOSEis used. Any other unknown fields will cause an error. The fields
%ican only occur as separate words because they expand to multiple arguments.
Also see ``LIMITATIONS''.
"$entry->get('Name[nl_NL]')"can return either the value of the 'Name[nl_NL]', the 'Name[nl]' or the 'Name' key in the Desktop Entry file. Exact language parsing order can be found in the spec. To force you get the untranslated key use either 'Name[C]' or 'Name[POSIX]'.
:"set(KEY => VALUE, ...)"
"get()"call languages are not handled automatically for
"set()". KEY should include the language part if you want to set a translation. E.g.
"$entry->set("Name[nl_NL]" => "Tekst Verwerker")"will set a Dutch translation for the Name key. Using either ``Name[C] or ``Name[POSIX] will be equivalent with not giving a language argument.
When setting the Exec key without specifying a group it will be parsed and quoted correctly as required by the spec. You can use quoted arguments to include whitespace in a argument, escaping whitespace does not work. To circumvent this quoting explicitly give the group name 'Desktop Entry'.
If you gave a file, text buffer or name to the constructor this method will be called automatically.
"Directory". For an application set the optional key
"Exec". For a link set the
Methods supported for backwards compatibility with 0.02.
"get(GROUP, "NAME[LANG]")". LANG defaults to 'C', GROUP is optional.:
"file://"uri a bit different and it uses Win32::Process. On other platforms your mileage may vary.
Please note that the specification is targeting Unix platforms only and will only have limited relevance on other platforms. Any platform-dependent behavior in this module should be considered an extension of the spec.
"wants_uris()"method to check if an application supports urls.
The values of the various Desktop Entry keys are not parsed (except for the Exec key). This means that booleans will be returned as the strings ``true and ``false and lists will still be ``;'' separated.If the icon is given as name and not as path it should be resolved for the
%icode in the Exec key. We need a separate module for the icon spec to deal with this.
Files are read and written using utf8, this is not available on perl versions before 5.8. As a result for older perl versions translations in UTF-8 will not be translated properly.
According to the spec comments can contain any encoding. However since this module read files as utf8, invalid UTF-8 characters in a comment will cause an error.
Jaap Karssenberg (Pardus) <[email protected]>
File::BaseDir and File::MimeInfo::Applications
Tutoriais de Tecnologia Web