You need to reload your terminal after this. You have several installation options, including npm: npm install -g spaceship-promptĪs indicated on the Spaceship prompt doc, this command should link spaceship.zsh as prompt_spaceship_setup to your $fpath and set the prompt spaceship in. Prompt character turns red if the last command exits with nonzero code.Current Node.js/Ruby/Python/Swift/Docker/… version.Current Git branch and rich repo status.Using the Spaceship prompt, you get a lot more information, such as: The prompt is the text you see before your commands, and, by default, it’s pretty poor and gives you just the basic file system information. The Prompt: Setting Up the Spaceship Prompt Second, you need to enable the plugin by adding its name to the plugins array and disabling WebGL rendering (as explained here) inside of the config object in. First, install it: hyper i hyper-font-ligatures To enable them, we need the hyper-font-ligatures plugin. Geoffrey Dorne defines the concept very clearly here, and you can find visual examples here. Now that we have a great font, we want to enable ligatures, which is a big word to represent two characters associated with another to form a new single character. Make sure you have those single quotes surround your whole list of fonts otherwise, it won’t work. Notice the list of fonts is set between single quotes, so you can add fonts with a several-word name surrounded with double quotes. hyper.js file should now have those set up like this: module.exports = Īlso, be careful here. This is a great-looking nerd font that you can download here (or choose another from all the ones available on this site) which comes with cool icons for file and folder names. We’ll also install our own font by setting the font-family to “FiraCode Nerd Font”. Let’s make a few changes, like setting the font size to 13 and the line-height to 1.2 (if they’re not already set this way). So I thought I’d make an article in this spirit of keeping it simple for everyone.Īt the end of this article you, too, will look for any reason to hit the command line, so let’s begin! I always found those articles were going far too deep in technical twists while all I wanted was to make my terminal more friendly to use quickly. I customized mine referencing several different articles on the web, docs, and troubleshooting forums. But we spend a significant amount of time in there, so we’d better make it enjoyable to be as productive as we can.Īnd as you probably spent a significant amount of time customizing your code editor - choosing the best font, installing the Material Icon theme to have great-looking files and folders, and choosing the best extensions out there - well, there’s no reason not to give your terminal a little makeover, too. If you’re here, chances are you’re not a big fan of your terminal, and entering commands is probably on your painful-moments list as a developer.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |