Forem: Jake Schwartz

TIL How Easy It Is To Switch To Zsh

Jake Schwartz — Fri, 06 Mar 2020 02:52:46 +0000

With the latest MacOS release, Catalina, the default operating shell was switched from bash to zsh. This was announced pretty early on, so it wasn't a surprise and I had "Learn ZSH" on my to do list for quite some time but now that I have updated my machines, it reminds you that you need to switch to zsh. And while it is possible to hide that message, this is as good opportunity as ever to make the switch.

There are several frameworks that make it easy to switch as well. The most popular of them is Robby Russell's Oh My Zsh. It seems easy to install and but at first glance, it doesn't have the customization and control I want. I instead chose to try Antigen first. It is similar to a Vim framework called Vundle in philosophy and even allows you to build off OMZ. Antigen is a package manager for zsh and keeps its plugins in what it calls "bundles".

Setting up Antigen took less than 10 minutes. I first installed all of the requirements:

$ brew install zsh
$ brew install antigen

and then I copied the the .zshrc example from the website:

source $(brew --prefix)/share/antigen/antigen.zsh
antigen use oh-my-zsh

antigen bundle git

# Syntax highlighting bundle.
antigen bundle zsh-users/zsh-syntax-highlighting

# Fish-like auto suggestions
antigen bundle zsh-users/zsh-autosuggestions

# Extra zsh completions
antigen bundle zsh-users/zsh-completions

# Load the theme
antigen theme robbyrussell

antigen apply

This does several things. The first two lines start antigen and set it up with a default set of configurations. Then, I add several bundles to add functionality to the shell. These often come in the form of auto-completion or set up commands that are typically in a .bash_profile or .bashrc file. Lastly, I chose a built-in theme and told antigen to apply those changes. When a session is started, it will install those bundles and themes, if they are not already installed, and then sets up the session.

Now you can just start a zsh session by running

$ zsh

This won't switch your shell permanently, it just starts a new session over your current session. This is nice because it allows you to add or remove things to your .zshrc file before entering entering the command that Apple gives to switch your shell over permanently.

That is just a basic zsh configuration. The next step is to move over the rest of my current bash shell functionality. My current set up is not too complex, so there are probably plugins or themes that have what I want out of the box.

TIL How To Add Scapegoat To IntelliJ's Build Process

Jake Schwartz — Tue, 07 Jan 2020 03:11:51 +0000

At work, we have been using Scapegoat with sbt to check for code smells. Scapegoat is a static code analyzer
that has an sbt plugin and we are using that to do our analysis on our build server. While it is possible to run locally as well, it is not built into
IntelliJ, which is what our team uses to develop all of our Scala codebases. Because it does not run whenever we compile, it is sometimes neglected to be run before checking in a change and developers, myself included, have to go back and make the appropriate changes.

To include this in the compile stage, we will take advantage of the sbt plugin:

// plugins.sbt
addSbtPlugin("com.sksamuel.scapegoat" %% "sbt-scapegoat" % "1.0.9")

Then, we will create a separate sbt file for scapegoat, enable the compiler plugin and then configure the scapegoat settings:

// scapegoat.sbt
addCompilerPlugin("com.sksamuel.scapegoat" % "scalac-scapegoat-plugin_2.12.10" % "1.4.0")

scapegoatVersion in ThisBuild := "1.3.11"

scapegoatDisabledInspections := Seq(
  "AsInstanceOf",
)

scalacOptions ++= Seq(
  "-P:scapegoat:dataDir:./target/scapegoat"
) ++ scapegoatDisabledInspections.value.map(x => s"-P:scapegoat:disabledInspections:$x" )

The examples above may not be the most up-to-date versions, but hopefully you get the gist. The second part about the disable inspections is also not required, but it a nice way to define the list in a 'nice' way using the sbt plugin and easily converting it to being using by the compiler plugin. The only required part is the -P:scapegoat:dataDir scalac option. Once you add this, you should see Scapegoat errors show up during both IntelliJ builds and when compiling through sbt.

Hi, I'm Jake Schwartz

Jake Schwartz — Sat, 22 Apr 2017 05:38:03 +0000

I have been coding for 3 years professionally, but started during high school in 2007.

You can find me on GitHub as jakehschwartz and on Twitter @jakehschwartz.

I live in San Francisco, but I am originally from Dover, NH.

I work for Zignal Labs on the Platform (backend) team.

I almost exclusively program in Scala, and use databases like MongoDB and Elasticsearch.

I am currently learning more about Scala, vim, git, bash, zsh, tmux and whatever else I think can help make my life easier.

Nice to meet all of you!