Follow up from here (I personally find issues easier to track than comments on merged PRs ...)
I did see the link to pipeR.mk, but I didn't realize how it would be useful. It would be helpful to add a sentence or two explaining the relationship between make, makestuff, pipeR.mk, and shellpipes (unless this explanation already exists somewhere — although even then I might make an argument for duplication if the shellpipes GH page is likely to be a user's first point of contact ...
It also wasn't obvious to me that the link underneath "shellpipes" in the README went to the GH pages site; if I had moused over it, I would have figured it out, but more explicit navigational hints would be helpful.
line 1: what does this do/what is it for? (I can see that it adds all *.R files in the directory to the 'Sources' list, but what does that achieve? I can't find 'Sources' in the makefile tutorial link listed below, or in https://www.gnu.org/software/make/manual/make.html; - is 'Sources' a makestuff thing?
line 4: is this best practice? It's not the deprecated "magic" thing you refer to elsewhere in the docs?
I think I get that 'autopiper' covers the fact that base.rda depen on base.R and can be generated using the recipe $(pipeR); it took me an effort to figure this out. Maybe it would help to move the comment on lines 13-15 up toward the top of the file?
l. 17 "you should just need to plot" is a little bit telegraphic; you need you just need to use any base-R or ggplot plotting command in your R scripts? (It would be good to be pointed to/have more information somewhere about adjusting plot sizes, creating multiple plot files from a single script, etc. ...)
https://github.com/mac-theobio/useMakestuff is 32 commits ahead of, 2 commits behind dushoff/newMakestuff:master. What's up with that? (What is the relationship between useMakestuff and newMakestuff? (I think I see that newMakestuff is just an example. Would it be easier to have people use wget or equivalent to grab the file rather than cloning a repo, or do I not really understand how this works?
what is the incantation for figuring out the rpcall() line you need to add to a script to work with it interactively? Update: I figured this out, the documentation for ?shellpipes::rpcall says "command-line call as generated in .Rout.arg [sic]" (should be .Rout.args), that helped me figure out that I needed to look in *.Rout.args
Follow up from here (I personally find issues easier to track than comments on merged PRs ...)
I did see the link to pipeR.mk, but I didn't realize how it would be useful. It would be helpful to add a sentence or two explaining the relationship between
make,makestuff,pipeR.mk, andshellpipes(unless this explanation already exists somewhere — although even then I might make an argument for duplication if the shellpipes GH page is likely to be a user's first point of contact ...It also wasn't obvious to me that the link underneath "shellpipes" in the README went to the GH pages site; if I had moused over it, I would have figured it out, but more explicit navigational hints would be helpful.
Some questions/comments about https://github.com/mac-theobio/useMakestuff/blob/master/pipeRex.mk
makestuffthing?wgetor equivalent to grab the file rather than cloning a repo, or do I not really understand how this works?Do you have any suggestions for intros to make? https://makefiletutorial.com/ ? https://www.gnu.org/software/make/manual/make.html ?
what is the incantation for figuring out the
rpcall()line you need to add to a script to work with it interactively? Update: I figured this out, the documentation for?shellpipes::rpcallsays "command-line call as generated in .Rout.arg [sic]" (should be.Rout.args), that helped me figure out that I needed to look in*.Rout.args