[SOLVED] BASH in new SUSE 42.2, command EXPR does not work?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Did you notice it is using YOUR ~/bin/expr? What is 'that'? cd /home/mats/bin; ls -l expr; file expr; ... (maybe cat it!)
Try \expr 1 + 1 (backslash to force 'system' expr)
Sorry, my mistake! By mistake there was an "expr" in /home/mats/bin that was taken instead of the real "expr". This "expr" was in fact the simple test:
a=`expr 1 + 1`
echo $a
Because of the name-collisition it was then calling itself! I have no idea how this test got into this directory with this name!
I did not think of this possibility! But I really should like Jjanel have noted "/home/mats/bin" in the prompt!
yeah if that is some expr exe in that dir /.../.../.../expr then it'd be dot forword slash command ./expr 1 + 1 BUT if you got an expr already installed in /usr/bin then you should not be having this issue becsuse it'd already just work because /usr/bin should be in your PATH - echo $PATH to see
Code:
userx%slackwhere ⚡ ~ ⚡> ls /usr/bin/expr
/usr/bin/expr
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.