Shell Programming and Scripting

In your script:

Code:

export PATH=$PATH:/path/to

or specify the PATH variable absolutely, without a reference to $PATH.

I use ksh as my login shell. The way I set PATH in my .profile file is:

Code:

PATH=$HOME/bin:$PATH:.
export PATH

which looks for commands in the bin subdirectory of my home directory first, the default locations set up by the system administrator on my system, and the current directory. I don' t include the current directory (specified by .) when I'm running as root, and many people never put . in PATH to avoid security issues that can pop up if you execute commands in a directory where other people can create files. If you put . in path anywhere but as the last entry, it makes this more likely to be a problem.

If you are using bash as your login shell, you need to set PATH in the first file in your home directory that has a name in this list: .bash_profile, .bash_login, and .profile. After updating the way you initialize PATH you will need to either log out and log back in or run the command:

Code:

. filename

where filename is the name of the file in which you changed the way you set PATH.

I think, in this case this can be done simpler using

Code:

dos2unis p4

provided this tool is available (usually it is).

---------- Post updated at 09:14 AM ---------- Previous update was at 09:07 AM ----------

The Notepad++ settings for line endings apply for new files only. If you open existing files, Notepad++ uses the line endings for this file.

You can explicitly change the line endings (EDit/EOLconversion).

With View/ShowSymbol/ShowEndOfLine turned on, Notepad++ will actually show you the EOL character for each line. In addition, if you see in the status line the word "Unix", you know that \n line endings are used for this file.

I guess you mean dos2unix? And, it may NOT be available all about, not even common linux distributions, but needs to be installed.

Yes, thank you for pointing out the typo. I blame myself, plus the person who puts the S next to the X on the keyboard.

And, that's why I said: "provided it is available", but it is easy to get anyway.

BTW, since the OP is obviously working on Windows for editing, but having Unix as a target platform, he maybe has Cygwin installed too (it would make sense at least), and dos2unix is available as a Cygwin package also. I prefer it over blindly erasing all carriage returns, because if, for whatever reason, an isolated \r appears somewhere in my code, I don't want to go it silently away. It's a matter of taste, of course.