#teminal

Без лишних предисловий просто расскажу о функциях bash profile, которыми сам пользуюсь.

Изменение громкости

Для того, чтобы изменить громкость звука в macOS с помощью терминала, добавьте в ~/.profile (или ~/.bash_profile, в зависимости от того, что у вас там есть) такую функцию:

function vl() { osascript -e "set Volume $1" }

Теперь можно изменять громкость системного звука с помощью команды vl и параметра от 0 до 7. Причем можно задавать промежуточные значения, например 3.5 (50% громкости)

Включение-выключение VPN (IPSec)

Если вы пользуетесь VPN по протоколу IPSec, то с помощью этой функции вы сможете включать и выключать настроенный профиль (предполагается, что профиль VPN уже есть у вас в системе), а также узнать статус подключения.

function uvpn() { INFO=`scutil --nc list` status=$(echo "${INFO}" | awk '{if (NR!=1) print$2}' | sed -e 's/[()]//g') vpnName=$(echo "${INFO}" | awk 'BEGIN {ORS=" "}; {if (NR!=1) for(i = 5;i <= NF-1; i++) print$i}' | sed -e 's/"//g') vpnID=$(echo "${INFO}" | awk '{if (NR!=1) print$3}') case "$1" in start) echo "started $vpnName" scutil --nc $1 $vpnID;; stop) echo "stopping $vpnName" scutil --nc $1 $vpnID status=$(scutil --nc list | awk '{if (NR!=1) print$2}' | sed -e 's/[()]//g') sleep .5 echo VPN is $status;; *) echo VPN is $status;; esac }

Запуск uvpn без параметров покажет состояние подключения. Соответственно uvpn start и uvpn stop довольно self-explanatory. К сожалению, если у вас IKEv2 VPN, этот скрипт не поможет. В интернете есть для этого решение с помощью Apple Script, но я его не тестировал.

Управление охлаждением процессора

Для работы этого скрипта вам понадобится установить программу SMCFanControl. Несмотря на то, что данная улитита старая и проверенная, разработчик напоминает, что программу стоит запускать на свой страх и риск, и что манипуляции с вентиляторами процессора могут привести к выходу компьютера из строя. Короче, я предупредил.

alias smc="/Applications/smcFanControl.app/Contents/Resources/smc" function fan() { RPM=$2 FANSTOTAL=$(smc -f | awk 'BEGIN { FS=": " } ; {print $2}' | head -1) case "$1" in auto|-a|reset|-r) smc -k "FS! " -w 0000 echo Fan speed is set to auto mode ;; set|-s) echo Total fans amount: $FANSTOTAL for i in $(seq 1 $FANSTOTAL); do smc -k "FS! " -w 0003 smc -k F`expr $i - 1`Tg -w `printf '%x\n' $(expr $RPM \* 4)` done echo Fan speed is set to $RPM ;; *) smc -f;; esac }

Описание:

fan set 3500 установит скорость 3500 RPM для каждого вентилятора в системе.

fan auto вернет режим работы вентиляторов по умолчанию

fan с любыми другими параметрами или с пустым аргументом просто покажет информацию о текущем состоянии вентиляторов.

Кстати, вместо функции в bash profile, можно добавить скрипт в /usr/local/bin.

vim /usr/local/bin/fanfun

#!/bin/bash set -e FANSTOTAL=$(smc -f | awk 'BEGIN { FS=": " } ; {print $2}' | head -1) RPM=$2 case "$1" in auto|-a|reset|-r) smc -k "FS! " -w 0000 echo Fan speed is set to auto mode;; set|-s) echo Total fans amount: $FANSTOTAL for i in $(seq 1 $FANSTOTAL); do smc -k "FS! " -w 0003 smc -k F`expr $i - 1`Tg -w `printf '%x\n' $(expr $RPM \* 4)` done echo Fan speed is set to $RPM ;; help|-h) echo "----------------------" echo "'fan set <number>' or 'fan -s <number>' to force fan speed" echo "'fan reset' or 'fan -r' to reset fan status to default" echo "----------------------" smc -f;; *) smc -f;; esac

В этом случае надо будет сделать симлинк на программу smc.

ln -s /Applications/smcFanControl.app/Contents/Resources/smc /usr/local/bin/smc

А также сделать скрипт исполняемым:

This is another new song. 

This was written by Dusty and I for both of our moms and Cal's dad, as well as for our friends and family that have passed. 

His mother passed away two months ago from a 2 year battle with breast cancer, two months after his older brother (and our good friend/bassist) passed.

My mom is also battling with a chronic illness as well and she is honestly my inspiration and who I hope to be like.

Cal's dad's cancer relapsed as well and it's a really difficult time right now... because he is as close to his father as I am my mother. 

So we wrote this for them. Because it's difficult.

Launch Sublime Text 2 from the Mac OS X Terminal

Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.

open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl

You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html

Installation

The official documentation I linked to above recommends creating a ~/bin folder (in your home directory). That's weird, I don't recall ever being asked to do that on OS X since most people install binaries within /usr/local/binwhich – if you're a developer – is likely to already have tons of other binaries.

So contrary to the Sublime team recommendation, we're not going to create a bin folder in your home directory:

ln -s /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl /usr/local/bin/sublime

This will simply create a symlink called sublime (remember, we like names that don't suck to type 500 times a day) between the subl binary stashed in the Sublime application package, and a folder where your system usually looks for binaries to execute (launch). Think of it as a wormhole of awesome.

Now let's do a check to see if everything will run smoothly. Enter this:

open ~/.bash_profile.

You should see at the top of the file a line that starts with: export PATH=

This contains all the directories that will be looked into for executable binaries when you type a command in Terminal. Since we create a symlink to subl called sublime in the /usr/local/bin directory let's check if this directory is listed on that same line.

If it is, perfect. Let's keep going. If not, simply add it like this and save the file:

export PATH=/usr/local/bin:(...)

Note: The "(...)" in this example represents other folders that would be listed on the same line and separated by a colon.

If you had to add /usr/local/bin to your PATH, run the following command before continuing:

source ~/.bash_profile

This will reload your .bash_profile with the newly added directory.

Testing

Open a Terminal window and run:

sublime filename (replace "filename" by an actual file name)

or

sublime foldername (replace "foldername" by an actual folder name)

or even

sublime . (to open the entire current directory)

Conclusion

Now you don't need to get out of Terminal to simply open a file or a folder, you didn't have to add an "alias" or yet another bin directory to your .bash_profile which you would have needed with the official instructions given by the Sublime team.

Have fun, Sublime is a great editor showing a lot of promise.