Netbeans has a terminal window but it requires cygwin to be installed. Since I can't install cygwin (it requires admin permission), is there a way to open a Windows command line prompt(cmd) inside Netbeans?
Cygwin does need to be installed for NetBeans to have a Terminal window, and by default administrator rights are required to install it. However you can override that default requirement using the --no-admin argument when you install it.
See section 2.4 of the Cygwin FAQs:
2.4.
Can I install Cygwin without administrator rights?
Yes. The default installation requests administrator rights because
this allows to set up the Cygwin environment so that all users can
start a Cygwin shell out of the box. However, if you don't have
administrator rights for your machine, and the admins don't want to
install it for you, you can install Cygwin just for yourself by
downloading setup-x86.exe (for a 32 bit install) or setup-x86_64.exe
(for a 64 bit install) and then start it from the command line or via
the "Run..." dialog from the start menu using the --no-admin option,
for instance:
setup-x86.exe --no-admin
(While this is an answer, I am unfortunately not in a position to verify that it actually works.)
Make sure your Netbeans is closed while installing the Cygwin plugin, preferably download the . msi file for your PC's architecture(32 or 64 bits).
Thereafter Click on the tools bar above then you'll seen open in Terminal that should provide a terminal at the bottom of your Netbeans program.
Most importantly ensure your Netbeans is closed during installation.
Related
I'm using wsl and it runs codes in vscode pretty fine and I have different libraries which I installed through pip and conda in wsl but when I run that code using vscode itself it doesn't recognize the libraries or even pip itself.
I don't have any other environment.
I should add that I installed the packages globally using conda install ... or pip install ... in base environment and I only have base environment and I run my code through code . and I also have python and remote wsl extensions installed in my vscode.
what can be the problem?
I don't have much personal experience with this, but I found some useful information in this Stack Overflow question (even though it doesn't utilize conda), along with https://code.visualstudio.com/docs/remote/wsl-tutorial#_python-development.
I also found this blog post useful, even if it doesn't cover WSL.
In short, make sure you:
Have installed the Python extension (by Microsoft) in VSCode. This is critical for being able to detect and select the Python interpreter. You don't mention having this in place, so I believe this is your likely problem.
You have done this already, but including it for others who might read this later -- Install the Remote - WSL extension (or the Remote Development extension pack) in VSCode.
You are also doing this already -- Start VSCode from inside your WSL distribution. Alternatively, you can start VSCode from Windows and then select the Remote WSL - Reopen Folder in WSL from the Command Palette (also accessible from the "Remote" Status Bar).
In VSCode, open the Command Palette with Shift+Ctrl+P, search for the Python: Select Interpreter command, and you should find your Conda environment in the list.
After selecting this, you should find that your project is using the interpreter and modules that you have installed via conda.
One thing I did to overcome this issue is go to Extensions -> Local (You should have two tabs there, Local and WSL:DISTRO) DISTRO refers to whatever DISTRO you're using, you will see that some of the local extensions are disabled in the current workspace (WSL) and there is a little cloud icon in the WSL:DISTRO tab that says install Local Extensions in WSL:DISTRO once you click that it will let you choose which extensions to install and you should be good to go!
There is a related question but it details the approach for WSL, in newer versions of Windows, the Linux distributions are not beta anymore and they are provided through the MS app store.
Where do I find the path to Ubuntu on Windows executable? (Not WSL.) I tried right-clicking on the icon to find Properties, but it is not there, it seems to be some special kind of a shortcut.
If you have multiple distros installed, you can read this how to launch one individually.
https://msdn.microsoft.com/en-us/commandline/wsl/wsl-config
However if you only have 1 installed, it will pick that one by default
There are three ways to launch and run WSL:
wsl.exe or bash.exe
wsl -c [command] or bash -c [command]
[distro] ie ubuntu -- this is the same as launching the installed app from the Windows menu.
In the first two cases, WSL must pick a distribution to run - a default distribution. If you don't explicitly set a default, it will be the first one installed.
So you can continue to simply use bash.exe
Open VSCode Settings Ctrl + , or File > Prefrences > Settings
User Settings will open up. Add the following in that file:
"terminal.integrated.shell.windows": "C:\Windows\System32\bash.exe"
Save and close the user settings file.
Enjoy bash in VSCode!
Just installed Eclipse Mars on Lubuntu 14.
While scrolling up and down in the console or editor - I get a kind of black rectangle covering some text, or the test is kind of twisted visually (lines become non-straight).
Anyone know how to fix this?
Haven't had this in previous versions of Eclipse on the same comp.
Exactly the same thing happened to me installing Eclipse Mars on Lubuntu 14 Toshiba Satellite notebook. I was really looking forward to the day of the Eclipse annual release of Mars and I was disappointed to be so disappointed with 5 minutes on installing.
Anyway, I can confirm that setting environment variable SWT_GTK3=0 by way of export does circumvent the problem. If you open a terminal and type "export SWT_GTK3=0" in the shell, you will also need to start Eclipse via the command line while remaining in the same shell. If you start Eclipse via a desktop launch icon, Eclipse will not see the SWT_GTK3 environment variable and the problem will persist. This is because environment variables in Linux are per-process and an application launched from the desktop is running in a different process to a shell process in a terminal.
So that Eclipse always sees the correct SWT_GTK3 environment variable after starting your machine, best you export SWT_GTK3=0 globally. To do this on Lubuntu, follow these steps:
Open a terminal window
Open the file /etc/profile for editing as sudo (e.g. sudo gedit /etc/profile)
Add the line
export SWT_GTK3=0
at the end of the file.
Save file, quit editor and reboot your machine.
Launch Eclipse Mars and hopefully your scrolling problem is fixed.
This worked for me but, as always, YMMV.
btw. You can check the SWT-GTK3 environment variable was exported after rebooting by opening a terminal window and typing the 'env' command. You should see
SWT_GTK3=0 in the list of environment variables and values that are displayed.
It seems like a new bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=469027
It happens also under Kubuntu. Anyway the workaround, at least for me, is to export the following environment variable:
SWT_GTK3=0
I solved my problem in Ubuntu 15.04 with Eclipse Mars by adding the following code in the start of data in the Exec option in eclipse.desktop (/home/.local/share/applications):
Exec=env UBUNTU_MENUPROXY=0 SWT_GTK3=0 /usr/lib/jvm/...
In that way you leave intact your OS preferences and act only on Eclipse starting script.
I have tried everything possible to install Netbean 7.3.1 on my Windows 8 OS supporting laptop. However, it was not going through from here https://netbeans.org/downloads/index.html.
This is the message I got after downloading all the software from mentioned link when tried to install for each download:
CRITICAll nullnull
I downloaded JDK (Name of the file: jdk-7u25-nb-7_3_1-windows-x64) and when I tried installing JDK I got an error says:
cannot find bundled JVM to run installer
Please can anyone share step-by-step instructions?
Open command prompt in the directory where your netbeans setup file is located. (to open cmd prompt, press shift and right click anywhere in the directory window and hit 'open command prompt here')
Now type the following command in command prompt
netbeans-8.0-windows.exe --tempdir C:\Temp --userdir C:\NBI
hit enter.
This is apparently a bug, though not in netbeans. Check out comments 9 and 10 for a possible work-around.
I just got this MSI wind netbook and tried to run eclipse on it. I installed JDK6 on the netbook already. Whenever I open eclipse there is nothing show up on the screen except a "warning sound" that alerts. What is the problem here?
ps.I just started learning java.
Most likely the Eclipse starter program can't find where you installed Java. Since Eclipse is a Java program, it needs a JRE installed (comes with the JDK typically) to run. Assuming you're running Windows on your MSI Wind, check to make sure the java executable is on your path in your computer environment settings (windows key + printscreen button, or windows key + pause button are the shortcuts to open the computer properties dialog if I remember correctly. Then go to advanced).
You can test if java is on the path by opening a cmd.exe shell window and typing 'java'. If it says it cannot find java, then you need to fix the path.
See this link for additional troubleshooting details: http://www.eclipsezone.com/eclipse/forums/t99010.html
You could try reinstalling the JDK. Perhaps having it on a different disk than the default (D: versus C:) is causing some trouble? It certainly isn't a problem with the hardware, I'm running Eclipse on Windows on an MSI Wind.
Use "Add/Remove programs" in the control panel to remove the java versions you have installed.
Then visit "java.com" and use it to install Java, and verify that it is working. You do not need more than that to use Eclipse.