> On Apr 3, 2017, at 07:39, "[email protected]" > <[email protected]> wrote: > > Send Discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.software-carpentry.org/listinfo/discuss > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Discuss digest..." > > > Today's Topics: > > 1. Re: nano clean the window scrool in Windows (was Re: nano not > found after installing gitbash (Raniere Silva)) (Erik Bray) > 2. Re: nano clean the window scrool in Windows (was Re: nano not > found after installing gitbash (Raniere Silva)) (Michael Sarahan) > 3. Dyslexia, learning to code, and the Carpentries (C. Titus Brown) > 4. Re: nano clean the window scrool in Windows (was Re: nano not > found after installing gitbash (Raniere Silva)) (Sumana Harihareswara) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 2 Apr 2017 19:59:46 +0200 > From: Erik Bray <[email protected]> > To: Michael J Jackson <[email protected]> > Cc: Software Carpentry Discussion > <[email protected]> > Subject: Re: [Discuss] nano clean the window scrool in Windows (was > Re: nano not found after installing gitbash (Raniere Silva)) > Message-ID: > <caotd34yqvyxnylbdudera6ftgpdkpe8g+elitmgvin82dca...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > 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 > > > ------------------------------ > > Message: 2 > Date: Sun, 2 Apr 2017 20:14:18 -0500 > From: Michael Sarahan <[email protected]> > To: Erik Bray <[email protected]> > Cc: Software Carpentry Discussion > <[email protected]> > Subject: Re: [Discuss] nano clean the window scrool in Windows (was > Re: nano not found after installing gitbash (Raniere Silva)) > Message-ID: > <CAB9hrOohC+Ox6ND7dv=oymz5rjoqawvc11z7jr1r4y8kjkg...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Please also consider MSYS2 or conda (which repackages MSYS2). Either offers > all the benefits of cygwin, but also handles Windows native paths more > intelligently, lowering the cognitive load. > >> On Apr 2, 2017 12:59 PM, "Erik Bray" <[email protected]> wrote: >> >> 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.software-carpentry.org/pipermail/discuss/attachments/20170402/45fdd3d1/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Mon, 3 Apr 2017 06:20:34 -0700 > From: "C. Titus Brown" <[email protected]> > To: Software Carpentry Discussion > <[email protected]> > Subject: [Discuss] Dyslexia, learning to code, and the Carpentries > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > at the JGI User Meeting two weeks ago, I met someone who wanted some advice > and/or lessons on learning to code while dyslexic. Any resources or opinions > would be welcome - I don’t know that I’ve heard it discussed by any of the > Carpentry folk or in the context of lesson design. Curious! > > (E-mail me privately if you’d like a summary of what I find.) > > thanks, > —titus > > > > ------------------------------ > > Message: 4 > Date: Sat, 01 Apr 2017 12:24:26 -0400 > From: Sumana Harihareswara <[email protected]> > To: Kate Hertweck <[email protected]>, Software Carpentry > Discussion <[email protected]> > Subject: Re: [Discuss] nano clean the window scrool in Windows (was > Re: nano not found after installing gitbash (Raniere Silva)) > Message-ID: > <1491063866.2097412.930893408.4bdff...@webmail.messagingengine.com> > Content-Type: text/plain; charset="utf-8" > > Hi all -- a request to move conversation about this to the relevant > GitHub issues, as the Steering Committee asked. Thanks. > > > -- > > Sumana Harihareswara > > Changeset Consulting > > [email protected] > > > > > > > >> On Fri, Mar 31, 2017, at 01:49 PM, Kate Hertweck wrote: >> >> Hello all, > >> > >> Thanks so much contributing your opinions and experiences to this >> discussion. The Steering Committee is following this conversation with >> great interest, in the hopes of developing some methods for >> alleviating hiccups during workshops. There appear to be two separate >> concerns being voiced here: 1) What are the goals of the SWC shell >> lesson? and 2) How can we improve the logistics of installing/using a >> text editor with the shell lesson? >> > >> If you would like to continue the conversation about the first concern >> and the goals of the shell lesson, please redirect your comments to >> this issue [1], which will allow us to track community consensus more >> accurately. This lesson has been taught enough that we have a good >> idea how it is perceived by our learners, and it seems the time is >> right to revisit our learning objectives and see how they match >> student interests. >> > >> If you’re interested in more information about instructor preferences >> and possible solutions for the second concern (text editors for the >> shell lesson), you will find this issue of interest [2] and we hope >> you will continue to add comments there. >> > >> For now, the Windows installer isn't working, so while we're working >> to fix that, we'll add instructions for using Atom in a workshop. If >> you are an instructor teaching the shell lesson soon and are >> comfortable using Atom (and helping your students get it installed!), >> please try it out and add to this issue [3] to let us know how it >> worked. We'll get in touch with people teaching upcoming workshops to >> let them know about this issue and potential solutions. >> > >> [1] https://github.com/swcarpentry/shell-novice/issues/542 > >> [2] https://github.com/carpentries/conversations/issues/11[1] > >> [3] https://github.com/swcarpentry/workshop-template/issues/390 > >> > >> > >> On Fri, Mar 31, 2017 at 12:46 PM, Karin Lagesen >> <[email protected]> wrote: >>> On 30.03.2017 18:15, Carol Willing wrote: > >>> [snip] >>>> Unlike nano, Atom was designed for people familiar with web >>>> browsing, and it could be argued that nano while seeming simple to >>>> some is more difficult to those that have grown up using the web >>>> browser daily. Having taught many students in different workshops, >>>> Atom just works. It takes minutes to install and students have no >>>> difficulty using it. I haven't seen students have difficulty opening >>>> a file or navigating directories. >>> >>> I have taught plenty of 20-something people who had very flimsy ideas >>> of what a file system was, what a directory was, and where their >>> files were. This is something they do learn in the shell lesson, but >>> still, having them maneuver in the directory structure like this for >>> an editor will take time away from teaching them all the other stuff >>> in the lesson. >>> > >>> I have no big opinions on editors as such, but for SWC I strongly >>> think it should be a terminal based editor to avoid these issues. >>> >>> Karin >>> > >>> > >>> _______________________________________________ > >>> Discuss mailing list > >>> [email protected] > >>> http://lists.software-carpentry.org/listinfo/discuss > >> > >> > >> > >> -- > >> Kate L. Hertweck, Ph.D. > >> Assistant Professor, Department of Biology > >> The University of Texas at Tyler > >> 3900 University Blvd., Tyler, TX 75799 > >> Email: [email protected] > >> Office: HPR 109, 903.565.5882 > >> https://www.uttyler.edu/biology/ > >> _________________________________________________ > >> Discuss mailing list > >> [email protected] > >> http://lists.software-carpentry.org/listinfo/discuss > > > > > Links: > > 1. http://(https//github.com/carpentries/conversations/issues/11 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.software-carpentry.org/pipermail/discuss/attachments/20170401/dffd4ded/attachment.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/listinfo/discuss > > ------------------------------ > > End of Discuss Digest, Vol 45, Issue 2 > ************************************** _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
