[04:36] <zequence> cub: if you investigate the contents of the desktop file, you will see the line which executes the application
[04:36] <zequence> /usr/bin/<something>, usually
[04:38] <zequence> Or, let me show an example
[04:38] <zequence> the desktop file ardour3.desktop
[04:38] <zequence> Name=Ardour3 (the name that appears in the menu)
[04:39] <zequence> Exec=/usr/bin/ardour3 (the actual binary)
[04:40] <zequence> Or, just the name is enough, cause that will make sure that what you see in the menu is for the right desktop file
[04:40] <zequence> Probably not a problem. I just put it in there in case
[04:41] <zequence> Right, I forgot to put in the rules
[04:41] <zequence> I was a little busy at the time. Still am. Also, a bit under the weather
[04:42] <zequence> Let me do some changes to the instructions during the coming weekend
[04:42] <DalekSec> zequence: he's long gone, mate.
[05:11] <zequence> DalekSec: He usually read the backlogs
[05:11] <zequence> It
[05:11] <DalekSec> Ah, pardon me then.
[05:11] <zequence> :)
[05:11]  * DalekSec ducks and hides.
[13:51] <ttoine> hello
[17:49] <cub> How about the blueprints, fdc-graphics contains kdenlive which is AudioVideo, is there something we should do to move it to fdc-video? Or does that not matter?
[17:51] <cub> Also, is the Categories order important? As for kdenlive it's: Qt;KDE;AudioVideo;AudioVideoEditing;
[17:58] <zequence> cub: kdenlive is for some reason put in the graphics section in Debian, so that should probably be changed upstream as well
[17:58] <zequence> I can't think of any other reason for the order being important than pure pedantism :).
[17:59] <cub> Aha
[17:59] <cub> I we find packages that might be dropped? Like Kino which hasn't been updated since 2009 and their webpage claims the project is dead. :D
[18:04] <zequence> Well, this is really a full go through of all multimedia packages, just the ones with desktop files. Other subjects than categorization is not a part of the plan.
[18:04] <zequence> this is not a full go-through, is what I meant
[18:05] <zequence> If Kino still works, I see no problem with keeping it in the repo, as long as the package maintainer is active
[18:05] <zequence> It's really a job for the maintainer to keep track of that, in Debian
[18:05] <zequence> But, if there are problems, one should report a bug and make sure the maintainer is aware of it
[18:09] <cub> Kino package is taken care of, and started just fine in my 14.04 
[18:09] <cub> Kino has 44 open bugs
[18:31] <zequence> atom has gone stable - http://atom.io
[18:36] <cub> Looks good. Still hooked on vim though.
[18:40] <zequence> I never started using anything beyond nano on terminal. Haven't had the patience to learn
[18:41] <zequence> There are some editing features that I'm not sure you can do in a terminal
[18:42] <zequence> Like cut and paste a section into a specific tab depth
[18:42] <zequence> Also, moving a selection left, right, 4 spaces with TAB, or SHIFT+TAB
[18:48] <cub> I have quite basic needs as long as I get 4 spaces tab, colour coding and Solarized theme