custom terminal command

Janus84 · 06-15-2020, 02:42 AM

There's so much on this topic out there but I'm still confused.
I had the objective to run an .exe file without typing

Code:

$ cd (when somewhere else in file system)
$ wine winbox64.exe

I only want to type

Code:

$ winbox

regardless of where I am.

I have created a bash script winbox.sh

Code:

#! /bin/bash

#launch MikroTik Winbox using Wine
wine winbox64.exe

which allows me to use

Code:

winbox.sh

But I still need to be in ./ directory which is fine for now

So I tried to create an alias in my bashrc file:

Code:

# User specific aliases and functions
alias winbox='bash ./winbox.sh'

but this still happens

Code:

$ winbox
bash: winbox: command not found

If someone can please correct me, I'd like to also create another command that would launch a .jar file that I use all the time.

pan64 · 06-15-2020, 03:25 AM

use full path to winbox.sh

berndbausch · 06-15-2020, 03:31 AM

Quote:

Originally Posted by Janus84

So I tried to create an alias in my bashrc file:

That's not sufficient. You have to execute your bashrc file, either by logging on or this way:

Code:

source $HOME/.bashrc

However, the winbox alias will try to run ./winbox.sh. This only works if the current directory contains winbox.sh.

Rather than juggling with aliases, copy winbox.sh into a directory that is in your path. For example, in .bashrc or .bash_profile, ensure that PATH contains $HOME/bin. For example:

Code:

PATH=$PATH:$HOME/bin

Then make winbox.sh executable and move it to $HOME/bin:

Code:

chmod +x winbox.sh
mv winbox.sh $HOME/bin/winbox

Once you have activated your PATH by logging on again, you should be able to run winbox no matter what is your current directory.

EDIT: pan64's suggestion works as well.

Janus84 · 06-15-2020, 05:36 AM

Quote:

Originally Posted by pan64

use full path to winbox.sh

That fixed it, thanks

Janus84 · 06-15-2020, 05:47 AM

Quote:

Originally Posted by berndbausch

Rather than juggling with aliases, copy winbox.sh into a directory that is in your path.

I have added PATH into bashrc but

Code:

PATH=$PATH:$HOME/bin

was showing in red.
I have changed to

Code:

PATH="$HOME/bin:$PATH"

would that be ok?

Now I have

Code:

~/bin$ ls -l
total 8
-rwxr-xr-x 1 root root 73 Jun 15 22:15 ubnt.sh
-rwxr-xr-x 1 root root 67 Jun 15 22:14 winbox.sh

but

Code:

~/bin$ winbox
bash: winbox: command not found

I did log out and then back in.

pan64 · 06-15-2020, 06:46 AM

in windows you can omit the extension, because the OS will try different extensions to find the real executable or script. But in linux you need to specify exactly the same name. So if it was named winbox.sh you need to type winbox.sh. Obviously you can create an alias which will replace the alias winbox to something usable (like: alias winbox=winbox.sh).

Roken · 06-15-2020, 07:19 AM

or just rename winbox.sh to winbox