Rmarkdown ioslides turn off fade-in behavior on .build - r-markdown

When I knit my .Rmd files to ioslides, the incrementally built bullets fade-in painfully slowly. The main title does the same thing. Can I turn off this "fade-in" behavior somehow (everywhere if possible, and at least on my .build bullets)?

Related

How to organize a R project structure in interaction with using R-markdown

I've been reading everywhere about the need to organize your R projects and also to use Rmarkdown.
I see an incoherence I can't solve.
Suppose I set for the following standard organization:
Project
data
raw-data
code
docs
out
reports
and also home of setwd().
Now I want to use Rmarkdown with my main project file called My_project.Rmd
I create it at the root project level, then I get at every knit rendition 2 directories created My_project_cache and My_project_files on to of every .hml file rendered that conflicts with the above structure.
This is very impractical.
I tried setting the options of output to avoid this, per this tip, but it fails on the cache directory, and I did not succeeded in setting Knit options to bypass it. And no-one seems to be bothered by this question making the solution look like a dead-end.
The other solution is to put My_project.Rmd directly in reports/ but it feels a little awkward and on top of that it breaks the above project structure by imposing ../ paths everywhere.
The third solution is to work with Rmd format, only at the end of a project, but this seems a little defeating the purpose of documenting everything neatly in the first place.
There may be a 4th solution using R Notebook feature, but it works until you decide to try to finalize your "final" document , which of course is never really final.
What am I missing here ?
For reference, I'm using RStudio on a Mac.

How can I improve the usability/readability of Toad

I have installed Toad 12.8 and I had a pretty big mistake in executing code. I executed code out of sequence, despite triple checking my work. Some how the tab I had selected was unselected and another script was ran. I still wince in embarrassment a week later.
I just wanted to know if there are ways to improve usability/readability of Toad. For instance, can I highlight the tab I have selected? Can I review scripts in a viewer to showcase scripts that I have open and manage which have been executed and not?
I have changed the tab style to 'Flat Buttons', which better showcases the script you are viewing among the many you have open, but thats just 1 small change.
Anyone else have options they like to use? Im not seeing a lot of options here under View Options...
I'm on 12.5. Current tab is highlighted (i.e. has a different color than other tabs). You could, though, change the window background color (by default, it is white).
Open "Configure TOAD options" and search for "TAB", you'll find quite a few options in there.
If you want to review what you've executed, navigate to "Query Viewer" tab in the Editor window. Sort results by "Start Time" in descending order and it'll show what you executed, when, how many time was spent on it, how many rows were affected ... quite useful.
As of running code you didn't mean to: well, what can I say? I'm sorry you did that, but - after all - it is you who should pay attention to what you are doing. No highlighting will solve that problem (also know as we have met the enemy, and it is us).
Something I like to do to is to change the color of TEST vs PROD in order to make them stand out. On the session/new connection window, scroll right and you'll see a "color" column. I set PROD connections to Red and TEST to Blue. Give it a try, maybe you'll like it for a visual reminder for the environment you are working in. It will change the status bar background color so it's not that intrusive.

Code Coverage Results: Export to Excel

