On 04/29/2015 02:21 PM, Naupaka Zimmerman wrote:
Hi all -
This same issue came up on the discuss list last summer, and one
solution that was proposed was to set the PROMPT_COMMAND variable to
echo the last line of history to a text file in Dropbox.
export PROMPT_COMMAND="history 1 >> ~/Dropbox/history.txt"
cool,
combined with tmux to split the terminal (or two terminals always visible)
1) tail -n 0 -f ~/myhistory
2) export PROMPT_COMMAND="history 1 >> $HOME/myhistory"
....
I'll experiment it at my next workshop
Rémi
Then the instructor can give the students a public link to this file
and they can easily follow along just by refreshing their browser. The
instructor doesn't have to do anything extra to get it to work
continuously once they set it up, and once the workshop is over, they
can just comment it our of their bashrc/bash_profile and it stops.
This works on Mac/Linux/GitBash.
I did a little explanation of it on a comment to one of the SWC blog
posts a while back:
http://software-carpentry.org/blog/2015/02/instructor-debriefing-2015-02-10.html
I have been using this for the past many workshops I have taught (both
for the shell and for the git lessons) and it is always a huge hit
with the students. I also do a similar thing with hard links to the R
files I am editing during R lessons.
Best,
Naupaka
On 29 Apr 2015, at 4:35, Juan Nunez-Iglesias wrote:
Lex,
That's a great idea re: bash command history. I thought I could hack
something together quickly (by following the ~/.bash_history file),
but it's not trivial to ensure every command is written to that file.
=\ Either way, that would be a fantastic teaching tool.
Juan.
On Wed, Apr 29, 2015 at 8:06 PM, Lex Nederbragt
<[email protected]>
wrote:
Hi,
I observed (helped out at) a SWC workshop once where RStudio was
used for teaching. The big advantage was that the students could see
the previous commands in the top left part (frame). This helped a
lot in allowing students to catch up. The IPython notebook allows
this to a certain extent, but with big output, an instructor needs
to scroll up to show students that want to review previous commands.
I agree that the Rodeo feels in beta-stage, but I think it has great
potential.
In fact, I wish someone would make such an application to help teach
the shell, where any output that is more lines than the terminal
screen is long, makes previous commands get out of view...
Lex
On 27 Apr 2015, at 19:51, Ted Hart
<[email protected]<mailto:[email protected]>> wrote:
I briefly tried out Rodeo over the weekend. It seems like a less
polished version of RStudio Server. I suppose one major selling
point is that it could be installed on a server and then students
could connect to the server. Then instructors wouldn't face the
vagaries of installing different versions, libraries, etc... But I
personally think it lacks many of the features of a full powered IDE
(breakpoints, debugging etc...) but no serious advantage over
iPython notebooks. Personally I'd rather teach in an iPython
notebook, but if an instructor really wanted a clone of RStudio,
this is a pretty good approximation.
T
On Mon, Apr 27, 2015 at 10:31 AM Jason Moore
<[email protected]<mailto:[email protected]>> wrote:
What makes Rodeo better or different than all of the other IDEs that
support Python?
Jason
moorepants.info<http://moorepants.info/>
+01 530-601-9791<tel:530-601-9791>
On Mon, Apr 27, 2015 at 8:38 AM, Daniel Chen
<[email protected]<mailto:[email protected]>> wrote:
Hello everyone:
Yhat just released a python IDE called Rodeo. It's like rstudio for
python. I'll be using this for the next few days, but so far I like
it better than the notebook (at least for exploring data).
I remember Greg being jealous of Rstudio has a teaching tool. Maybe
we have a Python equivalent?
http://blog.yhathq.com/posts/introducing-rodeo.html
- Dan
_______________________________________________
Discuss mailing list
[email protected]<mailto:[email protected]>
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________
Discuss mailing list
[email protected]<mailto:[email protected]>
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________
Discuss mailing list
[email protected]<mailto:[email protected]>
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
