Upgrade to Leopard mostly smooth, but has small glitch
I just installed Leopard on iMacG5 and everything went off very well. However when I restarted and looked at all the usual preferences, I launched the terminal and tried : [2008.07.03](02:06PM) -> [username] ~ $ ps aux | grep httpd username 305 0.0 0.0 599740 388 s001 S+ 2:07PM 0:00.00 grep httpd --> which showed that Apache was not running, so I tried : 2008.07.03](01:59PM) -> [username] ~ $ sudo launchctl load -w /Library/ LaunchDaemons/org.macports.apache2.plist Password: launchctl: Dubious ownership on file (skipping): /Library/ LaunchDaemons/org.macports.apache2.plist nothing found to load --> And that didn't work so well, so I tried : [2008.07.03](02:07PM) -> [username] ~ $ sudo /opt/local/apache2/bin/ apachectl -k start Password: /opt/local/apache2/bin/apachectl: line 70: ulimit: open files: cannot modify limit: Invalid argument --> which showed an error on line 70 of apachectl --> but it tried to see if it launched anyway, and it did as it shows below [2008.07.03](02:07PM) -> [username] ~ $ ps aux | grep httpd username 320 0.0 0.1 97264 1204 ?? S 2:07PM 0:00.00 /opt/local/apache2/bin/httpd -k start username 319 0.0 0.1 97264 1204 ?? S 2:07PM 0:00.00 /opt/local/apache2/bin/httpd -k start username 318 0.0 0.1 97264 1204 ?? S 2:07PM 0:00.00 /opt/local/apache2/bin/httpd -k start username 317 0.0 0.1 97264 1204 ?? S 2:07PM 0:00.00 /opt/local/apache2/bin/httpd -k start username 316 0.0 0.1 97264 1204 ?? S 2:07PM 0:00.00 /opt/local/apache2/bin/httpd -k start root 315 0.0 0.0 97164 888 ?? S 2:07PM 0:00.00 /opt/local/apache2/bin/httpd -k start root 312 0.0 0.3 97264 7232 ?? Ss 2:07PM 0:00.34 /opt/local/apache2/bin/httpd -k start username 322 0.0 0.0 599740 384 s001 R+ 2:08PM 0:00.00 grep httpd [2008.07.03](02:08PM) -> [username] ~ $ Any ideas why I got : ( 1 ) launchctl: Dubious ownership on file (skipping): /Library/ LaunchDaemons/org.macports.apache2.plist nothing found to load ( 2 ) /opt/local/apache2/bin/apachectl: line 70: ulimit: open files: cannot modify limit: Invalid argument --> Here's what I found : [2008.07.03](02:08PM) -> [username] ~ $ open -a ~/Applications/ BBEdit.app /opt/local/apache2/bin/apachectl # LINE 59 # Set this variable to a command that increases the maximum # number of file descriptors allowed per child process. This is # critical for configurations that use many file descriptors, # such as mass vhosting, or a multithreaded server. ULIMIT_MAX_FILES="ulimit -S -n `ulimit -H -n`" # -------------------- -------------------- # |||||||||||||||||||| END CONFIGURATION SECTION |||||||||||||||||||| # Set the maximum number of file descriptors allowed per child process. if [ "x$ULIMIT_MAX_FILES" != "x" ] ; then $ULIMIT_MAX_FILES fi # LINE 72 Bill Hernandez Plano, Texas
On Mar 7, 2008, at 14:31, Bill Hernandez wrote:
I just installed Leopard on iMacG5 and everything went off very well.
However when I restarted and looked at all the usual preferences, I launched the terminal and tried :
Did I understand correctly that you had Tiger, installed MacPorts and several ports, and now upgraded to Leopard and are trying to continue using the ports that were already installed? If so, I can't recommend that. I suggest reinstalling MacPorts and your ports from scratch. Ports may need to build differently on each version of Mac OS X.
On Fri, Mar 7, 2008 at 7:11 PM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Mar 7, 2008, at 14:31, Bill Hernandez wrote:
I just installed Leopard on iMacG5 and everything went off very well.
However when I restarted and looked at all the usual preferences, I launched the terminal and tried :
Did I understand correctly that you had Tiger, installed MacPorts and several ports, and now upgraded to Leopard and are trying to continue using the ports that were already installed? If so, I can't recommend that. I suggest reinstalling MacPorts and your ports from scratch. Ports may need to build differently on each version of Mac OS X.
That seems really cumbersome. If it is necessary, any way that the MacPorts team could whip up a script to migrate ports to a new OS release? or will a simple for loop (for i in `port installed`; do . . . ) do it? But on to the OP's question, httpd is running? What do those lines do if you run them in the Terminal? % export ULIMIT_MAX_FILES="ulimit -S -n `ulimit -H -n`" % echo $ULIMIT_MAX_FILES and as a hint, if you install BBedit's command line tools, you can simply type "edit <filename>" instead of all that other stuff. Or use TextWrangler, for those who are short of coin. It has the same facility. -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
On Mar 8, 2008, at 01:35, paul beard wrote:
On Fri, Mar 7, 2008 at 7:11 PM, Ryan Schmidt wrote:
On Mar 7, 2008, at 14:31, Bill Hernandez wrote:
I just installed Leopard on iMacG5 and everything went off very well.
However when I restarted and looked at all the usual preferences, I launched the terminal and tried :
Did I understand correctly that you had Tiger, installed MacPorts and several ports, and now upgraded to Leopard and are trying to continue using the ports that were already installed? If so, I can't recommend that. I suggest reinstalling MacPorts and your ports from scratch. Ports may need to build differently on each version of Mac OS X.
That seems really cumbersome. If it is necessary, any way that the MacPorts team could whip up a script to migrate ports to a new OS release?
or will a simple for loop (for i in `port installed`; do . . . ) do it?
I feel it's necessary. Consider all the ports you currently have installed that have a "+darwin_8" variant. If you upgrade to Leopard, your OS is now Darwin 9, but you still have +darwin_8 variants. If you upgrade those ports, they'll still keep the +darwin_8 variants as long as those ports still define those variants. Also, if those ports define a +darwin_9 variant, during upgrade, you'll acquire that as well, so now your port will be installed with "+darwin_8+darwin_9" which is not correct and could cause unexpected behavior. Consider also the case of the php5 port. The +apache variant, as it is currently written, uses the Apache 1.3 server Apple has in Mac OS X 10.4 and earlier. If you upgrade to Leopard, in which Apple's Apache is now version 2, php5 won't work anymore, because Apache modules need to be recompiled to work with a different Apache version. To generalize, there may be variants that can only be used on certain OS versions, or that work differently on different OS versions, so ports should be recompiled when you upgrade to a new major OS release. MacPorts itself may behave differently. For example, there was talk about using new facilities in Leopard for modifying the user's PATH. That specific example won't apply since it was ultimately decided not to use those facilities. But consider the case of upgrading from Panther to Tiger. If you had any ports installed that need startupitems, you should rebuild those ports so they'll be turned into launchd plists instead. One could probably script such a reinstall, but I'm not going to right now. The steps would be: get the name and variants of each installed port, and whether or not it's active. Uninstall each port (optional?). Move aside all directories where MacPorts has installed things (/opt/local, /Library/Tcl/macports1.0, /Applications/ MacPorts). Install MacPorts from the appropriate disk image for your new OS. Install each of your previous ports with the right variants, deactivating those ports that were originally inactive.
and as a hint, if you install BBedit's command line tools, you can simply type "edit <filename>" instead of all that other stuff. Or use TextWrangler, for those who are short of coin. It has the same facility.
BBEdit's command line tools are called "bbedit" and "bbdiff". TextWrangler's equivalent command line tools are called "edit" and "twdiff".
Ryan Schmidt wrote:
and as a hint, if you install BBedit's command line tools, you can simply type "edit <filename>" instead of all that other stuff. Or use TextWrangler, for those who are short of coin. It has the same facility.
BBEdit's command line tools are called "bbedit" and "bbdiff".
TextWrangler's equivalent command line tools are called "edit" and "twdiff".
These also works with the EDITOR variable, with .e.g. MacPorts. export EDITOR=edit port edit MacPorts --anders
paul beard wrote:
That seems really cumbersome. If it is necessary, any way that the MacPorts team could whip up a script to migrate ports to a new OS release?
The easiest way would be if `port upgrade' removes the installed platform variant and replaces it with the current one. Or will that have any other consequences? Rainer
On Mar 8, 2008, at 02:48, Rainer Müller wrote:
paul beard wrote:
That seems really cumbersome. If it is necessary, any way that the MacPorts team could whip up a script to migrate ports to a new OS release?
The easiest way would be if `port upgrade' removes the installed platform variant and replaces it with the current one. Or will that have any other consequences?
That would be an improvement.
On Mar 8, 2008, at 4:30 AM, Ryan Schmidt wrote:
On Mar 8, 2008, at 02:48, Rainer Müller wrote:
paul beard wrote:
That seems really cumbersome. If it is necessary, any way that the MacPorts team could whip up a script to migrate ports to a new OS release?
The easiest way would be if `port upgrade' removes the installed platform variant and replaces it with the current one. Or will that have any other consequences?
That would be an improvement.
sudo port -u upgrade foo does exactly that doesnt it? William Davis frstanATbellsouthDOTnet Mac OS X.5.2 Darwin 9.2.0 XQuartz 2.1.4 - (xorg-server 1.3.0-apple10) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non
William Davis wrote:
The easiest way would be if `port upgrade' removes the installed platform variant and replaces it with the current one. Or will that have any other consequences?
That would be an improvement.
sudo port -u upgrade foo
does exactly that doesnt it?
No. It tries to reinstall the same variant set as installed. So if +darwin_8 was chosen automatically on the initial install, upgrade chooses +darwin_8 again, even if you are now on darwin_9. Rainer
On Mar 8, 2008, at 1:35 AM, paul beard wrote:
and as a hint, if you install BBedit's command line tools, you can simply type "edit <filename>" instead of all that other stuff. Or use TextWrangler, for those who are short of coin. It has the same facility.
I included two very handy scripts for Leopard at the bottom, if you don't like them, please ignore them. "edit <filename>" didn't work for me using a shell worksheet port installed > ~/installed_ports.txt edit ~/installed_ports.txt -bash: line 4: edit: command not found instead of using : open -a /Applications/BBEdit.app ~/installed_ports.txt I should have used an existing shell script # shell script : bh_open # ------------------------------------------------ #!/bin/bash if [ -a /Applications/BBEdit.app ]; then open -a /Applications/BBEdit.app $1 elif [ -a ~/Applications/BBEdit.app ]; then open -a ~/Applications/BBEdit.app $1 else open -a /Applications/TextEdit.app $1 fi # ------------------------------------------------ and just call it from the Terminal : bh_open ~/installed_ports.txt The following ports are currently installed: apache2 @2.2.4_1 (active) apr @1.2.9_0 (active) apr-util @1.2.8_2 (active) bison @2.3_0 (active) bzip2 @1.0.4_1 (active) curl @7.16.4_0+darwin_8 (active) cyrus-sasl2 @2.1.21_0+kerberos (active) db44 @4.4.20_1+darwin_8 (active) expat @2.0.1_0 (active) fontconfig @2.4.2_0+macosx (active) freetype @2.3.5_0 (active) gd2 @2.0.35_0 (active) gettext @0.16.1_0 (active) jpeg @6b_2 (active) libiconv @1.11_4+darwin_8 (active) libmcrypt @2.5.8_0+darwin_8 (active) libpng @1.2.18_0+darwin_8 (active) libtool @1.5.24_0 (active) libxml2 @2.6.28_1 (active) libxslt @1.1.20_0 (active) m4 @1.4.9_0 (active) mhash @0.9.9_0+darwin_8 (active) mysql5 @5.0.45_0+darwin_8+server (active) ncurses @5.6_0+darwin_8 (active) ncursesw @5.6_0+darwin_8 (active) openldap @2.3.35_0 (active) openssl @0.9.8e_0+darwin_8 (active) pcre @7.2_0+utf8 (active) perl5.8 @5.8.8_0+darwin_8 (active) php5 @5.2.3_0+apache2+darwin_8+fastcgi+ipc+macosx+mysql5+pcntl+pear +postgresql+sqlite+tidy (active) pkgconfig @0.22_0 (active) postgresql82 @8.2.4_0+darwin_8 (active) postgresql82-server @8.2.4_0 (active) readline @5.2.001_0 (active) rpl @1.4.0_0 (active) sqlite3 @3.4.2_0+darwin_8 (active) tidy @20051026_0+darwin_8 (active) tiff @3.8.2_0+darwin_8 (active) zlib @1.2.3_1 (active) Even though this did not launch Apache : 2008.07.03](01:59PM) -> [username] ~ $ sudo launchctl load -w /Library/ LaunchDaemons/org.macports.apache2.plist Password: launchctl: Dubious ownership on file (skipping): /Library/ LaunchDaemons/org.macports.apache2.plist nothing found to load --> And that didn't work so well, so I tried : [2008.07.03](02:07PM) -> [username] ~ $ sudo /opt/local/apache2/bin/ apachectl -k start Password: /opt/local/apache2/bin/apachectl: line 70: ulimit: open files: cannot modify limit: Invalid argument Even though there was an error on line 70, it launched Apache and php seemed to be working fine, I am sure you are absolutely correct, and at some point I will begin having problems, so you are right, I will bite the bullet and delete the /opt directory, and start over again. Thanks very much to all who responded. There were a few of things I did not like about Leopard : ( 1 ) Blue/White background stripes in the Finder window (fixed in script finder_utility.scpt) ( 2 ) Translucent Menu Bar (fixed in script finder_utility.scpt) ( 3 ) Borderless Windows ( 4 ) Inability to close the Sidebar without closing the Toolbar (fixed in script stack_windows.scpt) ( 5 ) Lost hierarchical menus on {folders. disks} on the Dock (fixed in OS X upgrade 10.5.2) I know I will probably be criticized for posting these but they have turned out very helpful for me, and hopefully they will help someone else on the board. The problem with the sidebar causes the windows to take up too much room, causing a lot of clutter if you are working with several open windows. The second script somewhat addresses the problem. I hope this doesn't make anyone angry that I contributed these, even though it is not the right board... This script takes care of items ( 1 ) and ( 2 ) -- +---------+---------+---------+---------+---------+--------- +---------+---------+ on bh_a_script_title() (* Author : Bill Hernandez ProjectNo : 407 ProjectName : finder_utility (Leopard) FileName : finder_utility.scpt FilePath : ~/user_scripts/user/projects/finder/finder_utility.scpt Version : 1.0.0 VersionDate : [ 2008_03_08 ] Standardized : [ 2008_03_08 ] Created : 3/8/08 ( 9:14 PM ) Updated : Saturday, March 8, 2008 ( 9:15 PM ) *) end bh_a_script_title -- +---------+---------+---------+---------+---------+--------- +---------+---------+---------+---------+ property user_name : "" -- +---------+---------+---------+---------+---------+--------- +---------+---------+---------+---------+ on run set aList to {} copy "( 1 ) Show Stripes in List View ?" to the end of aList copy "( 2 ) Make the menu bar solid white, or solid gray, instead of translucent ?" to the end of aList set aDefault to item 2 of aList set aResult to choose from list aList default items aDefault if (aResult is not equal to false) then set which_choice to item 1 of aResult end if if which_choice is (item 1 of aList) then toggle_list_view_stripes() else if which_choice is (item 2 of aList) then toggle_menubar_background() end if end run -- +---------+---------+---------+---------+---------+--------- +---------+---------+---------+---------+ on toggle_list_view_stripes() set user_pwd to "" set b1 to "Cancel" set b2 to "Show Stripes" set b3 to "Don't Show Stripes" try set aResult to display dialog "OS X - Leopard" & return & "Show Stripes in List View ?" buttons {b1, b2, b3} default button {b3} on error -- DO NOTHING, USER CANCELLED end try set which_choice to button returned of aResult if which_choice is b3 then do shell script "defaults write com.apple.finder FXListViewStripes - bool FALSE; killall Finder" else do shell script "defaults write com.apple.finder FXListViewStripes - bool TRUE; killall Finder" end if end toggle_list_view_stripes -- +---------+---------+---------+---------+---------+--------- +---------+---------+---------+---------+ on toggle_menubar_background() set user_pwd to "" set aList to {} copy "( 1 ) Make the menu bar solid white ?" to the end of aList copy "( 2 ) Make the menu bar solid gray ?" to the end of aList copy "( 3 ) Make the menu translucent ?" to the end of aList set aDefault to item 1 of aList set aResult to choose from list aList default items aDefault if (aResult is not equal to false) then set which_choice to item 1 of aResult end if try set the_result to display dialog "Please enter your short login name ?" default answer user_name set user_name to text returned of the_result as string try set the_result to display dialog "Please enter your admin password ?" default answer user_pwd with hidden answer set user_pwd to text returned of the_result as string on error set user_pwd to "" end try on error set user_name to "" end try if ((user_name is not equal to "") and (user_name is not equal to "") as string) then if which_choice is (item 1 of aList) then --> White Menubar BackGround set RunCmd to "sudo defaults write /System/Library/LaunchDaemons/ com.apple.WindowServer 'EnvironmentVariables' -dict-add 'CI_NO_BACKGROUND_IMAGE' 1" else if which_choice is (item 2 of aList) then --> Gray Menubar BackGround set RunCmd to "sudo defaults write /System/Library/LaunchDaemons/ com.apple.WindowServer 'EnvironmentVariables' -dict-add 'CI_NO_BACKGROUND_IMAGE' 0" else --> Translucent Menubar BackGround set RunCmd to "sudo defaults delete /System/Library/LaunchDaemons/ com.apple.WindowServer 'EnvironmentVariables'" end if try do shell script RunCmd user name user_name password user_pwd with administrator privileges display dialog "You need to restart the computer for the change in the MenuBar background color to take effect..." on error display dialog "There was an error setting the MenuBar background color..." end try end if end toggle_menubar_background -- +---------+---------+---------+---------+---------+--------- +---------+---------+---------+---------+ This script takes care of items ( 1 ) and ( 2 ) -- +---------+---------+---------+---------+---------+--------- +---------+---------+ on bh_a_script_title() (* Author : Bill Hernandez ProjectNo : 408 ProjectName : stack_windows (Leopard) FileName : stack_windows.scpt FilePath : ~/user_scripts/user/projects/finder/stack_windows.scpt Version : 1.0.0 VersionDate : [ 2008_03_08 ] Standardized : [ 2008_03_08 ] Created : 3/6/08 ( 9:06 AM ) Updated : Saturday, March 8, 2008 ( 9:34 PM ) Note : Assign a Quickey to launch this script anytime the desktop get cluttered *) end bh_a_script_title -- +---------+---------+---------+---------+---------+--------- +---------+---------+ on run tell application "Finder" set windows_per_row to 4 set max_window_width to 330 set show_toobar to false if (show_toobar) then set w_header_height to 80 else set w_header_height to 24 end if set menubar_height to 46 set dock_height to 60 set left_spacer to 20 set right_spacer to 80 set col_spacer to 4 set screen_bounds to bounds of window of desktop set screen_width to item 3 of screen_bounds set screen_height to item 4 of screen_bounds set aWindows to get every window set no_of_windows to count of aWindows set no_of_rows to no_of_windows / windows_per_row set nor_mod to (no_of_rows mod windows_per_row) mod 1 set no_of_rows to no_of_windows div windows_per_row if (nor_mod > 0) then set no_of_rows to no_of_rows + 1 end if set w_height to (screen_height - menubar_height - dock_height) - (w_header_height * no_of_rows) as integer set w_width to ((screen_width - left_spacer - right_spacer) / windows_per_row) as integer if (w_width > max_window_width) then set w_width to max_window_width end if set col_no to 0 set row_no to 0 repeat with w_ref in aWindows set col_no to col_no + 1 if (col_no > windows_per_row) then set col_no to 1 set row_no to row_no + 1 end if set w_left to left_spacer + ((col_no - 1) * w_width) set w_top to (menubar_height + (row_no * w_header_height)) set w_right to w_left + w_width - col_spacer set w_bottom to w_top + w_height set w_props to properties of w_ref -- set sidebar width of w_ref to 0 set properties of w_ref to {sidebar width:0} -- DOES NOT WORK EITHER set properties of w_ref to {toolbar visible:show_toobar} -- ALL THREE OF THESE COULD BE JOINED TOGETHER set properties of w_ref to {current view:list view} set properties of w_ref to {bounds:{w_left, w_top, w_right, w_bottom}} select w_ref set x to col_no end repeat end tell end run -- +---------+---------+---------+---------+---------+--------- +---------+---------+ Bill Hernandez ms@mac-specialist.com
On Mar 8, 2008, at 7:48 PM, Bill Hernandez wrote:
There were a few of things I did not like about Leopard :
( 2 ) Translucent Menu Bar (fixed in script finder_utility.scpt)
You don't need a script. You just need to update to 10.5.2 and use the Desktop preference pane. Since emacs is also the only editor anyone could ever need, I don't understand the need for the other scripts.. :-) - Jordan
On 08Mar2008 21:48, Bill Hernandez <ms@mac-specialist.com> wrote: [...snip...] | I should have used an existing shell script | | # shell script : bh_open | # ------------------------------------------------ | #!/bin/bash | | if [ -a /Applications/BBEdit.app ]; then | open -a /Applications/BBEdit.app $1 | elif [ -a ~/Applications/BBEdit.app ]; then | open -a ~/Applications/BBEdit.app $1 | else | open -a /Applications/TextEdit.app $1 | fi | # ------------------------------------------------ [...snip...] Surely this does not work? "-a" is "and". Do you mean "-f" or "-x" perhaps? Personally I'd have just looped over the choices. And you should really quote the $1, otherwise a filename with spaces in it will bite you one day: #!/bin/sh for app in /Applications/BBEdit.app \ $HOME/Applications/BBEdit.app \ /Applications/TextEdit.app do [ -x "$app" ] && exec open -a "$app" "$1" done echo "$0: can't find something with which to open $1" >&2 exit 1 Cheers, -- Cameron Simpson <cs@zip.com.au> DoD#743 http://www.cskk.ezoshosting.com/cs/ Everybody talks about the weather, but does anybody *do* anything about it? - perry@dsinc.com (Jim Perry)
On Mar 8, 2008, at 11:01 PM, Jordan K. Hubbard wrote:
You don't need a script. You just need to update to 10.5.2 and use the Desktop preference pane.
Thanks, I couldn't find any info on how to fix the problem. It's ok anyway, with the script there are three choices, {white, gray, translucent}
Since emacs is also the only editor anyone could ever need, I don't understand the need for the other scripts.. :-)
I used emacs until I discovered BBEdit, and emacs became but page in history... BTW : ( 1 ) have any idea what preference I need to set to get the window borders back ? I hate border-less windows... ( 2 ) what can be done to set the {sidebar width : 0} without having to hide (losing) the Toolbar ? I like having the toolbar, but I hate being forced to have the sidebar open. When you have several windows (12-15) open, especially if you are trying to compare them side by side, having the sidebar open forces the window to be inconveniently larger. People get used to working a certain way for several years, then someone arbitrarily decides that after years of having a particular option available to the user, they are just not going to let them have it anymore. What skin is it off the programmer's nose if I want to close the sidebar, to me it's a nuisance. A bully approach, wouldn't you say ? I think major changes in the way one works should be handled as a preference. The computer is supposed to be a tool to help us, and removing backward compatibility is just wrong, especially in something like the sidebar which does not affect the operating system, but certainly affects the way I work... I am sure as they sat around the table while trying to decide what features to include in Leopard, someone decided that "The user is too stupid to come out of the rain, so we'll protect them from themselves, and prevent them from closing the sidebar. That will improve the user experience !" You can tell I hate to be bullied ! Bill Hernandez ms@mac-specialist.com
On Sat, Mar 8, 2008 at 7:48 PM, Bill Hernandez <ms@mac-specialist.com> wrote:
On Mar 8, 2008, at 1:35 AM, paul beard wrote:
and as a hint, if you install BBedit's command line tools, you can simply type "edit <filename>" instead of all that other stuff. Or use TextWrangler, for those who are short of coin. It has the same facility.
I included two very handy scripts for Leopard at the bottom, if you don't like them, please ignore them.
"edit <filename>" didn't work for me using a shell worksheet
port installed > ~/installed_ports.txt edit ~/installed_ports.txt -bash: line 4: edit: command not found
Did you install the command line tools when you installed BBEdit or TextWrangler? [/Users/paul]:: edit -h Usage: edit [-bcehlpuvVw] [+<line number>] ... +<line number> -b, --background --clean -c, --create -e, --encoding <encoding> -h, --help -l, --launch -p, --print --resume -t, --pipe-title -u, --create-unix -v, --version --view-top -V, --short-version -w, --wait --front-window --new-window --separate-windows emacs is all very well if you learned it when you were of young and supple mind, but I am older than jkh and never did master emacs when I had the chance. -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
On Mar 8, 2008, at 11:01 PM, Jordan K. Hubbard wrote:
Since emacs is also the only editor anyone could ever need, I don't understand the need for the other scripts.. :-)
This is what I meant to say : I used emacs until I discovered BBEdit, then emacs became but a faint page in history... Bill Hernandez ms@mac-specialist.com _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
On Mar 9, 2008, at 1:54 AM, paul beard wrote:
Did you install the command line tools when you installed BBEdit or TextWrangler?
I did, but in the past when I've installed a new major version of the OS, I've reformatted the drive and installed all the latest versions of the applications. For some reason this time, the installer didn't ask me if I wanted to archive the old OS, it appears to have installed right over Tiger. This made me think that perhaps the changes to the core OS, other than the interface were probably not that significant, and that is why I tried to run apache without having to install all new ports. What Ryan said makes sense about the Darwin 9 stuff, so tomorrow I will delete the /opt directory and start over. I've got a shell script that installs everything for me, moves files around, creates aliases, and does some other things, and this will give me an opportunity to fine tune the small items that need refining. I will try to re-install the command line tools Bill Hernandez ms@mac-specialist.com
participants (8)
-
Anders F Björklund
-
Bill Hernandez
-
Cameron Simpson
-
Jordan K. Hubbard
-
paul beard
-
Rainer Müller
-
Ryan Schmidt
-
William Davis