Question: Application launchers, Mate desktop
 

LinuxMint18, Mate desktop

I have a desktop launcher with the command:

env WINEPREFIX="/home/myusername/.wine" wine C:\\Program\ Files\ \(x86\)\\DVD\ Shrink\\DVD\ Shrink\ 3.2.exe

This works just fine. It also works fine if I put it as a launcher on the taskbar using this exact same command.

But I want it as a launcher on the Mate menu. When adding launchers to the Mate menu you must choose a type of "Application" or "Application in terminal". No such choice is required (or even available) in a desktop or taskbar launcher. It works from the Mate menu if I chose "Application in terminal", but it leaves a terminal window displaying, which I would like to avoid. It does not work if I chose "Application" (nothing happens - the application does not launch).

Is there any way to make this work from the Mate menu, WITHOUT having to display the terminal window too? Similar to the way it works for desktop and taskbar launchers?

Thanks in advance for any suggestions!

[edit]spelling correction[/edit]

just to get things straight, please post output of
(assuming your launcher is called "TheLauncher")

Here is right-click -> properties of the desktop icon:

Note: The desktop icon works 100%. So does the taskbar icon. It is the Mate menu launcher that doesn't work (unless it also displays the terminal window that I want to get rid of). I created the Mate menu launcher by cut-n-paste'ing the command from the right-click -> properties desktop icon.

paste the command into a textfile, e.g. like this:
make the file executable and point mate menu to that instead.
hope it works.

I couldn't get Mate menu to execute that shell file. It kept popping up some error, although executing the shell file from the command line worked. So the file was OK, just something about Mate menu not being able to execute it.

Oh well. This is not a show-stopper issue for me. I can use things as they are.

Thanks for trying to help, I appreciate it!

i don't know if i already told you, but you really need to post
a) exactly what you did, commands issued, checkboxes checked etc.
b) exact and complete error messages.

if you adhere to that, we will get there evtl.

Sorry, I was out of town for a while and not able to respond.

I just went to recreate my last failed attempt, to show you the error message. But when I recreated that previous failure, IT WORKED! So, no telling what I did the first time when I attempted it. Must have been some typo or other user error on my part.

FWIW, below screenshots show what worked for me, exactly like I want it to work. The screenshot showing the launcher is a launcher from the MATE menu (not a launcher from the desktop or the taskbar, which are different). It was the MATE menu launcher that I could not get to work previously. Now it works!

@ondoho - Thanks for the help! :)

that's all good and solved;

the next bit is optional, it's about cleaning your system and getting the best functionality:

you should rename /home/david/Bin to /home/david/bin.
IF ~/bin is in your $PATH, then you could e.g. execute DVDShrink.sh without having to enter the full path.

so do this: rename the folder to bin, log out and back in, then post the output of this command:
(and please copy-paste the actual text, and use code tags here on the forum. don't make a screenshot)

Thanks for the suggestion. I know about $PATH, and that Bin is non-standard as compared to bin. I'm pretty old school, and don't normally use capital letters or spaces in file/directory names, having come from a C systems programming background in Unix back in the System V days in the early 80's.

I am in the process of rearranging my home desktop so it's shared across an SSD (for OS/application) and a WD Black harddrive (for media and other stuff that does not need fast SSD access). Under my $HOME directory, I have taken up the convention - temporarily - that subdirectories that exist in their final location (SSD vs HDD) are named in the conventional manner (lower case first letter of directory name). And things that still need to be moved to their final destination are named with a capital first letter. BTW, since I mentioned my old Unix days above, you might recognize this naming as a variation of the /etc/rcX.d files for init - the case of the first letter of the name determined if it would be executed or not. I'm using that same concept of first letter case here - the case tells me if I still need to do something with that directory or not.

In the end, all my directories will be named normally, starting with lower case letters, but I'm not to that point in the transition yet.