On Sat, Jun 20, 2015 at 06:56:42AM -0300, Raniere Silva wrote: > Hi, > > I remember reading something about this a log time ago > but my searching skills to the archive aren't very good this morning. > > I just want to let you know that I give a try > to split the terminal in two using the up part for keep the last commands > visible for the learners and the session was very well. > > I wrote more about it at http://blog.rgaiacs.com/2015/06/18/swc_shell.html > if you have interest. And feedbacks are welcome. > > Cheers and enjoy your weekend, > Raniere Hi Raniere,
I used your script (with slight modifications) during git tutorial in Notre Dame last week. I made some further modifications to recover more screen "real estate" — tmux menu bar was removed, prompt was made minimialistic. Nevertheless, I think it was at best mixed success. No fault of the script of course, it worked perfectly. The problem is that 5 or 6 lines of history is not enough for someone who loses track or wants to recall a command from 5 minutes ago to do that. When doing anything with git, I tend to use 'git status', 'git log', 'git diff', 'git show' a lot to check what happened and what will happen. But each of those commands shows up in history, so, in effect, only one or two commands that "do stuff" would appear in the 5-6 line log window. But dedicating much space would not leave enough space for other output, so is not an option either. As a result of this lesson, I think something that allows viewing of full history is necessary. Next time I think I'll try simply running a script which rsync's .bash_history to some website (while true; do inotifywait -e CLOSE_WRITE ~/.bash_history; rsync ~/.bash_history server:public_html/bash_history.txt; done or something like that) instead. Zbyszek _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
