Keeping developer experience consistent across machines Terminal prompts can be made git aware and use colour to indicate state so you don’t have to query git so often.
#MAKE ATOM DEFAULT TEXT EDITOR MAC FULL#
You can replace tools like ls or cat with modern equivalents that support full colour, unicode icons, git state and more. If it does default to 'Plain Text', picks the wrong grammar for the file, or if for any reason you wish to change the selected grammar, you can pull up the Grammar Selector with Ctrl+Shift+L. But other developer tooling has advanced quite a bit since then. When you open a file and Atom cant determine a grammar for the file, it will default to 'Plain Text', which is the simplest one. Many of the terminal tools that come with unix environments are functionally similar to how they were 20 years ago. Years ago, on my old machine, I setup Sublime to be my default editor for everything, but couldn’t remember how I did. By default, macOS uses Apple’s TextEdit app for any text file, and it’s pretty bad. The latest version lets you run a full Ubuntu instance that integrates seamlessly with the underlying windows instance.īy using WSL2 you can have a (mostly) identical developer experience jumping between MacOS and Windows. Changing the default text editor on macOS I’ve been using the same computer for almost a decade, but recently upgraded my computer. Mac: OS X 10.11 and macOS 10. Windows “WSL” (Windows Subsystem for Linux) is a great tool for this you can use on Windows 10 and newer. I need to use the same tools and the same experience on both.
I regularly code on both MacOS and Windows machines and I was always annoyed how different the default experiences are on each. Duti -s public.json allĭuti -s ain-text allĭuti -s public.python-script allĭuti -s public.shell-script allĭuti -s public.source-code allĭuti -s public.text allĭuti -s public.unix-executable all
0 kommentar(er)
