I like to add a new-alias command to my Microsoft.PowerShell_profile.ps1 file that makes the “julia” command available in my powershell session.
From: [email protected] [mailto:[email protected]] On Behalf Of Tony Kelman Sent: Tuesday, June 21, 2016 12:46 PM To: julia-users <[email protected]> Subject: [julia-users] Re: Julia 0.4.6 Windows 32bits not run I disagree, adding Julia's bin/ directory to the Windows PATH is generally a bad idea. Any library that depends on the same set of libraries that Julia does, but wants them in a different configuration, can easily hit compatibility problems if Julia's dll's are all added to the path, and Windows puts dll's and exe's in the same location. You can write a wrapper script or similar, or set up a terminal environment in a way that you temporarily add Julia's location to your path only when you need it. On Tuesday, June 21, 2016 at 10:17:40 AM UTC-4, Андрей Логунов wrote: I had similar difficulties when having upgraded from 0.4.5 to 0.4.6 under Win10 x64. The REPL console did not run. But then i recalled that i'd added a value to the users's path variable, and it turned out to be the reason for the porblem in question for when i substituted 5 with 6 the problem vanished. It'd be much better if the path value was added/removed automatically during installation. вторник, 21 июня 2016 г., 22:15:21 UTC+10 пользователь Tony Kelman написал: Please provide more information. Exactly what error do you get? Can you try to run julia.exe from inside a command prompt if that provides more of an error message? On Tuesday, June 21, 2016 at 6:03:58 AM UTC-4, alx wrote: Hello, Julia 0.4.6 Windows 32bits, is installed correctly but does not run, Wrong configuration Windows XP
