This issue has bothered me for a while. The tab key does not produce anything when typing in the content part of any Rmarkdown file BUT works pretty well in the code chunks. Is it a bug or I need to setup something ahead? It's very annoying to often type spaces in the yaml and when creating the bullet points.
I'm using Rstudio Version 1.3.314 and updated Rmarkdown package directly from the github repo on a Win10 PC.
Related
I am trying to replace the Inconsolata font with its older version in IntelliJ (the newer version added things that I'm not happy with)
IntelliJ seemingly refused to remove a font that I wish to be removed.
The font in question is Inconsolata, and the picture below shows me trying to delete it. It works, at this stage.
However, after doing that, and restarting the PC, IntelliJ insists that the font exists.
It will give a strange name to the font, but the entry exists. This causes problem on my end - there's some reference caching the IntelliJ is doing, and if I were to replace the font with the older version, it'll still be using the newer cache, but will give a strange output if the cache is pointing to something that doesn't exists.
I've tried
Deleting the settings folder
Reinstalling IntelliJ and then restarting
Is there a way to delete a font in IntelliJ properly?
It looks like Windows doesn't properly delete a font. Unfortunately, this causes problems for some apps.
The fix
Head towards C:\Windows\Fonts from your terminal. Do not use a file browser, as that will open up the control panel item.
Delete all traces of inconsolata (There was Inconsolata-Bold.ttf, Inconsolata-Regular.ttf, inconsolata.otf) using a terminal
Now your IDE will no longer have the Inconsolata font.
This problem is very similiar to those:
"The binary code for the script is not found" and
The binary code for the script is not found” ssis
I have an SSIS project with multiple script files. SSIS claims that one of them has no binary even though there should be. There are no code errors, and I can build it properly. I suspect it's a VS bug because this problem appears and disappears randomly. What I mean by that is that this script is working fine, I open it to see the contents, close and suddenly this error happens! So I open it like 20 times, and it (without me doing anything) repairs itself! Any ideas on how to make it work better? It seems (though I can't confirm with 100% certainty) that this problem happens when you save the SSIS script (as in use ctrl+s) instead of simply exiting from the VS.
Things that I have tried that sometimes work:
Restarting Visual studio, opening the script without doing anything, closing it
Adding a small change to the code, exiting
Removing and adding breakpoints
Going on my knees in the direction of Redmond, Washington, and chanting the names of M$ presidents while opening and closing windows in the building to the rhythm of the windows starting sound
Randomly closing and opening the project, as well as going through items in the script component menu
Things that don't seem to work: rebuilding project, cleaning project, you know the standard stuff
I've found a solution that OFTEN works. Notice the usage of often.
1) Try restarting your computer.
2) If it doesn't work go to your system temp files directory, and find the location of SSIS temp projects (you can also open the script, right click on C# project, explore in windows explorer). Delete the project. (Make copies before deleting just in case). Start Visual studio, and once again edit script, close, hope it works. DON'T SAVE THE SCRIPT PROJECT BEFORE CLOSING! JUST CLOSE!
Note that for the second step, you can also try using a cleaning tool, like CCleaner of similar.
In my case, I did some idiotic changes to main package solution config manager and tried changing the "Target SERVER Version". That wiped out all the scripts project from each packages. Then I came to know that it is auto-generation everytime we open. That means each package is storing script project within it. But now I don't know why its not generating while pressing on "Edit Script button" (really pissed!)
Thank for suggestion. In my case, I did some idiotic changes to main package solution config manager and tried changing the "Target SERVER Version". That wiped out all the scripts project from each packages. Then I came to know that it is auto-generation everytime we open. That means each package is storing script project within it. But now I don't know why its not generating while pressing on "Edit Script button" (really pissed!)
"Lucky I am" . got an fix! Each package file was internally not linked with their Script.cs. So I opened each package file in Notepad++ and found Script.cs content within. I recreated scripts.cs in each package (steps) and pasted the content from notepad++. And it worked!!!
I created a simple XSLT file using Visual Studio 2010 which works just fine on my machine. However, when my colleague tried to run it on her pc with Visual Studio 2013 it informed her that the file could not be ran and generated this message:
Attempt by method 'System.Xml.Xsl.XslCompiledTransform.Load(System.Type)' to access field 'System.Xml.Xsl.CompiledQuery.Query.staticData' failed.
However, when I did a simple copy of the text in my file and pasted it into a new blank XSLT file on her machine (with VS 2013) and saved it with a different name, then it runs just fine even though it is completely identical to my original. It's as if there's some reverse compatibility issue going on. Has anyone else experienced this and, if so, do you know of any permanent fix so we don't have to copy and paste all the time? The XSLT file is being run from a local drive.
Neither of the two answers here worked for me, but one of the workarounds in the now-deleted MS Connect bug report has worked for me on multiple occasions:
Open the XSLT file's properties in Windows Explorer
On the General tab, look for an Unblock button.
Click it, then click OK
It seems like there's some kind of security feature in play here that detects that the file originated from another machine and it's fouling up something in the XSLT debugger.
Changing the encoding from UTF-8 to ANSI (or any other encoding) and back to UTF-8 fixed it for me. Not much different than creating a new file, but a little bit easier.
Encoding didn't work for me, but I've got a workaround. I get this error in VS 2015 so this bug has been around a while.
Don't do it this way: To test transforms I usually have the xslt open with the cursor in it and then, on the top menu, click xml->start xslt debugging->browse to the xml file
Do it this way: do it the opposite of above, that is, have the XML file open (not the xslt) then click xml->start xslt debugging->browse to XSLT file.
Not sure why it works, but it does.
The issue for me was that the xslt file was on a network drive. Moving the file to a local drive on my machine fixed the problem.
Got the idea from Microsoft's feedback forum
For future visiters, none of the above solutions (even in Microsoft forums) didn't work for me. I did try in every VS version (including both professional and community versions) and nothing changed.
The only thing worked for me is:
1- Copy all the text in the XSL file
2- File(top left corner) -> New -> File -> XSLT File
3- Paste the text and run
This is the only way that worked for me.
I am looking for functionality similar to what I get with sublime text (with the git-gutter plugin), such as the image below. In the gutter I can see I deleted some lines(red) and changed some lines (yellow).
I recently found the GitDiff plugin for xcode, which does pretty much what I want.
Xcode plugins can be installed and removed using Alcatraz
When you save a project, Sublime Text will create a .sublime-workspace file. In this file, there is an array of buffers, and for each buffer there is a color_scheme property. This is set to whatever color scheme was chosen when the buffers and workspace were created.
I recently changed my theme and color scheme in my user settings file. How can I refresh all of my project's workspaces so that way it uses my new color_scheme provided in my user preference file without needed to edit each project's workspace file one-by-one?
Expanding on the answer given by Tot you can do this for all views in all windows that are open by using a nested list comprehension (remember this is Python so we can be pretty flexible):
[ v.settings().erase("color_scheme") for views in [ w.views() for w in sublime.windows() ] for v in views ]
This way you don't have to run the command in each tab individually.
The only way I found to reset tabs to user's chosen color scheme is to enter this in the console :
view.settings().erase("color_scheme")
This will reset the color scheme of the selected tab - unfortunately you'll have to do it for each tab. But it's still quicker than closing and reopening the tab.
I only have this issue with Sublime Text 3 on Mac OS X.
Source : https://www.sublimetext.com/forum/viewtopic.php?f=3&t=19310
P.S. : If you've just updated your color scheme file, you'll sometimes have to execute this command twice. Just type the up arrow in the console to write the last command again.
Windows 10 AppData-related Solution
Please make sure that you are in a similar situation as me before trying this solution (see below). Steps:
Note the language and package that the Error loading colour scheme reports (my case was: markdown and MarkdownEditing).
Go to your AppData directory (type %AppData% in file explorer address bar).
Open directory Sublime Text 3, or whatever your version is.
Open the .sublime-settings file that matches the language from step 1.
Remove any lines that refer to the package you noted from step 1.
Remember that this file should be a properly formatted JSON file when you remove lines manually. Save this file and restart Sublime Text.
Background
I've decided to post here in case some of the python script solutions didn't work for you and your situation is similar to mine. I'm using GitHub to sync my Sublime Text AppData (Windows 10), in order to keep my workflow settings the same on multiple machines. Recently, I noticed that when I uninstalled a certain package on one of my machines, I accidentally merged some configuration files for that non-existent package on my other machine. This resulted in a persistent Error loading colour scheme, in particular for me when changing syntax to markdown (the package was MarkdownEditing for reference).