Skip to main content

OSX improved (Update)

Listen:

Updated May 17, 2024 to fit M* architecture

My favorite development environment on my MacBook includes an improved Zsh shell and an extended .vimrc configuration file with syntax highlighting, error checking, TextMate snippets, and the Solarized color scheme. 

Here's a guide for setting up similar features:  The features include directional key navigation for directories and files, developer-friendly colors, command highlighting, improved history search, auto-complete for options and SSH connections (if keys are known), and many more useful enhancements.  

Get Xcode:
 AppStore => Xcode => Install Xcode

From now we use a terminal window.

Install Brew
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Install git and wget:
 brew install git
 brew install wget


Install oh-my-zsh:
 wget --no-check-certificate https://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh -O - | sh

The script want to change your shell from /bin/bash into /bin/zsh, here you have to provide your password.

To change the theme edit ~/.zshrc and edit line 8:
 ZSH_THEME="YOUR_FAV_THEME"

Install and enable zsh-highlighting:
 git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ~/.oh-my-zsh/plugins/
 edit .zshrc and add in line 27 (space separated):
  zsh-syntax-highlighting

Solarized and Pathogen
(https://ethanschoonover.com/solarized)
(https://github.com/tpope/vim-pathogen)

mkdir -p ~/.vim/autoload ~/.vim/bundle; \  
curl -so ~/.vim/autoload/pathogen.vim \
    https://raw.github.com/tpope/vim-pathogen/HEAD/autoload/pathogen.vim

 
cd ~/.vim/bundle
 git clone https://github.com/altercation/vim-colors-solarized.git


Extended .vimrc:
cd ~/ && git clone https://github.com/ikaros/vim-configuration.git && rm -rf .vim && mv vim-configuration .vim && rake -T && rake place_vim_config

I remove some bundles for now:
 git rm --cache bundle/cucumber
 git rm --cache bundle/rubytest
 git rm --cache bundle/snipmate

and add snipmate, because the bundle above does not work:
 git submodule add https://github.com/msanders/snipmate.vim.git bundle/snipmate

update all bundles:
 git submodule update --init

To change the Solarized theme edit in your .vimrc the background-variable (set background=light | dark)

Finished. Enjoy your new shell!

Coding languages

Rust:
curl –proto ‘=https’ –tlsv1.2 -sSf https://sh.rustup.rs | sh

Golang: 
Download the binaries from https://go.dev/dl/
Sometimes I got into some trouble installing / updating Go, here's snippets to do so:
https://gist.github.com/gsrai/09bfc7db6548aecfbeacdcd89dcd0720

Additional tools I recommend

iTerm (terminal replacement)
VSCode (M* Apple Silicon)
Chrome
CrossOver (for gaming / windows applications)
Docker Desktop
Onyx (edit hidden OSX settings)

Tweaks

Apple Mail

Smart inboxes => filter for over x years old to clean up old mails, or filter for "unsubscribe" to get rid of spam and unwanted mails.

More infos about tuning mail.app to fit your need in that apple knowledgebase article 

Finder

Open finder, press "Apple + ,", here are my tweaks:
=> General: Open folders in tabs .. [X]
=> Tags: Add new tags to find docs, like "work", "private" etc
=> Sidebar: Select what you want to see in the finders' sidebar
=> Advanced: See screenshot 


Thats all, leave a comment when you have more tweaks everyone should know about ;)

Comments

Popular posts from this blog

Deal with corrupted messages in Apache Kafka

Under some strange circumstances, it can happen that a message in a Kafka topic is corrupted. This often happens when using 3rd party frameworks with Kafka. In addition, Kafka < 0.9 does not have a lock on Log.read() at the consumer read level, but does have a lock on Log.write(). This can lead to a rare race condition as described in KAKFA-2477 [1]. A likely log entry looks like this: ERROR Error processing message, stopping consumer: (kafka.tools.ConsoleConsumer$) kafka.message.InvalidMessageException: Message is corrupt (stored crc = xxxxxxxxxx, computed crc = yyyyyyyyyy Kafka-Tools Kafka stores the offset of each consumer in Zookeeper. To read the offsets, Kafka provides handy tools [2]. But you can also use zkCli.sh, at least to display the consumer and the stored offsets. First we need to find the consumer for a topic (> Kafka 0.9): bin/kafka-consumer-groups.sh --zookeeper management01:2181 --describe --group test Prior to Kafka 0.9, the only way to get this inform

Hive query shows ERROR "too many counters"

A hive job face the odd " Too many counters:"  like Ended Job = job_xxxxxx with exception 'org.apache.hadoop.mapreduce.counters.LimitExceededException(Too many counters: 201 max=200)' FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.MapRedTask Intercepting System.exit(1) These happens when operators are used in queries ( Hive Operators ). Hive creates 4 counters per operator, max upto 1000, plus a few additional counters like file read/write, partitions and tables. Hence the number of counter required is going to be dependent upon the query.  To avoid such exception, configure " mapreduce.job.counters.max " in mapreduce-site.xml to a value above 1000. Hive will fail when he is hitting the 1k counts, but other MR jobs not. A number around 1120 should be a good choice. Using " EXPLAIN EXTENDED " and " grep -ri operators | wc -l " print out the used numbers of operators. Use this value to tweak the MR s

AI's False Reality: Understanding Hallucination

Artificial Intelligence (AI) has leapfrogged to the poster child of technological innovation, on track to transform industries in a scale similar to the Industrial Revolution of the 1800s. But in this case, as cutting-edge technology, AI presents its own unique challenge, exploiting our human behavior of "love to trust", we as humans face a challenge: AI hallucinations. This phenomenon, where AI models generate outputs that are factually incorrect, misleading, or entirely fabricated, raises complex questions about the reliability and trust of AI models and larger systems. The tendency for AI to hallucinate comes from several interrelated factors. Overfitting – a condition where models become overly specialized to their training data – can lead to confident but wildly inaccurate responses when presented with novel scenarios (Guo et al., 2017). Moreover, biases embedded within datasets shape the models' understanding of the world; if these datasets are flawed or unreprese