<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daria Sova on Medium]]></title>
        <description><![CDATA[Stories by Daria Sova on Medium]]></description>
        <link>https://medium.com/@todariasova?source=rss-230fbd788199------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yEpP9uqKEclVuRkQ</url>
            <title>Stories by Daria Sova on Medium</title>
            <link>https://medium.com/@todariasova?source=rss-230fbd788199------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:31:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@todariasova/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Automating your MacOS setup with Homebrew and Cask]]></title>
            <link>https://medium.com/macoclock/automating-your-macos-setup-with-homebrew-and-cask-e2a103b51af1?source=rss-230fbd788199------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2a103b51af1</guid>
            <category><![CDATA[shell]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[bash-script]]></category>
            <category><![CDATA[setup-guide]]></category>
            <category><![CDATA[macos]]></category>
            <dc:creator><![CDATA[Daria Sova]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 13:01:01 GMT</pubDate>
            <atom:updated>2020-05-01T05:57:05.051Z</atom:updated>
            <content:encoded><![CDATA[<h3>Automating your macOS setup with Homebrew and Cask</h3><h4>How to quickly prepare your environment in a fresh macOS installation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*flq-toWWITvgNowNmzBQJA.gif" /></figure><p>Need to wipe clean your MacBook or simply got a new one and thinking about all this time it will take you to set it up the way the old one works? You might have an easy way to copy over your dotfiles (maybe be even the same way I described in my previous blog post 😉), but what about all the programs you had installed? What about all the programming languages, packages, and IDEs?</p><p>Don’t worry, your setup shouldn’t take forever and you shouldn’t even be thinking about it as much. Luckily it is very easy to write a little script that will just do everything for you! And as long as you keep it updated your setup will take just a few minutes.</p><p>Starting a script is just a matter of creating a new shell file, for example, I called mine `os-setup-script.sh` and added a few basic lines to it</p><pre>#!/usr/bin/env bash<br># Setup script for setting up a new macos machine</pre><pre>echo &quot;Starting setup&quot;</pre><pre># install xcode CLI<br>xcode-select —-install</pre><p>This indicates that we will use shell for running the script, produces simple test output signalling that the script started executing, and as the first step, installs Xcode CLI.</p><h3>Homebrew</h3><p><a href="https://brew.sh/">Homebrew</a> is an opened-source free package management system for macOS. And if you have been using MacBooks it’s likely you used for package installations (like Ruby, MySQL, FZF, etc).</p><p>If you want to see which packages you have installed with homebrew to include them in your script you can run the `brew list` command in your terminal.</p><p>The first thing we want to do though if you are planning to run it on a new computer is making sure that homebrew is installed, so we will add the following lines to our script:</p><pre># Check for Homebrew to be present, install if it&#39;s missing<br>if test ! $(which brew); then<br>    echo &quot;Installing homebrew...&quot;<br>    ruby -e &quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&quot;<br>fi</pre><p>This will install homebrew if it’s missing.</p><p>Then we want to make sure that we have updated the version of homebrew, in case it was already installed:</p><pre># Update homebrew recipes<br>brew update</pre><p>Now we can list and install homebrew packages with the following block:</p><pre>PACKAGES=(<br>    git<br>    tmux<br>    bat<br>    macvim<br>    mysql<br>    fzf<br>    ctags<br>&lt;...list all the packages you want to install&gt;<br>    readline<br>)</pre><pre>echo &quot;Installing packages...&quot;<br>brew install ${PACKAGES[@]}</pre><pre># any additional steps you want to add here</pre><pre># link readline<br>brew link --force readline</pre><p>Homebrew will automatically uninstall old versions of the formulas after 1 month, but if you want to do a manual clean up you can also add this step:</p><pre>echo &quot;Cleaning up...&quot;<br>brew cleanup</pre><h3>Specific languages</h3><p>If you want to install any specific languages and associated packages you can also easily do so. For example, if you want to install some python packages you can add something like this to your script:</p><pre>echo &quot;Installing Python packages...&quot;<br>PYTHON_PACKAGES=(<br>    virtualenv<br>    virtualenvwrapper<br>)<br>sudo pip install ${PYTHON_PACKAGES[@]}</pre><p>If you want to install ruby or ruby gems:</p><pre># ruby install<br>ruby-install ruby 2.5.5</pre><pre>echo &quot;Installing Ruby gems&quot;<br>RUBY_GEMS=(<br>    bundler<br>    byebug<br>    json<br>    middleman<br>    middleman-cli<br>    rake<br>    rspec<br>)<br>sudo gem install ${RUBY_GEMS[@]}</pre><h3>Cask</h3><p>Cask is an extension of the Homebrew package manager that lets you install macOS apps. It comes with homebrew so you do not need to install it, you can simply use brew cask &lt;app_name&gt; out of the box. As with the packages, you can also see a list of installed apps with the `brew cask list` command, and then add those to your script.</p><pre>echo &quot;Installing cask...&quot;</pre><pre>CASKS=(<br>    iterm2<br>    adobe-acrobat-reader<br>    skype<br>    slack<br>    spotify<br>    intellij-idea-ce<br>    visual-studio-code<br>    steam<br>    evernote<br>    1password<br>    macdown<br>)</pre><pre>echo &quot;Installing cask apps...&quot;<br>brew cask install ${CASKS[@]}</pre><h3>Some additional configurations</h3><p>You might want to add other things to your setup, this is just covering the basics. For example, these are some things that I added:</p><pre>echo &quot;Configuring OS...&quot;</pre><pre># Set fast key repeat rate<br>defaults write NSGlobalDomain KeyRepeat -int 0</pre><pre># Require password as soon as screensaver or sleep mode starts<br>defaults write com.apple.screensaver askForPassword -int 1<br>defaults write com.apple.screensaver askForPasswordDelay -int 0</pre><pre># Show filename extensions by default<br>defaults write NSGlobalDomain AppleShowAllExtensions -bool true</pre><pre># Enable tap-to-click<br>defaults write com.apple.driver.AppleBluetoothMultitouch.trackpad Clicking -bool true<br>defaults -currentHost write NSGlobalDomain com.apple.mouse.tapBehavior -int 1</pre><p>Once you are happy with everything you need for the brand new setup you can add the final line</p><pre>echo &quot;Macbook setup completed!&quot;</pre><p>And that’s it! 🎉 ✅</p><p>Now you have your perfect setup! And if you wipe your laptop clean or buy a new one you just run this script with sh &lt;path to file&gt; and your computer will do everything for you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2a103b51af1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/macoclock/automating-your-macos-setup-with-homebrew-and-cask-e2a103b51af1">Automating your MacOS setup with Homebrew and Cask</a> was originally published in <a href="https://medium.com/macoclock">Mac O’Clock</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing your dotfiles .*]]></title>
            <link>https://medium.com/@todariasova/managing-your-dotfiles-59e13e8ab2d6?source=rss-230fbd788199------2</link>
            <guid isPermaLink="false">https://medium.com/p/59e13e8ab2d6</guid>
            <category><![CDATA[vimrc]]></category>
            <category><![CDATA[dotfiles]]></category>
            <category><![CDATA[git-worktree]]></category>
            <category><![CDATA[bashrc]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Daria Sova]]></dc:creator>
            <pubDate>Tue, 05 Nov 2019 03:21:56 GMT</pubDate>
            <atom:updated>2019-11-05T03:21:56.446Z</atom:updated>
            <content:encoded><![CDATA[<h3>Managing your dotfiles .*</h3><p>So you are finally tired of manually syncing your dotfiles? 😬</p><p>I’ve had the same personal computer for 6 years (Thanks Steve 😉 🍏) but this year I finally upgraded. I keep all my dotfile configs in Github repo so it’s pretty easy to just clone them to my new computer and it’s ready to go. But then I also use them at my work laptop now, and I end up modifying them more often, so I started looking for a better way to sync them all together 🤔</p><p>This is not a new problem and if you google there’re hundreds of blogposts and comments out there. I basically did that. And this is the solution that I liked the most: the idea is to link a cloned git repo of your dotfiles with the ones you have in `~/$HOME` using git worktrees.</p><p>The reason I liked it is because you can easily commit any changes using the alias and it will actually commit them into your git repo and then push to Github — amazing! 🎉</p><p>This is mainly based on <a href="https://www.atlassian.com/git/tutorials/dotfiles">this blog post</a> I stumbled upon in my search journey for a perfect solution. So I took that as the base, tweaked a little to my needs and wrote a bash script for that will just do all of that for me whenever I’m setting up a new machine!</p><p>SO LET’S WALK THROUGH THE STEPS</p><h3>Ok back up a sec… what exactly is a git worktree</h3><p><em>You can skip this if you already know.</em></p><p>Worktree is essentially like a copy of your main git repository. You can have multiple worktrees associated with your main git repository. The best thing about them is that because those are linked it’s easy to sync up changes between your worktrees and main directory, as we will see later. You can read more about them <a href="https://git-scm.com/docs/git-worktree">here</a>.</p><h3>Let’s go through the setup steps</h3><ol><li>What we are going to do is clone your GitHub repo with your dotfiles in the folder of your choice:</li></ol><p>&quot;&gt; git clone —-bare &lt;GITHUB_REFERENCE&gt; $HOME/dotfiles</p><p>This clones my dotfiles repo in $HOME/dotfiles. It’s important to note that we want a <a href="http://www.saintsjd.com/2011/01/what-is-a-bare-git-repository/">bare repository</a> here. Since the repo will not be edited directly but rather through its worktree.</p><p>2. Now we want to create an alias that will be like new command, allowing us to manipulate the changes of our dotfiles in the home repo and commit them to the main repository as well as push to github.</p><p>You can name it whatever you want, I was choosing between config and dotfiles and chose the latter to see if it sticks.</p><p>alias dotfiles = &#39;/usr/bin/git --git-dir=$HOME/dotfiles/ --work-tree=$HOME&#39;</p><p>Now every time you do dotfiles command in the terminal it would know that you refer to that folder.</p><p>If you do dotfiles checkout in your home directory that will checkout all your dotfiles from the cloned repo to ~/.. That easy! No copy over commands.</p><p>3. Now, you probably have a lot of other files in your home directory, so we want to make sure that only the once we checked out are getting traced by git. So let’s set the appropriate flag:</p><p>dotfiles config --local status.showUntrackedFiles no</p><p>Now, if you do dotfiles status it shows you any uncommited changes, if any.</p><p>4. 🛑 ✋ Before you go and try all the git commands, we need to add the alias to your .bashrc file so you don’t have to set it every single time.</p><p>echo &quot;alias dotfiles=&#39;/usr/bin/git --git-dir=$HOME/dotfiles/ --work-tree=$HOME&#39;&quot; &gt;&gt; $HOME/.bashrc</p><p>That’s it! Now you cad do</p><p>dotfiles add &lt;file&gt;</p><p>dotfiles commit</p><p>aand</p><p>dotfiles push to make sure your changes are sync with github!</p><p>…aand any other git command really 😀</p><p>Now, let’s see how we can put this into a simple script to do the work for us.</p><p>All I did here was copying the commands described above. The only condition added is to checked whether you have already cloned the repository so that the script can be idempotent. Of course you can go further and add other checks, or backup your dotfiles before you run the script if you want to save those. For my purposes this will be used on clean new laptop so that’s all I need. But feel free to share your versions! 🎉</p><pre># /bin/bash<br># Change this variable to customize your script<br>#<br>REPO_NAME=’dotfiles’<br><a href="/service/mailto:GITHUB_LINK=&#39;git@github.com">GITHUB_LINK=’</a>&lt;your_repo_url&gt;’<br>ALIAS_NAME=’dotfiles’<br>GIT=`/usr/bin/git`</pre><pre>if [ ! -d “$HOME/$REPO_NAME” ]; then<br> echo “Cloning your github repo …”<br> `git clone --bare $GITHUB_LINK $HOME/$REPO_NAME`<br> cd ~/<br> echo “Adding your dotfiles directory to .gitignore”<br> echo “$REPO_NAME” &gt;&gt; .gitignore<br> alias dotfiles=’$GIT --git-dir=$HOME/dotfiles/ — work-tree=$HOME’<br> echo “Copying your dotfile to your home directory..”<br> `dotfiles checkout`<br> echo “Adding your alias to your bash config”<br> echo “alias dotfiles=’$GIT --git-dir=$HOME/dotfiles/ --work-tree=$HOME’” &gt;&gt; $HOME/.bashrc<br> source $HOME/.bashrc<br> echo “Configuring tracking of files..”<br> `dotfiles config --local status.showUntrackedFiles no`<br> echo “All done!”<br>else<br> echo “You already have $HOME/$REPO_NAME directoty”<br>fi</pre><p>I just started using this setup and it looks very promising! If you have another way of solving the same problem you like, let me know in the comment! 😃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59e13e8ab2d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rails Vim 101: Essential Vim plugins for Ruby on Rails Development]]></title>
            <link>https://medium.com/@todariasova/rails-vim-101-essential-vim-plugins-for-ruby-on-rails-development-d74e808d186d?source=rss-230fbd788199------2</link>
            <guid isPermaLink="false">https://medium.com/p/d74e808d186d</guid>
            <category><![CDATA[rails]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[vim-plugins]]></category>
            <category><![CDATA[vim]]></category>
            <category><![CDATA[terminal]]></category>
            <dc:creator><![CDATA[Daria Sova]]></dc:creator>
            <pubDate>Mon, 25 Jun 2018 23:17:36 GMT</pubDate>
            <atom:updated>2020-06-11T15:28:32.795Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this post I’ll talk about why did I switched back to vim for Rails development and what are the must-have vim plugins you should consider setting up your .vimrc for Rails.</em></p><h4>Little Into</h4><p>My first introduction to vim was a bit over two years ago when I was doing my first internship, learning the basics of Rails development. Everyone at the company seemed to be hard core vim programmer and I was a second year Comp Sci student using something like Sublime and Eclipse (yah I know..). So essentially I was “peer pressured” to learn how to code with vim and it was surprisingly very exciting. I had no idea that vim editor can be so powerful. At the time I was a very novice vim user and my vimrc was the most basic that was enough to work on relatively small rails apps. After that internship I very rarely vim for day to day development. Jumping from Java to Scala to Python to JS it just seemed easier to use IDEs that worked great (however I always used vim plugins for those 😉) .</p><p>Fast-forward three years, I just joined Shopify and last month and got back to Rails development. When I started I tried a few IDEs like Visual Code Studio which I very much like for Golang development, but it just did not work with the giant Rails project we have. Function definitions probably worked 10% of the time and a lot of the plugin were lagging. RubyMine is probably the best IDE out there for Rails development, but it feels very heavy, I personally don’t like how searching works and, honestly, I just couldn’t get used to all the keys shortcuts. That’s exactly when I remembered that once upon a time I used Vim! I knew it would take me quite a bit of time to get comfortable using vim again, but more concerning getting a setup with which my vim will be efficient and easy to use for Rails projects. But after a few weeks of struggling with IDEs and constantly switching between RubyMine and VSCode I decided that it would be worth investing the time into.</p><p>It took me probably around a few days of talking to other developers in the office, reading blog posts online, and changing my vimrc file to setup a decent environment for rails development.</p><p>If you’re switching to Vim as a Rails developer this might be very helpful to read. In this blog post I’ll show my basic setup that perfectly works for me and should work for anyone who is just setting up their vimrc 😉</p><h4><strong>The basics</strong></h4><p>Ok, first things first! Make sure that you have basic essential vim features enabled:</p><pre>set number</pre><pre>syntax on</pre><pre>filetype plugin indent on</pre><pre>filetype on</pre><pre>filetype indent on</pre><p>Those above make sure you have lines number, syntax highlighting, and filetype ident on.</p><p>Next up, you want to customize auto file indentation for ruby and erb files:</p><pre>autocmd FileType ruby setlocal expandtab shiftwidth=2 tabstop=2</pre><pre>autocmd FileType eruby setlocal expandtab shiftwidth=2 tabstop=2</pre><p>Next two plugins you would want are</p><pre>Plugin ‘vim-ruby/vim-ruby’</pre><pre>Plugin ‘tpope/vim-rails’</pre><p>Those will give you better syntax highlighting and will allow you to call rails console or run tests from vim windows.</p><p>If you do `==` on a single line or a visual block vim will automatically ident your Rails files. Cool, isn’t it? Veery useful 🙂</p><h4>File Navigation</h4><p>Ok, cool, we got syntax highlighting and indentation working, now we want something to navigate the files. If your project is relatively large it would be impossible to memorize where everything is.</p><p>For file hierarchy, I use a popular nerdtree plugin. It is a truly essential plugin to have for any kind of development in vim. It shows that file structure of the project that every IDE out there has by default. You can see the current directory, look for a file, open/close folders and jump to currently opened files in the directory to see where they are.</p><p>You can set it up so it automatically opens up with when you open file in vim (that’s what I did). I also remapped ‘trigger’ key to ‘-‘ (that will open close the nerdtree), and highlight of the current file in the tree window to ‘]’ (if you have multiple files open and press ‘]’ vim will highlight the current file in the nerdtree window — very useful).</p><p>Here are my NerdTree settings:</p><pre>“ Files structure tree</pre><pre>Plugin ‘scrooloose/nerdtree’</pre><pre>map — :NERDTreeToggle&lt;CR&gt; “ <em>open/close nerdtree window</em></pre><pre>map &lt;leader&gt;r :NERDTreeFind&lt;cr&gt; “ <em>this is the key to jump to the nerdtree window from any other window</em></pre><pre>autocmd BufWinEnter * NERDTreeFind</pre><pre>map ] :NERDTreeFind&lt;CR&gt; “ <em>pressing this inside any open file in vim will jump to the nerdtree and highlight where that file is -&gt; very useful when you have multiple files open at once</em></pre><h4>Search 🔍</h4><p>Searching is everything when you deal with huge code bases. You need to constantly look for variables and methods usages, definitions and files based on the keywords you come across in the code.</p><p>Thankfully there are a bunch of great plugins that make searching in vim painless. This is probably one of my favourite features. I really like how easy and fast searching in vim/terminal can be.</p><p>Ok, so we want to be able to search for files. Probably the greatest plugin out there is Fuzzy search (FZF). It is just great! There is also popular Ctrl-P. They pretty much have the same functionality but I found FZF to be a bit faster so stick to it.</p><p>FZF is a command line tool so to install vim support you have to install fzf first and only then fzf.vim.</p><p>On Mac OSX you can just do it with homebrew</p><pre>brew install fzf</pre><p>After that just add to your .vimrc:</p><pre>Plugin ‘/usr/local/opt/fzf’</pre><pre>Plugin ‘junegunn/fzf.vim’</pre><p>There are also a lot of things you can customizes like colours etc, so check out their <a href="https://github.com/junegunn/fzf.vim">GitHub repo</a> for the instructions!</p><pre>“ remap envoke key</pre><pre>nnoremap &lt;silent&gt; &lt;C-z&gt; :FZF&lt;CR&gt;</pre><p>I remapped the keys and all I have to do is press Ctrl-z and a search window pops up at the bottom (you can customize that too) and matches all the files in the directory as you type. Super fast! Once you found a file, you can choose it and open in the existing window or in the new horizontal or vertical split. Great, isn’t it?</p><h4>More searching</h4><p>Next one up is searching for various key words and function names in the files. This is essential for any development! For that you would want to install RipGrep. It is a great search tool. You can search for direct matches, regex expressions, and even specify files type or location for the search. Generally it searches through all the file under the current directory ignoring anything in .gitignore and binary files (who want to search through that..).</p><p>Setup is very easy:</p><pre>brew install ripgrep</pre><p>Done! Now head to their <a href="https://github.com/BurntSushi/ripgrep">Readme</a> to learn all the functionality!</p><h4>Autocomplete</h4><p>I love autocomplete! ❤️ It saves me time! Lots of time! And prevent me from mistyping 😄</p><p>So I use popular neocomplete!</p><pre>“ neocomplete Plugin</pre><pre>Plugin ‘Shougo/neocomplete.vim’</pre><h4>Function Definitions</h4><p>This is a hard one. The reason I tried to use RubyMine is because their Rails function definitions is the best out of all IDEs out there. Vim has a good well-known plugin C-tags that is intended todo the job. However, it is not that easy. There are two problems with it. First one is that it might not be able to handle giant projects and I heard people having problems with large code basis, however it seems to work fine for me.</p><p>Second one is that Ruby is a dynamically typed language which makes it almost impossible to get the definitions right: if you have several classes implementing functions with the same name, you might not jump to the right one..yah…</p><p>But It works well for jumping to class files and function definitions in the same file, overall I use it quite a big and ripgrep if I don’t end up in the right place 😉</p><p>The way Ctags work is the index classes, methods, function names and store that in tags files for quick referencing. Ctags actually support about 40 programming languages and could be used not only for Rails development.</p><p>To install:</p><pre>brew install ctags</pre><p>Now all you need to do is to run</p><pre>ctags -R.</pre><p>Inside a project directory</p><p>This will perform the indexing step. Note that it might take a little while for large project stay patient 🙂</p><p>Now you’re good to go and jump around!</p><p>Usage:</p><p>To just to a definition just press &lt;C-]&gt;</p><p>on an identifier. If you want to go back press &lt;C-t&gt;. What’s cool is that all your jump calls are stored in a stack so you can always go back to your original files with &lt;C-t&gt; jumps!</p><p>You can also remap the keys.</p><p>And for situations when there are multiple matches you would probably just to the closest one in the directory tree but tags allow you to explore all the options; use :tnext and :tprev for jumping between found definitions. You can read more about that in the docs.</p><h4>Comments</h4><p>One feature that I just love in IDEs is that I can comment/uncomment code blocks with just a single key shortcut. If you’re like me I got some great news: yes, there is a vim plugin for that! And it’s called Commentary.</p><p>Here is how to set it up:</p><pre>Plugin ‘tpope/vim-commentary’</pre><pre>noremap \ :Commentary&lt;CR&gt;</pre><pre>autocmd FileType ruby setlocal commentstring=#\ %s</pre><h4>Spelling</h4><p>Sometimes I cannot spell… 😄</p><p>You know when you committed something and about to push to a remote branch BUT WAIT you misspelled commit message 😢 that happened to me way too often in the last while and I got a spell checker plugin!</p><p>Set it up, if you don’t pay that much attention to English as I do!</p><pre>“ Set SPELLCHeCK YYAH</pre><pre>set spell spelllang=en_ca</pre><h4>Bonus</h4><p><strong>Vim Themes!!</strong> And colours setup! <em>yayayaya </em>💃 🎉 🎆</p><p>I am super visual person and I really care about the colours I see in my terminal (I do stare at my screen 8–12hrs a day 👀)</p><p>And thankfully you can completely customize your vim!</p><p>There are tooons of ready to go themes out there that you can just fins, plugin, and enjoy! (If you feel committed enough you can alway write your own *perfect* theme). I went with the first option for now!</p><p>I really like VS Code colours so I found a theme that was built on it, it’s called <a href="https://github.com/mhartington/oceanic-next">Oceanic-next</a>.</p><p>And looks like (except I made my text bold 😄):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jlyn92NEVxudnNdzvil1XA.png" /></figure><p>They have instructions on how to install it on the GitHub page 🙂</p><h4>Conclusions</h4><p>So this is about it! This setup works just fine for me, but I am always keeping eye on new plugins and configurations that will make my development life faster and easier! One thing I want to really invest time into is keys remapping, setting up the perfect keys map for all the plugins is just :gold: maybe once I do I will write another post 😉</p><p>If you are using some awesome plugins I haven’t covered please comment below, I’d love to learn about them! And thanks for reading this ❤️</p><p>This is the link to my <a href="https://github.com/DariaSova/dotfiles/blob/fun/.vimrc">current .vimrc </a><em>(it will probably be changing over time).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d74e808d186d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>