Menu-Spec and nested AppDirs

Mark McLoughlin markmc at
Thu May 26 11:28:19 EEST 2005

On Thu, 2005-05-26 at 08:37 +0200, Heinrich Wendel wrote:
> On Wednesday 25 May 2005 17:30, Mark McLoughlin wrote:
> > Hey,
> > 	My take on this would be that editors shouldn't be editing .desktop
> > files by making a copy with the same file ID and putting them in
> > ~/.local/share/applications. $XDG_DATA_HOME, AFAICT, is for application
> > data, not user configuration files.
> >
> > 	To show a concrete problem with doing it this way, if you installed a
> > vim package in your home directory, you'd expect the package to install
> > vim.desktop in ~/.local/share/applications, overriding the user's
> > changes.
> >
> > 	So, I think editors should be creating their own directory for
> > edited .desktop files, say ~/.config/pyxdg-applications and copying
> > the .desktop files there, but with a different desktop file ID.
> And a MenuEditor is no application that provides data? I don't think that's 
> the right approach, it would make desktop-file-ids meaningless.

	Let me put it another way ... if you were writing a system-wide menu
editor, would it be valid for the editor to
modify /usr/share/debian/applications/vim.desktop? Or even
create /usr/local/share/debian/applications/vim.desktop?

	Because, if I understand the purpose of $XDG_DATA_HOME correctly, then
its the same thing.


More information about the xdg mailing list