Command line opening of Atom triggering Windows command prompt

My normal routine for opening up a project in the Atom editor on Windows is to go to the directory using the Git Bash terminal and typing atom . This opens the entire contents of the directory in Atom.

After a recent Windows update, when I type atom . I now see this:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


This is a flashing command prompt. Is the base Windows command prompt taking over from the Git Bash terminal I’m using?

When I input just atom in the terminal the Atom editor opens as normal.

When I input explorer . it works just fine (opens an explorer window in the current directory).

When I open Windows PowerShell and input atom . the correct behavior happens.

When I run git-cmd.exe and input atom . the correct behavior happens.

This is a known issue with Atom:

Running atom.cmd . will produce the expected behavior.

  • How to connect windows7 Git to dreamhost server Git
  • How do I get Putty to show color coding on git output?
  • Jenkins can not clone Git repository over Git/SSH on Windows
  • Vim fugitive plugin does not recognise git archive on Windows
  • sh.exe": emacs: command not found (Git bash Windows)
  • GIT Bash for windows gives no result and returns to command prompt
  • Mercurial: “abandoned transaction found - run hg recover”. Recover does not work
  • Update multiple heroku apps by batch script
  • 2 Solutions collect form web for “Command line opening of Atom triggering Windows command prompt”

    I’d comment but don’t have enough reputation.

    I started experiencing the same thing this morning, but haven’t updated my Windows 10 for over a week.
    If you open:

    C:\Program Files\Git\git-cmd.exe

    it works fine. So I think it’s actually mintty.exe (C:\Program Files\Git\usr\bin), the terminal app that runs when you open Git Bash. My current version of mintty is 2.0.3.

    UPDATE: Looks like this is tied to today’s update of atom:

    UPDATE 2 – TEMPORARY SOLUTION: add this alias to your .bashrc or aliases file:

    alias atom='atom.cmd'

    Should do the trick until the good people at Atom release a fix.

    I suggest two steps:

    1. Check your git configs to make sure atom is still your default editor: git config -l. If it isn’t, set it with git config --global core.editor "atom --wait".
    2. You may need to create a new path for atom, depending on where you installed it.
    Git Baby is a git and github fan, let's start git clone.