鎵撳紑Bundle Editor
閫夊垯Show all
閫夊垯鏂囦歡澶?span class="hilite1" style="background-color: #ffff00;">TextMate錛堟垨鑰呴殢渚夸綘閫夊垯浠涔堬級
澧炲姞涓涓柊鐨則emplate‘openEncodedFile’錛堟垨鑰呴殢渚夸綘鑷繁鍛藉悕錛?br />
鍦═emplate data涓涓嬭瀹?br />
Extension錛氫腑 鐣欑┖
Command(s):
# open CocoaDialog’s file select menu
file=$(CocoaDialog fileselect \
--title "Open an encoded file" \
--with-directory $HOME/ \
)
# check for valid file
if [ -n "$file" ]; then
# open CocoaDialog's dropdown menu
# for more encodings add them to '--items'
# to list all possibile encodings use the Terminal with 'iconv -l'
res=$(CocoaDialog dropdown \
--title "Open an encoded file" \
--text "Choose the encoding:" \
??exit?onchange \
--button1 "Open" \
--button2 "Cancel" \
--items "BIG5" "EUC-TW" "GB2312" "SJIS" "EUC-JP" "KOI8-R" \
)
# if user canceled exit
[[ $( (tail -r <<<"$res") | tail -n1) == "2" ]] && \
exit_discard
res=$(tail -n1 <<<"$res")
# add more 'elif' according to '--items' if needed
if [ "$res" == 0 ]; then
ENC="BIG5"
elif [ "$res" == 1 ]; then
ENC="EUC-TW"
elif [ "$res" == 2 ]; then
ENC="GB2312"
elif [ "$res" == 3 ]; then
ENC="SJIS"
elif [ "$res" == 4 ]; then
ENC="EUC-JP"
elif [ "$res" == 5 ]; then
ENC="KOI8-R"
fi
# start conversion to UTF-8 and send the result as a new file back to TM
iconv -f "$ENC" -t utf-8 "$file" > "$TM_NEW_FILE"
fi
Output: Insert as Text - Activation: Key Equivalent shift+option+o (鎴戠殑寤鴻) - Scope: 鐣欑┖
]]>
Also you may want to check out this video in the Videocasts section of the handbook: Installing a Local Web Server on Mac OS X.
Download MAMP
(This will install Apache, MySQL, and PHP in one step.)
Find the latest version here: http://www.mamp.info/
Download and drag to Applications folder to install. Open MAMP and click "start servers," then "Open start page."
Download Drupal
Find the latest Drupal release here: http://drupal.org/.
Move the directory containing the Drupal files into the MAMP htdocs directory:
mv drupal-x.x.x/* drupal-x.x.x/.htaccess /Applications/MAMP/htdocs/yourdrupaldir
where yourdrupaldir is whatever you want the directory to be called.
Note: if you use Finder you may miss moving the .htaccess file which is necessary for clean URLs to work. It is generally best to download and unzip Drupal directly in the document root (default is htdocs) so you don't miss the .htaccess.
Create the Drupal database
To create a database for Drupal
- Go to the MAMP start page
- Click "phpMyAdmin"
- On the next page click "Databases"
- On the "Databases" page enter a name for your Drupal database in the "Create new database" field at the bottom of the page
- Select "utf8_general_ci" under the "Collation" drop-down (must be utf8!)
- Click "Create"
- Next you must create a user name with the privileges Drupal requires to use the new database
- Go back to the main phpMyAdmin page and click "Privileges"
- On the next page click "Add a new User".
- Fill out the "Login Information" form, making sure to change the "Host" field to "Local" and not leave it as "Any host" (for some reason Drupal will not be able to connect to your local database if you select "Any host")
- Leave the "None" radio button selected under the "Database for user" section, and under the "Global privileges" section leave everything unchecked
- Click "Go"
- On the next page scroll down to the "Database-specific privileges" section and select the new Drupal database you created from the dropdown
- Check the SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX and ALTER checkboxes and then click "Go".
You can also use a GUI such as Sequel Pro, just remember to use this as your Socket:
/Applications/MAMP/tmp/mysql/mysql.sock
Changing your password
The default username/password for your MySQL install is now root/root! For security purposes, it's always best to change this. If you're connected to the internet, this is a must.
When you are changing the default user/password from root/root, you need to do two things. Only the first is documented in the MAMP start page FAQ, but if you don't do the second then you get an error message when you try to access anything from the MAMP start page.
-
Use command line to change the password (as documented in the MAMP start page FAQ)
Open the terminal and type the following:
/Applications/MAMP/Library/bin/mysqladmin -u root -p password [NEWPASSWORD]It will ask for the current password after you hit enter. Once you have entered that, the MySQL password is changed.
-
Open a text editor and change the password in the three following files:
/Applications/MAMP/bin/phpMyAdmin-X.X.X/config.inc.phpFind the line that reads...
$cfg['Servers'][$i]['password'] = 'root';
...and change the value'root'to your new password, retaining the quotes./Applications/MAMP/bin/mamp/index.phpFind the line that reads...
$link = @mysql_connect(':/Applications/MAMP/tmp/mysql/mysql.sock', 'root', 'root');
...and change the last parameter to your new password./Applications/MAMP/bin/stopMysql.shReplace the
-prootwith your password. (If you don't change this one you can have zombie mysqld's running after you thought you stopped the server)
Optional: Adjust PHP's memory limit for scripts
By default, MAMP has the memory limit that a script can use set at 8MB, which is the PHP default. Looking at PHP's php.ini-recommended file, this memory limit is normally set at 128MB. To adjust this amount, open the php.ini file in a text editor and change the following line (approximately on line 232):
memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)
PHP.ini file locations:
/Applications/MAMP/conf/php4/php.ini/Applications/MAMP/conf/php5/php.ini
In MAMP PRO, don't alter the file directly since it will be recreated at each server start. Please edit the appropriate template (menu File > Edit template > ...) instead.
Even with larger PHP memory limits you can get timeout errors trying to import large Drupal databases into MySQL. These issues are discussed at length elsewhere with regards to the cache and views cache. Generally the solution is to empty the Drupal cache before importing/exporting databases to/from MySQL.
Connect Drupal
Navigate to http://localhost:8888/yourdrupaldir/install.php and fill in the installation fields using the information provided on the MAMP start page and the name you used for the database you created in step 3.
Start configuring Drupal!
Go to http://localhost:8888/yourdrupaldir/ and create the first account.
Continue with instructions in INSTALL.txt.
If you changed your MySQL username and password you will need to modify that in your local Drupal settings.php file as well.
Temporary Files Note:
By default the File System settings (admin/settings/file-system) will place the temporary files directory inside /Applications/MAMP/tmp/php which should be changed to something like files/tmp or sites/files/tmp to avoid later confusion.
Clean up your Localhost URL
If you would like to shorten your URL from "http://localhost:8888" to "http://localhost" follow these instructions:
- Open the MAMP application
- Click on "Preferences" and then "Ports"
- Change the Apache Port to 80 (the standard web server port)
]]>
“浣跨敤鍝鍘熷瀷璁捐宸ュ叿”澶ф鏄璁″笀闂茶亰鏃跺嚭鐜伴鐜囨渶楂樼殑璇濋涔嬩竴銆傛嵁 鎴戜簡瑙ｄ竴鑸互Visio鍜孭hotoshop涓轟富錛屼篃鏈変漢鐢‵lash鍜孭PT錛屾嵁涓涓柊鏉ョ殑鍚屼簨璇達紝浠栦滑鍏徃榪樼敤Excel銆傛垜瀹炲湪鎯充笉鍑虹敤Excel 鎬庝箞鐢誨浘錛屽搱鍝堛傛垜涓漢鏈鍠滄鐨勫伐鍏鋒槸OmniGraffle錛堝 涓嬪浘錛夛紝鑷粠鎴戠敤浜嗗畠浠ュ悗錛屽氨鍐嶄篃涓嶆兂鐢ㄥ叾瀹冨師鍨嬭璁¤蔣浠朵簡銆?/p>
棣栧厛鎴戝繀欏婚殕閲嶄粙緇嶄竴涓?a style="padding: 2px; margin: 0px; color: #336699;" target="_blank" >Omni Group榪欏鍙湁26涓漢鐨勫皬鍏徃錛屼粬浠漢鏁拌櫧灝戯紝浣嗗嵈浜у嚭 浜嗗儚OmniWeb銆?a style="padding: 2px; margin: 0px; color: #336699;" target="_blank" >OmniGraffle銆?a style="padding: 2px; margin: 0px; color: #336699;" target="_blank" >OmniPlan鍜?a style="padding: 2px; margin: 0px; color: #336699;" target="_blank" >OmniOutliner絳? 絳変竴緋誨垪娣卞彈鐢ㄦ埛嬈㈣繋鐨勭簿鍝佽蔣浠訛紝瀹炲姏緇濆涓嶅灝忚銆?/p>
浣犲彲浠ョ敤OmniGraffle錛堜互涓嬬畝縐癘G錛夋潵鍋氬緢澶氫簨鎯咃紝鎴戜竴鑸敤 瀹冩潵緇樺埗嫻佺▼鍥懼拰鐣岄潰鍘熷瀷銆傜浉姣旇緝浜嶸isio絳夊伐鍏鳳紝瀹冪殑浠ヤ笅鐗圭偣鍜屽姛鑳借浜虹埍涓嶉噴鎵嬶細
婕備寒鐨勭晫闈?/h3>
OG鐨勭晫闈㈠お婕備寒浜嗭紝鑷沖皯姣旂伆紿佺獊鐨刅isio濂界湅澶氫簡銆?#8220;緹庣殑灝辨槸濂? 鐨?#8221;錛堛婃渶浣寵璁?00緇嗗垯銆嬶級錛岀敤OG緇樺浘鐨勬椂鍊欒剳涓父甯稿厖婊＄伒鎰燂紝鑰屽鐫Visio鍒欏彧鎯沖敖蹇妸宸ヤ綔鍋氬畬銆?/p>
鑳借交鑰屾槗涓劇殑緇樺埗鍑烘紓浜殑鍥懼艦
OG鐨勫彲鐢ㄦу仛寰楀緢濂斤紝鍙互璁╀竴鍚嶆柊鎵嬪緢蹇湴緇樺埗鍑?#8220;鎯寵浜鴻垟涓鍙?#8221; 錛圝obs褰撳勾璇勪環OS X鐣岄潰鏃剁殑鍘熻瘽錛夌殑嫻佺▼鍥懼拰鍘熷瀷鍥俱傛垜浣跨敤瀹冩病澶氫箙灝卞畾涔変簡涓濂楄嚜宸辯殑鏍峰紡錛堝涓嬪浘錛夛紝騫跺湪欏圭洰涓噸鐢ㄣ?/p>
涓板瘜銆佺簿鑷寸殑妯℃澘錛圫tencil/Template錛?/h3>
闄や簡瀹樻柟鐨勬ā鏉垮錛?a style="padding: 2px; margin: 0px; color: #336699;" target="_blank" >Graffletopia緗戠珯鎻愪緵浜嗕紬澶氳璁＄簿緹庣殑妯℃澘銆備笉浠呮湁甯歌 鐨勭綉緇溿佽蔣浠舵祦紼嬨佺數璺瓑綾葷洰錛岀敋鑷寵繕鏈塙CD鐩稿叧鐨勬ā鏉匡紙濡備笅鍥撅級錛屼笉浠呮樉钁楁彁鍗囧伐浣滄晥鐜囷紝鑰屼笖涔熶嬌寰椾綘鐨勪駭鍑虹墿涓庝紬涓嶅悓錛?/p>
Information Architecture
User-Centered Design Activities
杈呭姪瀵歸綈鍜屽昂瀵歌皟鏁村姛鑳?/h3>
鍦ㄧ敤Visio鐨勬椂鍊欙紝浣犳湁澶氬皯嬈℃兂鎶婂涓厓绱犵殑澶у皬璋冩垚涓鏍風殑錛熷弽姝ｆ垜 姣忔鐢ㄥ畠緇樺埗嫻佺▼鍥劇殑鏃跺欓兘鎯寵繖涔堝仛錛屽彲姣忔閮介渶瑕佷竴涓釜鐨勮皟鏁達紝璁╀漢鏃犲彲濂堜綍銆傚湪OG閲岄潰錛岃繖鏄竴浠跺皬鑿滀竴紕熺殑浜嬪効銆傚綋浣犺皟鏁翠換浣曚竴涓厓绱犵殑澶у皬 鏃訛紝OG閮戒細鑷姩鎹曟崏騫舵樉紺洪〉闈㈠唴鎵鏈夊厓绱犵殑澶у皬錛屽茍杈呭姪榧犳爣鐨勮繍鍔紙閫氳繃紓佹ф劅錛夛紝浠ヤ究璁╄繖涓鍏冪礌鐨勫ぇ灝忓拰鍏跺畠浠諱綍涓涓綘鎯寵鐨勫厓绱犱繚鎸佷竴鑷達紙濡備笅 鍥撅級銆傚浜庢病鐢ㄨ繃OG鐨勪漢鏉ヨ錛岃繖鍚搗鏉ュ彲璋?#8220;闇囨捈”錛屾垜絎竴嬈″彂鐜拌繖鍔熻兘鏃舵縺鍔ㄤ笉宸詫紒姝ゅ錛屼繚鎸佷袱涓垨澶氫釜鍏冪礌鍦ㄦ按騫沖拰鍨傜洿鏂瑰悜涓婂榻愪篃鏄交鑰屾槗涓劇殑 浜嬶細杈呭姪綰挎誨湪浣犻渶瑕佺殑鏃跺欏嚭鐜幫紙濡備笅鍥撅級銆?/p>
杈呭姪灝哄璋冩暣
杈呭姪瀵歸綈
OG榪樻湁鏁頒笉娓呯殑濂界敤鐨勫皬鍔熻兘錛岃浜烘劅瑙夋棤鏃舵棤鍒諱笉澶勫湪榪欎釜杞歡鐨勫叧鎬涔嬩腑錛佹諱箣錛屽浜庤璁＄被杞歡鏉ヨ錛孫G緇濆鏄敤 鎴蜂綋楠岀殑鍏歌寖涔嬩綔銆?/p>
鏈鍚庯紝寰堜笉騫哥殑鏄紝榪欎釜杞歡鍙湁Mac鐗堛備笉榪囧鏋滀綘鍙湁PC鐨勮瘽錛屼笉濡? 鐪嬬湅榪欓噷 錛氾級
]]>
銆銆1銆佷笅杞組ySQL 5.x 鍙戣鐗?錛岃В鍘嬪茍瀹夎鏄犲儚涓殑涓や釜瀹夎鍖呮枃浠躲?/p>
銆銆a. mysql-5.x-osx10.6_x86_64.pkg 錛峬ysql 5.x 鏍囧噯鐗堝畨瑁?/p>
銆銆b. MySQLStartupItem.pkg錛峬ysql鍚姩欏圭洰錛屽彲浠ヤ笂浣犵殑鐢佃剳鍦ㄥ惎鍔ㄧ郴緇熸椂鑷姩榪愯mysql鏈嶅姟銆傚畠瀹夎鍦?Library /StartupItems/MySQL/錛屽鏋滀綘涓嶆兂緋葷粺鍚姩鏃惰繍琛宮ysql鏈嶅姟錛岃涓嶈瀹夎銆傚鏋滀綘鍦ㄥ畨瑁呭悗鍙堜笉鎯充嬌鐢紝璇峰垹闄?Library /StartupItems/MySQL/榪欎釜鐩綍銆?/p>
銆銆鍚姩mysql錛?/p>
銆銆2銆佸鏋滀綘宸茬粡瀹夎浜哅ySQLStartupItem.pkg錛岄噸鏂板惎鍔ㄧ數鑴戝嵆鍙?/p>
銆銆3銆佸鏋滀綘鏈夊畨瑁匨ySQLStartupItem.pkg鎴栬呬笉鎯沖惎鍔ㄧ數鑴戯紝榪愯錛氬簲鐢ㄧ▼搴忥紞瀹炵敤紼嬪簭錛嶇粓绔▼搴忥紝鍦ㄧ粓绔腑杈撳叆鍛戒護錛?/p>
銆銆sudo /Library/StartupItems/MySQL/MySQL start
銆銆鐒跺悗杈撳叆浣犵殑緋葷粺綆＄悊鍛樺瘑鐮侊紝濡傛灉娌℃湁璁懼畾瀵嗙爜灝辯洿鎺ュ洖杞︺?/p>
銆銆鍏抽棴mysql鏈嶅姟錛?/p>
銆銆緇堢涓緭鍏ュ懡浠わ細sudo /Library/StartupItems/MySQL/MySQL stop
銆銆鐒跺悗杈撳叆浣犵殑緋葷粺綆＄悊鍛樺瘑鐮侊紝濡傛灉娌℃湁璁懼畾瀵嗙爜灝辯洿鎺ュ洖杞︺?/p>
銆銆mysql root璐︽埛瀵嗙爜錛?/p>
銆銆mysql root瀵嗙爜鍒濆鍊兼槸絀恒傝繖鏍瘋櫧鐒舵病鏈夐棶棰樸備絾寰堜笉瀹夊叏銆傚緩璁綘鏇存敼root鐢ㄦ埛瀵嗙爜銆傛敞鎰忥細mysql root鐢ㄦ埛鍜岀郴緇熶腑鐨剅oot鐢ㄦ埛鏄笉涓鏍風殑銆傛槸瀹屽叏涓や釜涓嶅悓鐨勭敤鎴楓?/p>
銆銆鏇存敼mysql root瀵嗙爜璇峰湪緇堢涓緭鍏ュ懡浠わ細
銆銆/usr/local/mysql/bin/mysqladmin -u root password 鏂板瘑鐮?/p>
銆銆鍚屾椂浣犱篃鍙互闅忔椂浣跨敤榪欐潯鍛戒護鏇存敼浣犵殑瀵嗙爜銆?/p>
銆銆4銆佷笅杞絰鐗坢ysql鏁版嵁搴撶鐞嗗伐鍏?/p>
銆銆榪欐槸涓涓繍琛屽湪mac os
x緋葷粺涓殑mysql鏁版嵁搴撶鐞嗚蔣浠訛紝鏀寔鏈湴鍙婅繙紼嬫暟鎹簱綆＄悊銆傚茍涓旇繕鏄厤璐圭殑銆傝繖涓▼搴忕殑浼樼偣鏄畬鍏–GI鐣岄潰銆傚茍涓斿瘑鐮佹槸淇濆瓨鍦ㄦ湰鏈轟笂鐨勩傜浉瀵規瘮杈?
瀹夊叏銆?/p>
1.鎬庢牱璁劇疆mac涓殑榛樿java鐗堟湰鍛?錛?/strong>
鍏堢湅涓涓媘ac涓紝java閾炬帴鍒頒簡鍝噷錛?/font>
榪涘叆鍒扮浉搴旂殑鐩綍錛歝d /usr/bin
鏌ョ湅java閾炬帴鍒頒簡鍝噷錛歭s -l java
localhost:bin root# ls -l java
lrwxr-xr-x 1 root wheel 74 May 18 10:26 java ->
/System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java
鍙互鐪嬪埌java榪炴帴鍒頒簡current鐗堟湰銆傞偅涔堣繖涓埌搴曟槸浠涔堢増鏈憿錛熷叾瀹烇紝mac涓璫urrent鍙槸涓涓揩鎹鋒柟寮?
鑰屽凡錛屾槸涓轟簡鏂逛究璁劇疆榛樿java鐨勩?/font>
榪欎釜閾炬帴榪炲埌鍝噷錛岄粯璁ょ殑java灝辨槸鍝釜銆備絾鏄湪mac涓彲浠ヤ繚鎸佽繖涓猨ava閾炬帴涓嶅彉錛屽彧鏄敼鍙樹竴涓嬪綋鍓嶇殑 java鍗沖彲錛屼笅闈㈡槸姝ラ錛?/font>
1錛夋墦寮Finder 錛?鍗曞嚮妗岄潰鍦版鐨刦inder鍥炬爣鍗沖彲銆?/font>
2錛堿pplication-->Utilities-->Java-->Java Preferences
3)鐢辯浜屾鍙互鎵撳紑“Java Preferences”瀵硅瘽妗嗭紝閫変腑“General”tab銆傚湪涓嬮潰鐨?#8220;Java Application Runtime Settings”鍖烘妸闇瑕佺殑java鐗堟湰鎷栧姩鍒版渶欏剁鍗沖彲銆?/font>
鏈欏剁鐨刯ava灝辨槸褰撳墠錛坈urrent錛塲ava錛岃繖鏍峰湪鏀瑰彉榛樿java鐗堟湰鏃跺氨涓嶇敤鍦?usr/bin涓嬮噸 鏂拌緗甹ava閾炬帴錛岃屾槸鐩存帴鍦ㄨ繖閲屾妸闇瑕佺殑java鎷栧埌鏈涓婇潰灝辮銆?/font>
2.MAC涓殑javahome璁劇疆
鍦╳indows涓紝javahome鐨勫煎彧鏄彇鍒扮増鏈彿鐨勭洰褰曞嵆鍙紝浣嗘槸鍦╩ac涓湁紼嶅井鐨勪笉鍚岋紝瑕佸幓鍒扮増鏈彿鐩? 褰曚笅鐨凥ome鐩綍錛屽錛?/font>
JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
3. 鍦∕AC涓緗甁AVA_HOME鐜鍙橀噺
鐜鍙橀噺瑕佸啀etc鐩綍涓嬬殑profile鏂囦歡涓厤緗紝榪欐牱鎵嶆槸姘鎬箙鐨勯厤緗?br />
cd /etc
vi profile
杈撳叆濡備笅鍐呭錛?/font>
JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
export JAVA_HOME
淇濆瓨銆傜劧鍚庨噸鍚垨鑰呮敞閿錛屼嬌鐜鍙橀噺鐨勯厤緗搗浣滅敤銆?br />
榪欐牱javahome鐨勭幆澧冧究浠ら厤緗ソ浜嗐?/font>
鍚屾牱鐨勯亾鐞嗭紝鎴戜滑鍙互鍦╬rofile榪欎釜鏂囦歡涓繘琛孭ATH,CALSSPATH絳夌幆澧冨彉閲忕殑閰嶇疆銆?/font>
]]>
To change your path, you must edit the .profile file in your home
directory. If you are comfortable using the vi editor, you probably
don’t need to read any further. If not, then you can use
TextEdit to edit your .profile.
The default .profile is fairly short. The .profile is read when you open a Terminal window and each line is executed just like typing a command into the Terminal window. While this is handy because you can make any available command run whenever you drop to a shell, we’re concerned with changing an environment variable, PATH.
In your editor, find the line that starts with export PATH= and give it a look to make sure it doesn’t already contain the directory path you’re going to add. Sometimes the PATH variable can get lengthy, but chances are yours just has a few directories separated by colons, perhaps something like this:
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
There are a few things to note before making changes. The format of this line is important. The use of spaces in this command, or their lack, matters. In particular, there cannot be spaces around the equals sign or between any of the directories. If there are spaces in the directory name you want to add, you’ll need to escape the space by preceeding it with a "backslash or by putting the path in quotes (export PATH=”/path/here”).
The export= keyword in front of that line has a very specific purpose. Defining a variable without exporting it makes it available only to the current shell, not to any subsequent shells. You may think to yourself that you don’t plan to make any subsequent shells, but this happens whenever you run a shell script. If the PATH variable was not exported, when you run a shell script, the PATH would no longer exist and it is possible that the script would fail.
The $PATH at the end of the example above tacks the previous value of the variable (if it exists) onto the end of the PATH. By default, this will add ‘:/bin:/sbin:/usr/bin:/usr/sbin’ to the end of the PATH for you which is useful because most everything you run from the command line lives there.
So, to add a new directory to the path, simply add it to the existing PATH line in .profile being careful to separate it from other directories there with colons and careful not to introduce unwanted spaces (everything after the space will be ignored). For example, to add the directory /mightyq/bin to the PATH shown above, the line could become any of the following examples:
export PATH=/mightyq/bin:/opt/local/bin:/opt/local/sbin:$PATH
export PATH=/opt/local/bin:/mightyq/bin:/opt/local/sbin:$PATH
export PATH=/opt/local/bin:/opt/local/sbin:$PATH:/mightyq/bin
Note that in the third example the new directory is added to the end of the PATH. You have the ability to optimize the searches your shell will do on your behalf each time you run a command by organizing your PATH logically. Putting less frequently used or really massive directories later in the path may give you a little performance boost (although these days things are pretty fast, so you have to be a little anal to really enjoy this).
If you don’t need a directory in your path, you can reverse the process by deleting the unwanted directory still taking care to preserve the no spaces, colon separation rules.
One last note, to test the change you made, you can use the echo command, but you need to make the shell reload the .profile first. Assuming you are in your home directory (if not, running ‘cd’ without any options will take you there), run these commands:
. ./.profile
echo $PATH
The first is a neat little command in that it shows three uses or interpretations of the period in a single line. The first . is a shortcut to cause the shell to ’source’ or load the contents of the subsequent file as itself, in the manner that the shell uses when you login to a system or start a Terminal window. If you simply executed these commands like a shell script (bash .profile, for example) you would start a new shell, that shell would get the variable set, and at the end of running the .profile script, that new shell would cease to exist and the newly defined variables would be relegated to the missing sock universe.
The second period means the current working directory. It’s not compulsory in any way in this command, but it’s habit from explaining the dots to folks, so I type it all the time now. In this context, you could also use ~/.profile as ~ explicitly means your home directory.
The last dot causes the .profile to be hidden from view in a normal directory listing or Finder view. It doesn’t change the file in any other way, it just make it invisible and de-clutters your directories. To see hidden files, you can use ‘ls -a’ and you might be surprised by what you find.
]]>
When confronted with the task of editing your .profile file, there are
several options. For the seasoned veteran, editing this file is simply a
matter of dropping to a shell, editing in vi, and :wq’ing. There is
the pico editor which, for a command line editor, is a little friendlier
than vi. For the majority of users, editing a text file is warmer and
fuzzier using a GUI text editor like TextEdit.
The problem is that files starting with a period are hidden from listings in the Finder windows, so trying to find a hidden file to open using TextEdit will not get you very far. While many third party editors provide options for opening hidden files, if you don’t have one installed, you can easily open these hidden files using TextEdit which is a part of OS X.
To open your .profile file, for example, start the Terminal application (searching for ‘terminal’ using Spotlight and clicking on the Terminal application is an easy way to do this). Since Terminal will put you in your home directory by default and .profile is in your home directory, you can edit .profile simply by typing:
open .profile
If the file you want to edit is in another directory, you’ll need to cd into that directory first or specify the full path name in front of the filename.
The open command used above uses the same mechanism to open a file using a default application that the Finder does when clicking on a file. If for some reason the default application for the file you are trying to edit has changed to something that doesn’t work for editing, you can force open to use TextEdit by adding the -a option:
open -a TextEdit .profile
Make your changes to the file and save it and you’re done. One compulsory note of caution: hidden files are often hidden for a reason. They tend to hold configuration information that, if incorrectly changed, could cause one or more applications to misbehave. Tread lightly and make backups before changing.
]]>
榪涘叆NuFile鐨勯厤緗〉闈紝鎴戜滑鍙互璁劇疆鍦ㄥ彸閿彍鍗曚笂鍙互鏂板緩鍝簺鏂囦歡銆侼uFile鏀寔 鐨勬枃浠剁被鍨嬪緢澶氾紝鍖呮嫭鏂囨湰鏂囦歡銆丣ava鏂囦歡銆丳HP鍜孫ffice緋誨垪銆備綘榪樺彲浠ュ鍔犳柊鐨勬枃浠剁被鍨嬨?/p>
閰嶇疆瀹屾瘯鍚庯紝鎴戜滑鍦?a title="http://mac.linsheng.me/?p=253" target="_blank">Finder紿楀彛涓殑鍙抽敭鑿滃崟 涓紝灝卞彲浠ユ柊寤烘枃浠朵簡銆?/p>
]]>
鎵撳紑“緇堢”錛岃緭鍏ヤ互涓嬩唬鐮侊細
defaults write ~/Library/Preferences/com.apple.finder
AppleShowAllFiles -bool true
鐒跺悗閲嶅惎 Finder 鍗沖彲錛岄噸璧稦inder鏈夊縐嶆柟娉曪紝鏈綆鍗曠殑鏂規硶灝辨槸錛?/p>
鍚屾椂鎸変綇Control +
Option閿紝鐒跺悗鐐瑰嚮Dock宸﹁竟鐨凢inder鍥炬爣錛岃繖涓椂鍊欒彍鍗曟渶涓嬮潰灝變細鍑虹幇閲嶆柊鎵撳紑Finder鐨勯摼鎺ャ傚彟澶栬繕鍙互鍚屾椂鎸変綇Option
+ Command + ESC涓夐敭鎵撳紑寮哄埗閫鍑哄簲鐢ㄧ▼搴忓璇濇錛屽湪閲岄潰鍏抽棴Finder涔嬪悗錛孎inder浼氬湪鍏抽棴涔嬪悗鑷姩閲嶆柊鎵撳紑銆?/p>
鎭㈠闅愯棌鐨勪唬鐮侊細
defaults write ~/Library/Preferences/com.apple.finder
AppleShowAllFiles -bool false
]]>