basshadow.blogg.se

Git on mac terminal
Git on mac terminal






git on mac terminal
  1. #Git on mac terminal upgrade
  2. #Git on mac terminal code
  3. #Git on mac terminal windows

We'd rather be working on hyperlinks in the Terminal ( #574 #204), or adding support for a default Terminal application ( #492), or tab tearout ( #5000), or application theming ( #3327), or Mark Mode( #5804), or Quake Mode ( #653), or any of the other 1000 open issues on this repo.

#Git on mac terminal windows

But it absolutely is not a priority for us when we'd rather work on improving the developer experience here on Windows first and foremost. Git Bash is a package that installs Bash, some common bash utilities, and Git on a Windows operating system. Bash is a popular default shell on Linux and macOS.

git on mac terminal

A shell is a terminal application used to interface with an operating system through written commands. We could use (whatever the UI stack on OSX is), OpenGL, and (something?) to replace them. What is git bash on Mac Bash is an acronym for Bourne Again Shell.

git on mac terminal

There might be replacements for each of those components. Replacing any one of them with a cross-platform solution would be an enormous undertaking, if it's possible at all. Most versions of MacOS will already have Git installed, and you can activate it through the terminal with git version. Those are all critical components in how the Terminal is built. On selecting ' associate a Git Repository with this site the, could not locate Git box comes up every single time.

#Git on mac terminal upgrade

If WinUI, DirectX, and WinRT were available on OSX, then it would be trivial for us to port the Terminal to MacOS. As of the latest upgrade Febrauary 2020 the Git functionality of DW is broken for my MacBook Pro. With the 4 of us on the Terminal, I'm not sure it's really feasible for us to try and support an entirely separate UI stack. They likely have a team of engineers for the Windows version and a separate team for the Mac version. Plus, with their larger teams, it's probably easier for them to maintain two different UI stacks (one for Windows and one for OSX). I'm not sure what tech stack they're using, but I'm sure that once they got the apps running cross-platform, it was easier to maintain that. Office on the other hand has been around for decades and has an enormous team of engineers. We wanted to make sure to build a native application so that in the long run, the Terminal would have a smaller memory commit and be far more performant than we could ever get with Electron. However, they do come with the burden of the entire Electron runtime, and that's something that we weren't comfortable with on the Terminal team.

#Git on mac terminal code

Visual Studio Code and Teams are Electron applications which are fundamentally web apps, so they're trivial to make cross platform.








Git on mac terminal