Please be aware that some listings have been temporarily delisted from our marketplace in order to improve the security of the platform. We apologize for any inconvenience this may caused.
For more information on this matter, please visit #1.
If you are a listing owner and would like to have your listing(s) reinstated, please open a ticket at https://gitlab.eclipse.org/eclipsefdn/it/websites/marketplace.eclipse.org/-/issues.
Thank you for your understanding and cooperation.
ShellWax
Details Group Tabs
Sunday, March 26, 2023 - 03:40
Reviews Sign in to post reviews
broken and slow
Submitted by Elatllat Mising name on Mon, 2020-08-17 15:08
node.js
Submitted by Mario Charest on Fri, 2020-05-08 12:21
Version: 2020-03
Ubuntu 20.04
openjdk 11.0.7
Missing node:
Could not find node.js. This will result in editors missing key features.
Please make sure node.js is installed and that your PATH environment variable contains the location to the `node`executable.
But node is installed ( with apt install nodejs), node is in the PATH. I can start it from the shell, node lives in /usr/bin/
Suggestion?
error after installation: Missing node: Could not find node.js
Submitted by Anselm Distelrath on Wed, 2020-01-15 05:53
Windows 7
Eclipse IDE for Enterprise Java Developers.
Version: 2019-12 (4.14.0)
Build id: 20191212-1212
Error message:
Missing node:
Could not find node.js. This will result in editors missing key features.
Please make sure node.js is installed and that your PATH environment variable contains the location to the `node`executable.
What should be done to correct this?
Re: Missing node: Could not find node.js
Submitted by Alexander Kurtakov on Fri, 2020-01-17 06:07
Install node.js (https://nodejs.org/en/) locally on your machine and make sure that 'node' executable from it is on your PATH. If you're on Linux you can try https://github.com/flathub/org.eclipse.Java .
How to use shellwax in eclipse to debug the bash script ?
Submitted by Prashant Adlinge on Tue, 2019-12-31 13:29
Not able to debug the shell script as that of shellEd.
Is there any document for the same ?
Eclipse freezes while opening a .sh file
Submitted by Alex Mattern on Wed, 2019-11-20 10:25
I do not recommend this tool as it causes eclipse to freeze for about 20-30 seconds upon opening a .sh file. During the freezing time Eclipse says that it is doing something with Bash Language Server.
I am unable to log into Github due to firewall and therefore cannot post any associated support ticket there.
Re: Eclipse freezes while opening a .sh file
Submitted by Alexander Kurtakov on Thu, 2019-11-21 09:23
Is this happening on latest Eclipse version? I remember such issue but it was an issue in LSP4E which has been fixed a release or two ago?
Re: Re: Eclipse freezes while opening a .sh file
Submitted by Alex Mattern on Thu, 2019-11-21 21:58
I have already self-updated my eclipse version to the newest version. So the newest 2019 version is where the slowness is occuring.
Fails without dependencies
Submitted by Philippe Cloutier on Wed, 2019-08-21 09:34
This depends on Node.js and does not install it automatically. Eclipse will work if Node.js is missing, but ShellWax will not help.
Problems with activation of ShellWash
Submitted by Gregory Miecznik on Fri, 2019-07-12 13:56
Hi,
I just installed ShellWax into Eclipse IDE, Version 2019-03, on Linux RH7, but I can't open a project with shellWax - it is not listed in File->New->Projects, nor in File->New->Other.
What else do I need to install or customize to make ShellWax project visible.
Thank you
Greegory Miecznik
Re: Problems with activation of ShellWash
Submitted by Alexander Kurtakov on Mon, 2019-07-15 08:09
There is no need for specific project. Just open *.sh file in any kind of project (with Generic Editor in case you have other editors too). and that's it.
Re: Re: Problems with activation of ShellWash
Submitted by Hubert Degaudenzi on Fri, 2020-01-03 08:44
Well, I am afraid that doesn't cut it. Most of my shell executables don't have any extension (as it is recommended generally on *nix). I then need to be able to switch explicitly to the new shellwax editor.
It is true that ".sh" extension are somehow used but in principle this is reserved for scripts which are sourced by a specific shell (and not executed).