I suggest NOT deleting the ".profile" file. Instead, we'll just rename it, and put a new shell startup in a different file. My reasons for using a different file are given below, after the command lines.
You should be able to copy and paste each hilited "Code" section below. The second one is intended as a multi-line copy/paste, so be sure to do it that way.
First, rename the existing ".profile" file:
Code:
mv ~/.profile ~/was-profile
Second, create a new shell startup file with only the setup for FSL in it:
Code:
cat >~/.bash_profile <<- '--EOF--'
# FSL Setup
FSLDIR=/usr/local/fsl
PATH=${FSLDIR}/bin:${PATH}
export FSLDIR PATH
. ${FSLDIR}/etc/fslconf/fsl.sh
--EOF--
Third, confirm the contents of ".bash_profile":
Fourth, list the directory contents and post it:
You will have a Finder-visible file in your home folder named "was-profile". Don't delete it yet, keep it around for a few days.
At this point, you can test whether the change works or not. You should be able to open a new Terminal window, and it should not say anything.
If you quit Terminal and relaunch it, the first window opened should do the same: nothing said. This demonstrates that the change persists between launches of Terminal.
A further test would be to log out and login again, or do a Restart of the computer. Running Terminal.app should say nothing.
-- Explanation --
I used the shell startup file named ".bash_profile" instead of ".profile" because the shell looks for that file first. If it sees it, it runs the commands therein, and then doesn't even look for a ".profile" file.
The reason I did it this way is because of a puzzling thing I saw in the listing of ~, which I reproduce here:
Code:
-rw-r--r-- 1 MissDefy staff 13 May 21 14:28 $
drwxr-xr-x+ 33 MissDefy staff 1122 May 21 17:52 .
drwxr-xr-x 6 root admin 204 May 21 00:38 ..
-rw------- 1 MissDefy staff 3 Oct 14 2011 .CFUserTextEncoding
-rw-r--r--@ 1 MissDefy staff 24580 May 22 2013 .DS_Store
drwx------ 2 MissDefy staff 68 May 21 17:53 .Trash
-rw------- 1 MissDefy staff 312 May 21 17:52 .Xauthority
-rw------- 1 MissDefy staff 14281 May 21 17:52 .bash_history
-rw-r--r-- 1 MissDefy staff 90 Aug 24 2012 .cim_install_log
drwx------ 3 MissDefy staff 102 Aug 25 2011 .cups
drwx------ 16 MissDefy staff 544 May 22 2013 .dropbox
drwxr-xr-x 3 MissDefy staff 102 May 21 17:52 .fontconfig
drwxr-xr-x 3 MissDefy staff 102 Aug 21 2012 .matlab
drwxr-xr-x 6 MissDefy staff 204 Oct 24 2012 .network_backups
[COLOR="Red"]-rw------- 1 MissDefy staff 135 May 22 2013 .profile
[/COLOR]-rw------- 1 MissDefy staff 80 May 21 17:52 .serverauth.1041
drwxr-xr-x 3 MissDefy staff 102 Jul 19 2011 .ssh
drwxr-xr-x@ 4 MissDefy staff 136 Feb 18 05:07 ACUVE_color_files
drwx------+ 30 MissDefy staff 1020 May 21 17:53 Desktop
drwx------+ 10 MissDefy staff 340 Nov 15 2012 Documents
drwx------+ 465 MissDefy staff 15810 May 21 2013 Downloads
drwx------@ 9 MissDefy staff 306 May 22 2013 Dropbox
drwxr-xr-x 5 MissDefy staff 170 May 18 16:44 Gamez
drwx------+ 42 MissDefy staff 1428 May 19 23:33 Library
drwx------+ 35 MissDefy staff 1190 May 21 01:02 Movies
drwx------+ 31 MissDefy staff 1054 May 18 16:06 Music
drwx------+ 28 MissDefy staff 952 May 21 01:38 Pictures
drwxr-xr-x+ 6 MissDefy staff 204 Aug 1 2011 Public
drwxr-xr-x 29 MissDefy staff 986 May 3 13:43 Random
drwxr-xr-x+ 6 MissDefy staff 204 Aug 1 2011 Sites
drwxr-xr-x 14 MissDefy staff 476 May 21 2013 Work
drwxr-xr-x 3 MissDefy staff 102 Apr 26 17:36 matlab
-rw-r--r-- 1 MissDefy staff 758066 May 18 05:26 strings.txt
I've hilited the info for ".profile" in red.
The puzzling thing is the modification-date shown for ".profile". It's around the same day as when you posted this listing. Which means that something either changed the ".profile" around the same time you made the listing, or something used the 'touch' command to change the modification-date of that file.
Normal shell startup doesn't change the mod-dates of ".profile" files, although something in the secondary FSL shell startup might. Without seeing the contents of the FSL shell startup file, it's just a guess. I don't need to see it now, but if the whispering "I see you" problem isn't solved, or it comes back, I may ask you to attach it. If that happens, I'll give specific instructions.
The other thing to notice is that the ".dropbox" and "Dropbox" folders have a similar modification date to that of the ".profile" file. So maybe the ".profile" file is getting written due to Dropbox. That's just a wild guess at this point, based on nothing more than the similar mod-dates.
So, if the ".profile" file is somehow being changed via Dropbox, then using ".bash_profile" will cause the shell to ignore any ".profile" file that happens to show up.
Anyway, if this solves the problem, and it doesn't reappear after Dropbox gets used, then it should continue to work, without breaking FSL. If the problem reappears, then post again and we can take another look.
This still doesn't give a definite answer to the question of how the whispering ".profile" file got there in the first place. Unfortunately, that's nearly impossible to figure out without a detailed examination of the entire disk, along with a bunch of answers to questions like what websites are visited, what web services are used (e.g. Dropbox), what matlab modules are used, and so on. That's a time-consuming and expensive process, at best. And it may not even come up with an answer.