Re: Leopard Migration Hammered Mutt
On Sun, Jan 27, 2008 at 09:31:17PM CST, Bill [EMAIL PROTECTED] wrote: Since I would like to add /sw/bin to my /etc/profile I opened it, but only discovered: ___ # System-wide .profile for sh(1) if [ -x /usr/libexec/path_helper ]; then eval `/usr/libexec/path_helper -s` fi if [ ${BASH-no} != no ]; then [ -r /etc/bashrc ] . /etc/bashrc fi ___ This is not what I expected, and can't think of where I should add /sw/bin/ to my path. Forget messing with /etc/profile. Did you try my suggestion? A short time ago, Eugene wrote: /sw indicates Fink. http://www.finkproject.org/doc/bundled/install-fast.php The last command runs a little script to help set up your Unix paths (and other things) for use with Fink. In most cases, it will run automatically, and prompt you for permission to make changes. If the script fails, you'll have to do things by hand. (If you need to do things by hand, and you are using csh or tcsh, you need to make sure that the command source /sw/bin/init.csh is executed during startup of your shell, either by .login, .cshrc, .tcshrc, or something else appropriate. If you are using bash or similar shells, the command you need is . /sw/bin/init.sh, and places where it might get executed include .bashrc and .profile.) So basically add the line . /sw/bin/init.sh into your ~/.profile or ~/.bash_profile init files. This should add /sw/bin to your PATH, and set up other Fink-related environment variables as well. -- Eugene
Re: Leopard Migration Hammered Mutt
On Sat 26.Jan'08 at 13:02:26 -0500, Marc Vaillant wrote: On Sat, Jan 26, 2008 at 05:13:11PM +, [EMAIL PROTECTED] wrote: export shows: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? put export PATH=${PATH}:/sw/bin in ~/.profile You may want to try just typing /sw/bin/mutt first just to see if it works properly after migration. Raffi
Re: Leopard Migration Hammered Mutt
On Monday, 28 January 2008 at 02:49, [EMAIL PROTECTED] wrote: Thanks, Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? http://www.finkproject.org/doc/users-guide/install.php?phpLang=en#setup (in short, source /sw/bin/init.sh in .bash_profile)
Re: Leopard Migration Hammered Mutt
Thanks, Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? Bill -- Original message -- From: Peter Münster [EMAIL PROTECTED] On Sat, Jan 26 2008, [EMAIL PROTECTED] wrote: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Hello, Just after logging in, you can enter the command ls -alrut, that shows in the last lines, the files that have just been read. Among these files, there should be an initialisation file for your shell, for example .bashrc or .profile. In the end of this file, you can put the line PATH=$PATH:/sw/bin (for a csh-like shell, the syntax is perhaps different...) Cheers, Peter
Re: Leopard Migration Hammered Mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 02:49 AM, quoth [EMAIL PROTECTED]: Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? It adds it to the existing path. Your Path is stored as a colon-separated list of folders containing programs (e.g. /bin:/usr/bin:/sbin:/usr/sbin). The string $PATH is a reference to the existing path---if you say echo $PATH your shell will print out your current PATH, because that's the string referred to be the notation $PATH. When you tell your shell to set a variable name to be something, it performs a similar kind of expansion. For example, if you say FOO=$PATH, the variable FOO will now contain a copy of the contents of the variable $PATH. You can append things to variable expansions, because the shell operates almost entirely in terms of lines of text. For example, if you say FOO=word, then the command echo $FOO will print out word. If you then say BAR=$FOO-plunkity, the BAR variable will consist of word-plunkity. A similar think would happen had you instead said FOO=$FOO-plunkity, which is that FOO would then be a reference to the text word-plunkity. Do you see how that works? Thus, the command suggested, PATH=$PATH:/sw/bin, will set the PATH to be a string consisting of whatever $PATH is (i.e. your current path), a colon, and the string /sw/bin. It will not throw away your existing path. If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? That would be /etc/profile ~Kyle - -- It was luxuries like air conditioning that brought down the Roman Empire. With air conditioning their windows were shut, they couldn’t hear the barbarians coming. -- Garrison Keillor -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnUZNBkIOoMqOI14RAvPfAJ9gBxtJxjfGemlOl+4EllY61WyyZQCfTcC9 /7s+ttnYhH7uk3ahlkjXb1s= =PJjD -END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
On Sun, Jan 27, 2008 at 08:49:04PM CST, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: From: Peter Münster [EMAIL PROTECTED] On Sat, Jan 26 2008, [EMAIL PROTECTED] wrote: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Just after logging in, you can enter the command ls -alrut, that shows in the last lines, the files that have just been read. Among these files, there should be an initialisation file for your shell, for example .bashrc or .profile. In the end of this file, you can put the line PATH=$PATH:/sw/bin Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? Your ~/.bash_profile doesn't need any initial references to PATH, because your shell inherits the default value from its parent process. Without creating ~/.bash_profile, open a Terminal.app window and type echo $PATH to see the shell's default value. Going this way, I would go with Peter Münster's suggestion. If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? /sw indicates Fink. http://www.finkproject.org/doc/bundled/install-fast.php The last command runs a little script to help set up your Unix paths (and other things) for use with Fink. In most cases, it will run automatically, and prompt you for permission to make changes. If the script fails, you'll have to do things by hand. (If you need to do things by hand, and you are using csh or tcsh, you need to make sure that the command source /sw/bin/init.csh is executed during startup of your shell, either by .login, .cshrc, .tcshrc, or something else appropriate. If you are using bash or similar shells, the command you need is . /sw/bin/init.sh, and places where it might get executed include .bashrc and .profile.) So basically add the line . /sw/bin/init.sh into your ~/.profile or ~/.bash_profile init files. This should add /sw/bin to your PATH, and set up other Fink-related environment variables as well. -- Eugene
Re: Leopard Migration Hammered Mutt
Thanks for the thorough explanation. It helped me to grasp how the whole Path thing works. Since I would like to add /sw/bin to my /etc/profile I opened it, but only discovered: ___ # System-wide .profile for sh(1) if [ -x /usr/libexec/path_helper ]; then eval `/usr/libexec/path_helper -s` fi if [ ${BASH-no} != no ]; then [ -r /etc/bashrc ] . /etc/bashrc fi ___ This is not what I expected, and can't think of where I should add /sw/bin/ to my path. I appreciate your patience. Bill -- Original message -- From: Kyle Wheeler [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 02:49 AM, quoth [EMAIL PROTECTED]: Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? It adds it to the existing path. Your Path is stored as a colon-separated list of folders containing programs (e.g. /bin:/usr/bin:/sbin:/usr/sbin). The string $PATH is a reference to the existing path---if you say echo $PATH your shell will print out your current PATH, because that's the string referred to be the notation $PATH. When you tell your shell to set a variable name to be something, it performs a similar kind of expansion. For example, if you say FOO=$PATH, the variable FOO will now contain a copy of the contents of the variable $PATH. You can append things to variable expansions, because the shell operates almost entirely in terms of lines of text. For example, if you say FOO=word, then the command echo $FOO will print out word. If you then say BAR=$FOO-plunkity, the BAR variable will consist of word-plunkity. A similar think would happen had you instead said FOO=$FOO-plunkity, which is that FOO would then be a reference to the text word-plunkity. Do you see how that works? Thus, the command suggested, PATH=$PATH:/sw/bin, will set the PATH to be a string consisting of whatever $PATH is (i.e. your current path), a colon, and the string /sw/bin. It will not throw away your existing path. If it is possible I would rather add /sw/bin to the resource file where the rest of my Path is stored. How would I go about doing this? That would be /etc/profile ~Kyle - -- It was luxuries like air conditioning that brought down the Roman Empire. With air conditioning their windows were shut, they couldnât hear the barbarians coming. -- Garrison Keillor -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnUZNBkIOoMqOI14RAvPfAJ9gBxtJxjfGemlOl+4EllY61WyyZQCfTcC9 /7s+ttnYhH7uk3ahlkjXb1s= =PJjD -END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 03:31 AM, quoth [EMAIL PROTECTED]: Thanks for the thorough explanation. It helped me to grasp how the whole Path thing works. Since I would like to add /sw/bin to my /etc/profile I opened it, but only discovered: ___ # System-wide .profile for sh(1) if [ -x /usr/libexec/path_helper ]; then eval `/usr/libexec/path_helper -s` fi Hmmm. I don't have path_helper (I still use Tiger), but I'm willing to bet that it's got some hard-coded method of guessing your path. You have two options: either investigate path_helper and see what it's doing, or resign yourself to adding /sw/bin to your path in your own home directory. ~Kyle - -- Genius may have its limitations but stupidity is not thus handicapped. -- Elbert Hubbard -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnU7nBkIOoMqOI14RAviaAJ9YXQhzhDGqemQltboU3QEXZ4xP0QCg737a l5bRPYgS97t6v7NtHnqGVww= =M022 -END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
* Eugene [EMAIL PROTECTED] [2008-01-27 21:18 -0600]: So basically add the line . /sw/bin/init.sh into your ~/.profile or ~/.bash_profile init files. This should add /sw/bin to your PATH, and set up other Fink-related environment variables as well. All the explanations have been helpful. The only thing I'd add is an explanation that the line . /sw/bin/init.sh is a shortcut telling the shell to execute the script /sw/bin/init.sh (which has to have execute permission). The shell commands in init.sh get executed and change your path. The leading '.' is easy to miss, but it's a common usage in shell scripts. Breen -- Breen Mullins Menlo Park, California
Re: Leopard Migration Hammered Mutt
Here's what I was able to come up with about path_helper: ___ In Leopard, Apple has introduced a new mechanism for managing and maintaining your system path ($PATH). Previously (and in most current Linux environments) paths were managed by updating the PATH environment variable directly in either the system profile (/etc/profile) or your local profile (~/.bash_profile). Commonly you had entries like: export JAVA_HOME = /usr/lib/j2se/jdk1.5.0_13/ export PATH=$PATH:$JAVA_HOME/bin ... In Leopard, you no longer have to modify the profile to make adjustments to system paths. Instead, you can put a simple text file containing a path entry (or entries) into /etc/paths.d/. Each line in this file will be interpreted as a path and added automatically to the system path. littlesquare.com ___ Thanks for everyone's patient assistance. Bill -- Original message -- From: Kyle Wheeler [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 28 at 03:31 AM, quoth [EMAIL PROTECTED]: Thanks for the thorough explanation. It helped me to grasp how the whole Path thing works. Since I would like to add /sw/bin to my /etc/profile I opened it, but only discovered: ___ # System-wide .profile for sh(1) if [ -x /usr/libexec/path_helper ]; then eval `/usr/libexec/path_helper -s` fi Hmmm. I don't have path_helper (I still use Tiger), but I'm willing to bet that it's got some hard-coded method of guessing your path. You have two options: either investigate path_helper and see what it's doing, or resign yourself to adding /sw/bin to your path in your own home directory. ~Kyle - -- Genius may have its limitations but stupidity is not thus handicapped. -- Elbert Hubbard -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHnU7nBkIOoMqOI14RAviaAJ9YXQhzhDGqemQltboU3QEXZ4xP0QCg737a l5bRPYgS97t6v7NtHnqGVww= =M022 -END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
export shows: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Thanks, Bj ___ -- Original message -- From: Jonas Jacobsson [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Now I get the following when I attempt to evoke mutt: -bash: mutt: command not found Could someone walk me through this slowly? I have some unix background, but it's been quite a while since I've configured mutt. Is the directory where you have the mutt binary in your PATH variable? Type export and see. /jonas
Re: Leopard Migration Hammered Mutt
On Sat, Jan 26 2008, [EMAIL PROTECTED] wrote: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Hello, Just after logging in, you can enter the command ls -alrut, that shows in the last lines, the files that have just been read. Among these files, there should be an initialisation file for your shell, for example .bashrc or .profile. In the end of this file, you can put the line PATH=$PATH:/sw/bin (for a csh-like shell, the syntax is perhaps different...) Cheers, Peter -- http://pmrb.free.fr/contact/
Re: Leopard Migration Hammered Mutt
On Sat, Jan 26, 2008 at 05:13:11PM +, [EMAIL PROTECTED] wrote: export shows: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? put export PATH=${PATH}:/sw/bin in ~/.profile Marc
Re: Leopard Migration Hammered Mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, January 24 at 03:36 PM, quoth [EMAIL PROTECTED]: Recently, I switched from and older MacBook Pro to a new MacBook using Apple's Migration Assistant. All User issues went well, but unix issues did not fair so well. One of which was my mutt setup which had worked for years, and even many months under Leopard. Now I get the following when I attempt to evoke mutt: -bash: mutt: command not found Could someone walk me through this slowly? I have some unix background, but it's been quite a while since I've configured mutt. Looks like the problem is that mutt is no longer installed. You'll need to re-download the source (from www.mutt.org). Next, you'll need to uncompress it, such as with the command `tar -xzvf mutt-1.4.2.3.tar.gz`. Then you'll need to configure it; run `./configure --help` to get a listing of all the configure options (I don't know which ones you'll need), and then run `./configure` with all the options you want. Once that's done, run `make sudo make install`. (Sorry, that's not very slow, but it's a pretty open-ended question.) ~Kyle - -- In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- Douglas Adams -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFHmLlUBkIOoMqOI14RAmXfAKDNr7tD+olL8+HitXtTi+N7C/Ex7wCgtwR6 eH0M+cn9VRPIzAIbF/vjI5g= =YSgv -END PGP SIGNATURE-
Re: Leopard Migration Hammered Mutt
On Thu 24.Jan'08 at 15:36:11 +, [EMAIL PROTECTED] wrote: Recently, I switched from and older MacBook Pro to a new MacBook using Apple's Migration Assistant. All User issues went well, but unix issues did not fair so well. One of which was my mutt setup which had worked for years, and even many months under Leopard. Now I get the following when I attempt to evoke mutt: -bash: mutt: command not found Could someone walk me through this slowly? I have some unix background, but it's been quite a while since I've configured mutt. All this means is that mutt is somehow no longer in your path. Try: sudo /usr/libexec/locate.updatedb; locate mutt | grep bin
Re: Leopard Migration Hammered Mutt
On 2008-01-24 15:36:11 +, [EMAIL PROTECTED] wrote: Recently, I switched from and older MacBook Pro to a new MacBook using Apple's Migration Assistant. All User issues went well, but unix issues did not fair so well. One of which was my mutt setup which had worked for years, and even many months under Leopard. Now I get the following when I attempt to evoke mutt: -bash: mutt: command not found Could someone walk me through this slowly? I have some unix background, but it's been quite a while since I've configured mutt. That actually sounds as though your PATH environment variable is hosed now. -- Thomas Roessler [EMAIL PROTECTED]