Adding desktop folder as a .desktop file folder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BAMF |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
Unity |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
Unity Foundations |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
unity-2d |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
bamf (Ubuntu) |
Fix Released
|
Wishlist
|
Marco Trevisan (Treviño) | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) |
Bug Description
This is a feature request, that doesn't follow exactly a standard, but a "de-facto" problem: it happens quite often that you create a new desktop link (manally, using the "create launcher" feature of Gnome-destktop, or using tools like Chromium Application creator); well, these .desktop files are completely ignored by BAMF when matching a window to an application, while they should have the greatest priority maybe from the user point of view.
What about adding the one line patch that would allow this? Monitoring the user desktop file too BAMF could be more precise when linking an application to a desktop file (that could be also customized)... I think that most of users wouldn't use ~/.local/
Related branches
- Jason Smith (community): Approve
- Unity Community Hackers: Pending requested
-
Diff: 1121 lines (+555/-236)3 files modifiedsrc/bamf-application.c (+27/-14)
src/bamf-application.h (+4/-4)
src/bamf-matcher.c (+524/-218)
Changed in bamf: | |
assignee: | nobody → Treviño (Marco Trevisan) (3v1n0) |
Changed in bamf (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in bamf (Ubuntu): | |
status: | New → Confirmed |
Changed in bamf: | |
status: | New → Confirmed |
affects: | unity → unity-foundations |
Changed in unity-foundations: | |
status: | New → Confirmed |
Changed in unity: | |
status: | New → Confirmed |
Changed in unity: | |
status: | Confirmed → In Progress |
Changed in bamf (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in unity-2d: | |
status: | New → In Progress |
Changed in bamf: | |
status: | In Progress → Fix Committed |
Changed in bamf (Ubuntu): | |
status: | In Progress → Fix Committed |
assignee: | nobody → Treviño (Marco Trevisan) (3v1n0) |
Changed in unity-foundations: | |
status: | Confirmed → Fix Committed |
Changed in unity-2d: | |
status: | In Progress → Fix Committed |
Changed in unity-foundations: | |
assignee: | nobody → Treviño (Marco Trevisan) (3v1n0) |
Changed in unity-2d: | |
assignee: | nobody → Treviño (Marco Trevisan) (3v1n0) |
Changed in unity: | |
assignee: | nobody → Treviño (Marco Trevisan) (3v1n0) |
status: | In Progress → Fix Committed |
Changed in unity: | |
milestone: | none → 4.4.0 |
Changed in bamf: | |
status: | Fix Committed → Fix Released |
Changed in unity: | |
status: | Fix Committed → Fix Released |
Changed in unity-2d: | |
status: | Fix Committed → Fix Released |
Changed in unity-foundations: | |
status: | Fix Committed → Fix Released |
Changed in bamf (Ubuntu): | |
status: | Fix Committed → Fix Released |
no longer affects: | bamf (Ubuntu Quantal) |
Changed in unity (Ubuntu): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
status: | New → Fix Released |
It seems to me that the Chromium issue is a bug that needs to be filed against that project, to make them generate the launcher into ~/.local (and then if they want, symlink to it on the Desktop).