In the introduction to his book R packages, Hadley Wickham provides a neat function for making sure that everything is set for writing your own R extensions, by simply running the
devtools::has_devel(), which, if all goes well, should evaluate to
This did not work out for me and I had to fix this problem on 2 different occasions so I felt I need to share this info in case there are others also stumped by this hurdle.
The fix I found – after a full sweaty day – was in this conversation on GitHub and I would like to break it down very quickly:
- Make sure you have installed Rtools from CRAN
- Make sure that Rtools/bin as well as Rtools/MinGW/x64/ are added to your system PATH (if you don’t know how, click here)
- In addition, it is recommended that you install LATEX (the link is also found on the Rtools page mentioned on No. 1)
- Run the following lines of code
install_github("hadley/devtools") # to get the latest 'pre-CRAN' package updates
has_devel() # output should be TRUE
Like I said, I had this problem on 2 different machines (Windows 7 and 10) and the same fix worked on both of them.
Well, I just have to share this with whosoever is desperately looking for a solution to this problem and happens to stumble across this post.
It’s not easy being a newbie in any thing, and computing is no exception.
I have written a small program that I will be using for my work in the office and which would also benefit a few staffers. I wrote it in C++ and compiled it using Visual Studio. However, I couldn’t find the executable file (*.exe) anywhere on my computer!
I went over to the MSDN site, as well as StackOverflow, looking for a solution but there was none in sight. To make matters worse, I discovered that MANY beginner programmers were facing the same issue.
Then I found this video on YouTube – and voilá! – problem solved. The answer to my question is ridiculously straightforward; indeed, ignorance is very costly.
If you’re in a bind like I was, I hope this works for you the way it did for me!
This is a good blog. I use IDEs, but my take on them is this: It makes a lot of sense for learners to start with manual before moving on to automatic, because the day you’re forced to drive manual, you may find yourself unable to do so.
IDEs are simply programs to write programs. They are generally editing environments with tools
to help programmers write code quickly and efficiently. As an example, we can create PHP-driven
web applications using a combination of Eclipse and PHPEclipse. Core features typically include:
• Code completion or code insight: The ability of an IDE to know a language’s
keywords and function names is crucial. The IDE may use this knowledge to do such
things as highlight typographic errors, suggest a list of available functions based on the
appropriate situation, or offer a function’s definition from the official documentation.
• Resource management: When creating applications, languages often rely on
certain resources, like library or header files, to be at specific locations. IDEs
should be able to manage these resources. An IDE should be aware of any required
resources so that errors can be spotted at the development stage and not…
View original post 485 more words
My office colleague, “R”, is always on my case: “Ha! I’m always amazed to see you using your command line!” Well, remarks like this, kinda make me feel, geeky, but trust me, I’m no nerd – just some curious cat. It may make one look like they have special powers, but I’m just blessed that the first time I started using (or rather, fooling around) with computers, it was at the command line.
It never did much with it, but that start spared me from the irrational trepidation that many people have towards the console. The only DOS commands I knew back then were
ROBOCOPY – of which I only used the first three. So, I wasn’t really a user. A few years down the line, atrocious internet connections forced me to do
pinging. But that was it. I’m not a Special One.
I use the command line interface (CLI) nowadays for one simple reason: I’m lazy. Maybe I became lazy since I started doing a lot more programming. Nowadays I work principally from Windows Powershell, which is both a CLI and a scripting environment. It can’t get better than this. But here’s why:
- It saves me tons of time: After setting up my Powershell profile, whenever I want to read my Bible, I just type in
bible. When I want to log onto my WiFi, I pass the instruction
smile, and when I’m done I tell my machine to
smileoff. How long did it take me to write the script that enables me to do this? Just a few minutes. How much time is it saving me? Cumulatively, hours!
# Alias: smile/smileoff. Command for controlling my personal Wi-Fi
(netsh wlan connect name='Smile@Maverick')
New-Alias -Name smile -Value Connect-Smile
(netsh wlan disconnect)
New-Alias -Name smileoff -Value Disconnect-Smile
- I have a lot more control over my computer: As one begins to use the command line more often, one gathers more and more experience on its features and the different possibilities. I know feel much more in control when I’m using the computer and I can customise it a lot more, so that it actually is MY computer. As I pick up one or two scripts (or scripting skills) from the internet and apply them to my system, I can make it bend a lot more to my whims and caprices, and also selectively shut out prying eyes.
- I gain more expressivity: I read this blog on this issue and I agree with the author – since I started using the command line, almost exclusively, when interacting with the operating system, the mindless mouse clicking has turned into an actual semblance between me and the computer. For good measure, I included a greeting message in my Profile, so whenever I fire up the program, I get this greeting. Are these the beginnings of AI for me (á la Mark)?
- I have less stress after upgrades: I remember the jump I had to make from Windows XP/7 and Windows 8. The difference was so clear and the learning curve quite steep. I recall having to make the same leap from Windows 2000 to XP. Why, oh why, Microsoft??? I upgraded to Windows 10 a few months ago, but guess what? I never had to bother about the new interface. I can count on one hand the number of times I have used the Start Menu. When I first saw it I was like “What the heck?! I will operate from my blue screen, thank you very much.” On a serious note, if you can learn to carry out your most mundane tasks and launch your commonly used programs from the command line, you will save yourself hours or even days and weeks of trying to figure out how to use your PC’s GUI after major operating system upgrades because the CLI stays basically the same. This works across platforms to (in a way); the other day a friend asked me to do something on her Mac and being a Mac-ignoramus, I opened the shell, BASH, and worked from there. She was just staring at me with utter amazement!
- I can run many programs and utilities in the same window: I discovered this one only recently and I’m exploring it. Just like I mentioned about
ipconfig earlier, I found out that I could run Git and R right there in the CLI. So, when I want to just do a quick commit, I run
gitcmd, which I pre-configured in my Powershell Profile to run
git-cmd.exe. Alternatively, I could have pointed the Git directory to
$PATH (for more information on how to do this in Windows, read this article).
This post is getting too long, sorry. There are other benefits you can discover on your own on the internet. All I am saying to those who are so accustomed to clicking-and-pointing: Learn to use command line, especially if you’re a professional or in any kind of technical field. It will save you a lot of hassle once you get the hang of it.