0

I am using Windows and MobaXterm.

I created a .bash_profile file in the ~ directory and the following line

alias sbp="source ~/.bash_profile"

is the only code in that file.

However, when I was trying to do sbp, I got an error.

enter image description here

This works on my Mac and it used to work on my old Windows computer (but that one has some water damage so it broke down). Why does this not work now?

Thanks in advance!

Jodast
  • 1,279
  • 2
  • 18
  • 33
Seaky Lone
  • 992
  • 1
  • 10
  • 29
  • Have you checked that the alias really is that? `alias sbp` will show the alias. – Cupcake Protocol Sep 14 '18 at 00:21
  • @CupcakeProtocol Yes I have checked the syntax for about 1000 times. And actually some other aliases are also not working. The error messages are almost the same except the suffix. – Seaky Lone Sep 14 '18 at 00:26
  • Why would you want to source bash_profile? It should be automatically loaded when a new session starts. – Mia Sep 14 '18 at 01:20
  • @pkqxdd I don't have a new session. It's on my local computer. So I have to update it manually. And this should not be the problem. I also tried some code like ' alias cddt="cd C:/Users/Seaky/Desktop" '. Still doesn't work. – Seaky Lone Sep 14 '18 at 01:34

1 Answers1

4

From the way that error message is garbled I'm pretty sure that the .bash_profile file you created has DOS/Windows-style line endings, consisting of a carriage return character followed by a newline character. Unix tools expect unix-style line endings consisting of just a newline; if they see DOS/Windows-style endings, they'll treat the carriage return as part of the content of the line. In this case, bash will treat the carriage return as part of the alias definition, and therefore part of the filename to filename to source. Try running alias sbp | cat -vt to print the alias with invisible characters shown; my guess is it'll print alias sbp='source ~/.bash_profile^M' (where the ^M is cat -vt's way of representing the carriage return).

Solution: convert the file to unix format, and either switch to a text editor that knows how to save in unix format, or change your settings in the current editor to do it. For conversion, there are a number of semi-standard tools like dos2unix and fromdos. If you don't have any of those, this answer has some other options.

BTW, the reason the error message is garbled is that the CR gets printed as part of the error message, and the terminal treats that as an instruction to go back to the beginning of the line; it then prints the rest of the message over top of the beginning of the message. It's a little like this:

-bash: /home/dir/path/.bash_profile
: No such file or directory

...but with the second line printed over the first, so it comes out as:

: No such file or directory_profile
Gordon Davisson
  • 118,432
  • 16
  • 123
  • 151