I accidentally enabled tokenization for a large file, how can I disable it? - tokenize

I was opening a large .csv file and then a popup appeared saying: "tokenization, wrapping and folding have been turned off for this large file in order to reduce memory usage and avoid freezing or crashing."
I didn't think much of it and enabled it, but now everytime I try to open the file the window freezes. Is there a way to disable tokenization for this file?
I tried decreasing the max tokenization line length to disable tokenization for the .csv file. But, despite that nothing changed and it still kept crashing everytime I try to open it.

Related

Need to save twice with guard and livereload

When I save changes to a html file, the browser refreshes the page quickly and correctly. The first time I save changes to a scss file, the page starts to reload, but stops without loading any of the style sheets (although it does load images). If I save it a second time, the page reloads fully. Thereafter, most I only need one save. However, sometimes I have to do a second save in order to get it working properly again.
I am running rails v4.2.5.1, guard v2.13.0, guard-livreload v2.5.1, chrome browser v48 with livereload extensions 2.1.0.
It turned out that when I upgraded by hard drive from a mechanical to a SSD drive, this problem stopped occuring. Maybe something was timing out.
Best to open issues like that in guard-livereload. There are lots of moving parts here. And there are debugging options on both sides.
If an SSD drive fixed things, your editor may have had a lot of plugins activated during save - and if the "total save time" is longer for multiple files, things can get wacky. It could be lots of issues, so it's best to open an issue and ask for help. (There are debugging tutorials in Wikis too).

SourceTree stopped showing changes in XAML files

Under SourceTree, when you click a file on the list, it nicely shows the changes made to it.
Suddendly, my SourceTree stopped showing edits made into a XAML file. The window showing the edits is completely blank even if there are edits made to the XAML file.
Previously the edits were showing correctly but suddendly they stopped to be shown.
Is there a way to fix this somehow?
I found an answer to this.
The XAML file was very big with lot of changes and SourceTree was configured to view differences only up to a certain magnitude.
Under SourcTree, you can go Tools->Options and specify Size Limit (Text) and Size Limit (Binary) values. By increasing these values the differences in XAML are again showing.

VBA: set txt to be printed in Portrait mode

this time I'm fighting against a .txt file which doesn't want to be (programmatically) set to be printed in Portrait-mode instead of Landscape-mode (which is the default apparently).
Thing is I know how to do that with application like Word or Excel, but sadly enough I'm working on a device that has no Office at all.
I'm not providing any code at all since my problem is pretty straightforward, and I think I need a simple command in order to solve it. What I basically (programmatically) do in my subroutine is:
Open the file as #1 (I know this appears so '80, but I don't want to modify an up-and-running system, potentially having errors show up)
Write text to the file
Close #1
Save the file
Call text editor shell to show the file to the user
How can I then automatically set the print format to Portrait?
P.s.= I do not have the possibility to insert a userform or an object to print the txt file in "special ways", the user has to print the file from txt editor itself (wordpad just in case)
First to state the obvious: there are no print settings stored in text files (or indeed anything else except for the text). Print settings would be controlled within whatever you are using to print - in this case Notepad or Wordpad.
There are only very limited command line switches for Notepad and Wordpad, which unfortunately don't include page setup. In theory you may be able to automate setting portrait using SendKeys (see here and here) but if it is possible at all it's likely to be difficult and unreliable (focus and timing are two issues).
I can't see a good way round this within the parameters of your question. Adding an object within your application would probably have been the best solution. You might try looking for an alternative text editor you could install that is easier to automate. The only other alternative might be to set defaults within the printer drivers and hope that those stick when the user opens Notepad.

Every time i open a file with jedit text editor, large buffer warning pops up

I use jEdit very often to open my xml files. It so happened that once i tried opening a huge file(around 900MB file size, say xyz.xml) with jEdit, which failed.
From then on, every time i open any file(file size< 1MB) with jedit text editor, large buffer warning pops up:
The buffer is very large and jEdit may become unresponsive.
Can anybody help me how to resolve this problem. Is the only way out for this is to reinstall the editor?
JEdit doesn't support very large files very well. You can increase the size that JEdit is allowed to use inside of Java by changing java's heap size when you launch jedit like this:
java -Xmx512m -jar /FOO/BAR/jedit.jar
If increasing the memory size doesn't work for your largest files, you should try another editor. vim performs very well with very large files.

Have PDF-Creator suppress warning dialog not to halt build process

I have a msbuild script that includes creation of a few PDF's using PDF creator. It's the Convert2PDF.vbs that's being used, converting doc's to PDF's, and a while ago it stopped working and none seemed to take the time to fix it. So I looked into it and by debugging the script I found that it was in fact a document for which Word presented a dialog with information about contents being larger than the margins. This halted the entire thing since none could press this dialog during the auto-build.
So what I wonder is if there is a way to tell the PDF Creator script, via cmd line arguments or by altering the script, to suppress these kinds of warnings and just continue with conversion?
I solved this by creating a script in word that suppressed warnings if the given document resided within the build folder specified.