Im trying to make a bash script that opens up a konsoe window and executes the cmmands in the script.However when I use the command konsole -e it allows me to enter only one command. how ca I make it run commands one after the other.

The big problem is not concatenating commands, but dumping them into a newly created terminal emulator.

I usually do this (just a simple example):

Feel free to use ||, && or ; depending on the effect you need to achieve in between the quotes. Also, in the example I use urxvt, but you can use konsole instead if you want. You will need to figure out the -e equivalent for konsole, I don't have it installed to check.

This is a the service menu I am trying to make:


[Desktop Entry]
Version=1.0
ServiceTypes=video/*
Actions=conv2mp3
X-KDE-Submenu=Convert Audio/Video

[Desktop Action conv2mp3]
Name=MP3
Exec=konsole -e "input_file='%f' && output_file_name=${input_file/.*/}&& ffmpeg -i '${input_file}' -acodec libmp3lame -ab 160k -ac 2 -ar 44100 '${output_file_name}.mp3'"


The && works in xterm but it doesnt recognize the %f and I thinks konsole recognizes it but cannot run multple commands

Try to wrap it as I did above. Instead of directly launching the stuff, use konsole -e bash -c "commands". (though my guess is that this might not work either).

Your best bet to do this kind of stuff is to wrap everything into a shell script. Then, just call your shell script instead of concatenating so much commands.

Yes i tried it but it doesnt recognize the %f which is the file location of the selected file

ok is there a way to run a command and show the output in a terminal

Only by running into it.

I'd try something like this:

Now, you need to save that script into a directory that's in your $PATH, and chmod u+x it.

On the desktop file you do:

Note that I know very little about .desktop files so I don't know if the quotation has been done correctly (the bash script should be ok, though).

Thank you so much.Solved my problem.ur the best.

Glad it helped.

In case you are wondering, the key point when passing the argument is that kde pass arguments using %f, %u and things like those.

On the contrary, bash doesn't know about the nature of the arguments, and they are named by their position. On the kde land, we pass %f to our script, but once we are into the bash script, and since %f is the first parameter, we access this positional parameter as $1. That's the key, the rest is simple enough to understand if you made that long command line for the initial desktop file.