I'm using Windows 7 and trying to use Grunt for workflow. I've never used it before and am trying to make sure everything is installed and running correctly. I've installed everything (Node.js, Ruby, Sass, Git, yo, Bower, Grunt) and everything up as far as Grunt is working fine. I'm testing out Grunt on a previous project from my company that works on all the other machines in the office (both PC and Mac) and I can start it watching my files, but when I edit a .scss file that is being watched and save it I get
Encoding::UndefinedConversionError: "\x9D" to UTF-8 in conversion from Windows-1252 to UTF-8. Use --trace for backtrace. Warning: Exited with error code 1
I've tried forcing all .scss files to encode UTF-8, changed defaults on Sublime Text to always use UTF-8, checked filenames for unusual characters, and it hasn't fixed anything. Any suggestions for what else I can try? Has anyone else had this problem?
Related
I'm a noob at setting up LaTeX and I'm completely stuck. I had a broken MikTex + TexStudio setup that the previous owner of my work computer left behind (I also mention that I recently upgraded from Windows 10 to Windows 11). Unable to fix it, I decided to just wipe out everything and start clean. I uninstalled TexStudio and MikTex (also deleted all the files in AppData, etc.) and I installed TexLive (and gave the PC a restart as prescribed) to use it in VS Code (which I already had). All the guides I found say that once I install the LaTex Workshop extension in VS Code, everything should work on it's own (or at least no one mentions that there are problems that could arise).
However, when I try to compile a tex file I get the following error:
11 [0x00002528] INFO latexmk null - this process (19956) started by 'Code' with command line: latexmk -synctex=1 -interaction=nonstopmode -file-line-error -pdf "-outdir=c:/Users/.../texfile_locationfolder" "c:/Users/.../texfile"
It seems that this is a fresh TeX installation.
Please finish the setup before proceeding.
For more information, visit:
https://miktex.org/howto/install-miktex-win
The fact that it mentions MikTex makes me think something messed up and VS Code is trying to use MikTex instead of TexLive. How can I fix this?
PS: I've tried to look at the settings for the VS Code extension, but there are dozens of settings options and, fairly enough, I don't have any idea what most of them do.
I found a fix: I went into the Environment Variables list and found that MikTex was still in there. After deleting everything related to MikTex in the PATH Environment Variables, all was working well. Yeey!
I had the same issue (on Windows). Resolved by deleting a MikTex folder, found by searching for MikTex in File Explorer.
Then, I deleted this folder from the recycling bin and restarted my computer. LaTeX Workshop detected TeXLive and works as expected.
Now I download Apache NetBeans 11 and after that, I CLONE my Git PHP Repository to Windows Folder, If I open HTML files via Notepad, everything is ok, but when I open it via NetBeans, I got wrong characters interpretation like this:
BAD
Ăšvod
RIGHT
Úvod
How can I solve it to use UTF8? When I open a file in example via PSPad Editor I see the encoding is UTF8, but the format is UNIX, not DOS, maybe this cause a problem
Edit:
When I use Netbeans 8.2 Characters are ok
Any sugestions?
This problem has been brought up a few times and I tried every suggested solution, but nothing helped.
What I have is a native module in a VS code extension. This works very well on Linux + Mac, but I cannot get it to load on Windows 10. Every time the extension is activated and tries to load the native module I get this error. What makes this so strange is that the native module works beautifully in a node session (in a Win command line). I checked what NodeJS version Visual Studio Code uses and installed exactly this version (x86, as vscode is still 32bit). I did an npm install npm -g, ran npm rebuild as well as normal node-gyp rebuild in my extension folder (or node module folder for node-gyp). Every time the module is built fine and works in a node session. Still I cannot get it to work in vscode. So I believe it must be something that has to do with the vscode app on Windows, just don't know what it is. For compilation I tried both VS 2013 and VS 2015.
Interesting here is also how node-gyp compiles the native module on Windows. It appears as if it uses a number of hacks, e.g. the compiled module crashs hard when using std::throw_with_nested (a C++11 feature). Another problem is the win_delay_load_hook.cc file, which contains a hack to make some weird situation work (this init fails on Win 10, so I had to disable that, this is a general DLL init problem not related to the vscode init). So it could well be it's just node-gyp on Win10 which is causing all the trouble. Yet, as I wrote, the native module works nicely in a node session.
What else could I do to find out what exactly is the problem? Is there a log file that shows exactly why the registration is not right? Is there a problem with vscode in general, on Windows 10?
I wanted to see how the code of FFMpeg works. So what I did is imported this project in eclipse. When I run the binary from the command line, it decodes the entire video without any problem and displays it as well. However if I run exactly same binary from the eclipse, it fails. It fails when the binary executes the following statement -
instance->display = XOpenDisplay (NULL);
Can anyone tell if there is any special requirement for running X11 apps in eclipse? I have linked the necessary libraries in the code. Also the binary works perfectly from the command line.
Had a similar problem developing with ROOT gui classes.
I solved the issue adding the env variable DISPLAY to :0 in the run configuration tab.
Last day I wrote a script so that my J2ee app could do backups. After deployment, the script was not working. I was wondering why, so I copied it from the deployment directory to my home dir. It was not even executing the first echo. That was strange because I tested the script on the very same machine. Later, after another SO question, I discovered that passing it through dos2unix would solve the problem. What happened was that I wrote the script on Linux, I did a simple copy and paste on Eclipse (running on windows), then I deployed the application (and the script was with /n/r the windows way).
How can I avoid this? I mean, I should write the script on Linux and not touch it at all (I'd like to have other options), or is there some special setting I could use?
You can set Eclipse to use Unix line-endings. http://www.sics.se/node/2108
Navigate to the Workspace preferences
(General:Workspace) Change the Text
File Encoding to UTF-8 Change the New
Text File Line Delimiter to Other and
choose Unix from the pick-list Note:
to convert the line endings of an
existing file, open the file in
Eclipse and choose File : Convert Line
Delimiters to : Unix