On Thu, Mar 30, 2017 at 6:47 PM, Michael J Jackson <[email protected]> wrote: > Hi, > > The original motivation for the choice of Atom was: > >> today at the workshop, one of the our Windows learners asked me why after >> quit nano the previous command weren't available when scroll the window up. >> The learner was very annoyed to not be able to see the history. > > > This is indeed the case with nano. The quick fix is to use two shell > windows, one with the editor and one with the prompt (a common mode of > working with multiple shell windows anyway). Learners and instructions will > need to switch windows, but this was listed as an issue with Atom as well.
This is not *normally* the case with nano. This is one of the many, many bugs associated with the current Windows installation environment based on "Git Bash". The Cygwin-based learning environment I'm working on (see https://github.com/carpentries/conversations/issues/11#issuecomment-290994635) does not have these bugs. The reason Cygwin works so well is that all software in the environment, from the shell, the terminal emulator, and nano (not to mention core libraries like ncurses and readline) were built to work together. When you enter and exit nano in Cygwin's bash it properly restores the previous screen. > I'd stick with nano for the reasons suggested below, until some research has > been done to show that Atom will not get in the way of the attendees > learning experiences. Otherwise there's a risk that SWC goes chasing after > the latest shiny tools before their value has been proven. +1 Best, Erik _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
