<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Ben, an excellent explanation. I work with Mac.<div>Recently I experienced a problem with a new version of HKL2000. X11 window showing the diffraction frame stayed on for a very short time</div><div>before being closed. Somehow problem was sorted out by changing wireless environment to constant internet connection in my office.</div><div>But I suspect that, as I usually open automatically 8 tabs in a Terminal window, not all of them where doing the same procedure not completing</div><div>some X11 activation, stamp or sort of these things. I work with tcsh and not with bash from historical reasons. I hope that all you have written about bash</div><div>environment is true with some modifications also for tcsh. Anyhow it was very inspiring to read your message.</div><div>As there are less and less IT support for unix around we have to go back to school ourself and to learn or refresh essentials :-)</div><div>My best regards</div><div>FF</div><div> <br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Dr Felix Frolow <br>Professor of Structural Biology and Biotechnology, Department of Molecular Microbiology and Biotechnology<br>Tel Aviv University 69978, Israel<br><br>Acta Crystallographica F, co-editor<br><br>e-mail: <a href="mailto:mbfrolow@post.tau.ac.il">mbfrolow@post.tau.ac.il</a><br>Tel: ++972-3640-8723<br>Fax: ++972-3640-9407<br>Cellular: 0547 459 608</span>
</div>
<br><div><div>On Jan 30, 2013, at 03:08 , Ben Eisenbraun <<a href="mailto:bene@hkl.hms.harvard.edu">bene@hkl.hms.harvard.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Tue, Jan 29, 2013 at 10:54 AM, Kip Guja <<a href="mailto:kip@pharm.stonybrook.edu">kip@pharm.stonybrook.edu</a>> wrote:<br><blockquote type="cite">You need to use .profile not .bashrc on a Mac<br></blockquote><br>Actually that's not true.<br><br>In the case of bash, a login shell will read /etc/profile,<br>~/.bash_profile, ~/.bash_login, and ~/.profile in that order. A<br>subshell, i.e. an interactive shell that is not a login shell, will<br>read ~/.bashrc.<br><br>In the traditional UNIX windowing environment of X11, the X11 session<br>will invoke a login shell, reading one or all of the various profile<br>files, and all subsequent shells started via terminal emulators and<br>the like will usually be subshells, which will read your ~/.bashrc.<br><br>If you look at /Applications/Utilities/XQuartz.app/Contents/MacOS/X11,<br>you'll see that the Xorg ported to OS X does exactly this. A snippet:<br><br>case $(basename "${SHELL}") in<br> bash) exec -l "${SHELL}" --login -c 'exec "${@}"' - "${@}" ;;<br><br>Where users get tripped up on OS X is that many of them will use<br>Terminal.app as their terminal emulator, and since it's not an X11<br>application, it uses a login shell as the default shell in its<br>interface.<br><br>The solution is to just follow the Bash FAQ suggestion to have your<br>~/.bash_profile contain:<br><br>test -f ~/.bashrc && . ~/.bashrc<br><br>Which will ensure you always pick up your base shell environment<br>regardless of how the shell is started.<br><br>Hopefully some of that explanation helps you, Simon, but if you're<br>still stuck, you can run 'bash -x' to put the shell into debug mode as<br>it interprets your shell start up files. It should give you some clues<br>as to what's going wrong. Annoyingly that option is not documented in<br>the manpage on this machine. Here is some additional explanation:<br><br><a href="http://wiki.bash-hackers.org/scripting/debuggingtips#use_shell_debug_output">http://wiki.bash-hackers.org/scripting/debuggingtips#use_shell_debug_output</a><br><br>-ben<br>_______________________________________________<br>phenixbb mailing list<br>phenixbb@phenix-online.org<br>http://phenix-online.org/mailman/listinfo/phenixbb<br></blockquote></div><br></div></body></html>