There is a 'Code Coverage Results' window in Visual Studio which allows you to view the contents of a *.coverage file (generated by one of the VS performance tools). I was wondering if there was a way to export the Code Coverage Results to excel for further analysis. The tools in the Code Coverage Results window seem somewhat limited and was wondering if I was missing something.
I've queried quite a few statements and cannot find the answer I was hoping to find. There were three main questions which did not seem to have answers:
Can you search the data within the code coverage results? The typical VS search will not allow you to search within the Code Coverage Results window
Can the Code Coverage Results be exported to excel, or as a *.csv file? If not, then can the *.coveragexml file (which seems to be the only export option) be imported into excel in a way that i would get a table similar to the one in the Code Coverage Results window?
Is there an 'Expand All'/'Collapse All' button for the Code Coverage Results window? It would be nice to be able to expand all of the Code Coverage Result tree if possible ... or at least be able to expand a group of branches which have been expanded.
Any suggestions/input would be useful.
What you can do is this:
Export to XML (I renamed it to ...coverage.xml so it is recognized as an XML file but not sure if that's necessary)
Load with Visual Studio
Format in VS (Ctrl+K, Ctrl+D)
Now you can open this in Notepad++ for example (or any other good XML viewer). There you choose to close or open all text blocks.

Sublime Find and Replace without having to click save

When I do a global search/replace in a project, Sublime will automatically open all the files involved, and not save them. I then have to manually save every single file.
Is there a way to have Sublime automatically save all the changes that have been done, and not open the files that where not previously open?
Thanks in advance for anyone who can help me with this.
http://www.sublimetext.com/forum/viewtopic.php?f=3&p=40348
I think it's Option + Command + S(Mac) or Command + Alt + S(Win).
Just performed a similar task with the free Visual Studio Code. Replace in Files without opening files and fast. Just made 60k changes in just a few minutes.
Robust if awkward.
While it doesn't change the fact that Sublime Text doesn't seem to be the best tool for this job, here's a practical workaround procedure I've come to rely on. It's reasonably slow but painless if done correctly. Memory consumption impact seems negligible, if you're wondering. The ballpark of my use cases is up to about 10k files in up to a handful of minutes on a mediocre memory-cramped machine using Sublime Text 3.2.2 (3211) on Windows 10 Pro x64.
Requirements
You'll need the package SideBarEnhancements to be installed.
…which in turn relies on Sublime Text 3 or newer as of writing this.
Procedure
(Could probably be deferred until step 3.) You add the directory A that you're going to operate on to the project sidebar.
You initiate your batch replacement operation over numerous files inside directory A.
Sublime Text takes its time to open numerous tabs belonging to directory A recursively and perform replacement in each.
You right-click on the directory A in the project sidebar to bring up its context menu and choose "Save Views".
Sublime Text takes its time to save each tab belonging to directory A recursively.
You right-click on the directory A in the project sidebar to bring up its context menu and choose "Close Views".
Sublime Text takes its time to close all tabs belonging to directory A recursively.
Disclaimers
Warning
Do not make the mistake of skipping step 3 or you'll effectively become stuck in a GUI loop of writing confirmation dialogs defaulting to "Yes" for however many thousands of files you're operating on.
If you decide to abort operation between steps 2 and 3 — your best course of action, is to back the files up on disk, proceed with the outlined procedure and then restore the backup.
Caution
All of the tabs belonging to the directory you'll operate on will be closed by the end of this procedure. If you need a substantial portion of them to remain open throughout replacement — consider organizing the files contained into a sub-directory structure conducive to cherry-picking.
General advice
As a rule of thumb, before proceeding with this procedure, it would be wise to check if the required context menu entries are in fact present (greyed out or not) in your combination of editor+package versions. And to be on the safe side, you might want to back up your data and Sublime Text session before massive operations.

Notepad++ SourceCookifier plugin very slow on large C++ headers

I like to browse through my C++ projects in Notepad++. I use the SourceCookifier Plugin in order to easily jump in between definitions on large files. However, if I load a large C++ header file (around 30.000 lines), with a lot of #define and typedef declarations inside, it seems to hang and takes a long of time to load.
Does anyone know if there is any option one can set to make it faster or can this plugin generally not load so many definitions?
You can accelerate everything by throwing your project folder into the SourceCookifier panel while (and this is the important but badly documented part) pressing a modifier key (shift, ctrl or alt).
.. for importing INCLUDE files. But you have to additionally either
press the CTRL, SHIFT or ALT key while dropping a file or folder into
the treeview.
Or even smarter... separately only add your large define/typedef sources like described. It will result in a performance boost, since their symbols won't be listed in the tree view anymore, but SourceCookifier will still navigate you there, when hitting "Go To Definition" on one of their symbols somewhere else in the project.
I also sometimes use to add header files with several thousand defines to a SourceCookifier session. Without pressing ctrl-key it takes up to 5 mins per file, but with pressing ctrl-key it only takes 1 second!
EDIT/
Adding source files without pressing ctrl-key:
"Go To Definition" functionality? Yes.
Symbols shown in tree view as subnodes of source file node? Yes.
==> Not recommended for laaaarge source files.
Adding source files with pressing ctrl-key:
"Go To Definition" functionality? Yes.
Symbols shown in tree view as subnodes of source file node? NO.
==> Recommended for laaaarge source files.