ReferenceError: autocb is not defined - iced-coffeescript

After migrating to new mac book computer iced coffee script starts work incorrectly.
When I run script ...
iced script.iced
... I got error ...
ReferenceError: autocb is not defined
... on the row:
exports.method = (arg1, arg2, autocb)=>
On old mac it works good. Iced coffee script versions are the same on both machines. On both machines I can call iced in terminal:
iced
iced> a = 3
3

The problem was in iced-coffee-script version. On old machine it was 1.6.3-f
iced --version ⏎
IcedCoffeeScript version 1.6.3-f
On new - 1.6.3-i. I installed 1.6.3-f and all starts work well on new machine.
npm i iced-coffee-script#1.6.3-f -g

Related

gatsby new command error "TypeError: rd.cursorTo is not a function"

Im creating a new site using the command gatsby new and im getting the following error
Cloning site template C:\Users\catal\AppData\Roaming\npm\node_modules\gatsby-cli\node_modules\yoga-layout-prebuilt\yoga-layout\build\Release\nbind.js:53
throw ex;
^
TypeError: rd.cursorTo is not a function
at Timeout._onTimeout (C:\Users\catal\AppData\Roaming\npm\node_modules\gatsby-cli\node_modules\create-gatsby\lib\index.js:5:852)
at listOnTimeout (node:internal/timers:564:17)
at processTimers (node:internal/timers:507:7)
Node.js v18.7.0
Im using windows 11
That was reported in gatsbyjs/gatsby issue 35426 in last April (2022), for now without conclusive resolution.
Try the create-gatsby locally first, following its readme, to check if this is a version issue (although node minimum version was set to 10).
If possible, try it also in a Linux WSL2 (for instance Ubuntu) VM, in order to check if this is related to the OS.
Upgrading my python version to latest fixed the issue for me.

Julia stdin error with Vim and AsyncRun in WIndows

I am using Vim in Windows with the plugin AsyncRun; when I try to execute a simple julia <filename> I get the following:
ERROR: error initializing stdin in uv_dup: Unknown system error 6 (Unknown system error 6 6).
This should be a julia-Windows issue since the same procedure in linux works correctly. Python and other languages also function with Vim & Asyncrun in Windows. Calling julia <filename> in either cmd or PowerShell executes as expected.
Is there a cli option or configuration for julia that can fix this?
EDIT: This bug has been fixed.

Python 3 installation, additional to existing Python 2 on Windows: Fatal Python error: Py_Initialize: unable to load the file system codec

Sorry if this is a re-post. I have been searching for hours and there are a lot of similar problems, but they are not exactly the same as my issue.
I have been working with Python27 on my 64bit Windows for a while now and I would like to install Python 3 in parallel.
I downloaded and executed the installation .exe of Python 3.5 for 64bit Windows. The installation worked without any errors and added C:/Python35 to the Windows PATH variable.
However, when I click on python.exe in the directory C:\Python35, instead of launching a python 3.5 shell as it's supposed to do, it pops up a Window saying
Python has stopped working
Also there is a command shell saying:
Fatal Python error: Py_Initialize: unable to load the file system
codec File "C:\Python27\Lib\encodings__init__.py", line 123
raise CodecRegistryError,\
^ SyntaxError: invalid syntax
Current thread 0x00001ce0 (most recent call first):
So appearently Python 3.5 is using the Lib directory of Python 2.7. This is probably related to the PYTHONPATH variable that is set to
C:\Python27;C:\Python27\Lib;C:\Python27\DLLs;C:\Python27\Lib\lib-tk
When I change the PYHTONPATH variable to
C:\Python35;C:\Python35\Lib;C:\Python27\DLLs;C:\Python35\Lib\lib-tk
Python 3.5 works, but Python 2.7 throws the error above.
Is there any way to permanently define that the command "python3" uses one PYTHONPATH and the command "python2" uses another PYTHONPATH?
Copying python.exe and renaming it to python3.exe didn't help. Neither did uninstalling and installing Python 3.5 again.
I have a lot of old jupyter notebooks that are written in Python 2.7 and it would be great if I could continue to use them by choosing different kernels (see here).

Kulture error - kpm command not found

I recently installed Sublime Text 3 with the aim of coding some C# on the Mac. I then followed the steps on http://www.omnisharp.net for the installation of the plugins and everything works fine until I try to build a simple "HelloWorld" project. Then I get the error
/Users/guevara/Library/Application Support/Sublime Text 3/Packages/Kulture/build.sh: line 21: kpm: command not found
I did check that I have the ASP.NET 5 KVM for MAC installed. Following the steps at http://www.enterpriseframework.com/post/2014/12/02/how-to-mac-vnext-step-by-step-setup-and-first-app also works, so the kpm command has been installed through Homebrew.
Any idea what I am doing wrong or why Kulture can't find the kpm command?
Thanks,
Alex
Look at the last line of installing kvm on OS X instructions at https://github.com/aspnet/Home:
Run command source kvm.sh on your terminal if your terminal cannot understand kvm.
but with the beta3 there's an issue in Kulture's build.sh, I have updated 4 1st lignes:
ver=`cat ~/.k/alias/default.alias`
add_to_path=$HOME"/.k/runtimes/"$ver"/bin"
export PATH=$PATH:/usr/local/bin:$add_to_path
[ -s $HOME"/.k/kvm/kvm.sh" ] && . $HOME"/.k/kvm/kvm.sh"

Jeet Framework: Got an error when trying to run Jeet 2:

Got an error when trying to run Jeet 2:
In CMD:
Compiling Stylus OK!
Saving Compiled Stylus OK!
Live Reload is on and listening!
Compiling SCSS ... Error!
I'm on Windows XP
Is there something with the Ruby installation on Windows?
I followed your tutorial on https://github.com/CorySimmons/jeet#quick-start
If you can type ruby into your Command Prompt and it doesn't return an error then you have Ruby.
You need to install Compass as well: http://compass-style.org/install/
In Windows command prompt you don't use the $ in front of the gem command! You just type gem update system, instead of $ gem update system.

Resources