Aptana Studio 3: How to get Syntax Highlighting of Shell Scripts *.sh - shell

Is there any "Formatter" / syntanx highlighting for linux shell script available for Aptana Studio 3 ?!?
I did find "shelled" but this seems only to work with eclipse and not aptana studio 3 standalone (and i could not get it to work in eclipse either)
Just simple plain syntax highlighting for *.sh files anyone?!?

Try ShellEd (http://shelled.sourceforge.net/project-info.html). It has worked pretty well for me.

Related

VS Code Terminal ignoring CR

My VS Code terminal is currently ignoring CR in linux shells (WSL-fish, WSL-bash, git-bash):
This doesn't occur when using those terminals natively. Any idea what might cause this, or how to fix it?
Although I wasn't using WSL in a remote fashion (just as a terminal) I tried installing the Remote-WSL extension when VS Code recommended it and that fixed the problem.

Gradle output not formatted correctly in VS Code's bash terminal

After a VS Code update a few weeks ago, Gradle's output started to display formatting character sequences like this:
.
I'm running VS Code on Windows and my bash shell is the one installed with Git. When running Gradle in bash directly (outside of VS Code) the formatting is correct. How can I fix this in VS Code?
How is VS Code invoking Gradle? Can you add the following to the Gradle command line that VS Code invokes?
--console=plain
See https://docs.gradle.org/current/userguide/command_line_interface.html
Set to plain to generate plain text only. This option disables all color and other rich output in the console output. This is the default when Gradle is not attached to a terminal.

No premake script(premake5.lua) found error

This is my first posted question so sorry for any mistakes I make. I recently was trying to setup Box2D on visual studio 2017 and I was told that you must use premake5 to first create the sample project and then you can begin using Box2D. The problem is that when I call premake5 vs2017 Downloads/Box2D-master/Box2D-master/Box2/premake5.lua in command prompt (I have also tried with vs2015 and vs2013 ), the program throws an error No Premake script (premake5.lua) found!. I have triple checked file paths but nothing seems to be working. Do you have any ideas?
This worked for me:
$ git clone https://github.com/erincatto/Box2D.git
$ cd Box2D/Box2D
$ premake5 vs2017

The colors are jacked up when using Vimdiff from Git in Windows

I have configured Git to use Vimdiff as its diff/merge tool on a Windows machine. It works, but the colors are messed up. First, it won't show any syntax highlighting, no matter how much I tell it to turn the syntax on and set the filetype. Second, the colorscheme is obnoxious, but when I do :colorscheme and hit CTRL-D, I do not see the usual list of colorschemes. None of the default ones are there, only ones that I installed myself.
The weird thing is that my colorscheme is fine, and I have all the expected colorschemes available, and syntax highlighting works, when I launch Vim directly from the command prompt, i.e. not through Git.
This makes it unnecessarily painful to review changes, and it is especially annoying when I'm trying to show a diff to a coworker. They are nearly unreadable. This has been bothering me for months and I can't figure it out.
Is there something different about having Git start Vim from just launching Vim? How do I fix this so can get my Vims behaving consistently?
Finally, after months, I figured it out. I thought I should share my findings in case anyone else was fighting the same battle.
Git for Windows comes packaged with its own versions of a number of programs. Apparently, Vim is among them. Doing a :echo $VIM shows that when Vim is started by Git, it is pointing to C:/Program Files (x86)/Git/share/vim. This Vim install seems different than my full Windows Vim install.
At this point you could solve the problem several ways, conceivably. One would be to repoint the VIM environment variable. Instead, I changed the path above to be a symbolic link to my actual Vim install:
C:\Program Files (x86)\Git\share>mklink /D "C:\Program Files (x86)\Git\share\vim" "C:\Program Files (x86)\Vim\"
symbolic link created for C:\Program Files (x86)\Git\share\vim <<===>> C:\Program Files (x86)\Vim\
Now the syntax highlighting is working, the colorscheme looks good, and it is much easier to review code.

Ruby prompt environment not connecting to gvim text editor

I am a Rails newbie and in following a video tutorial got to a point where I have to open Ruby command prompt environment.
The problem is I want to use gvim as as my text editor, but I can't seem to get it to work. It gives an error message that reads
gvim is not a recognizable internal or external command, operable programme or batch file
gvim may not be installed in your system. gvim is a popular open-source text editor.
You didn't mention which operating system you are using.
You can install gvim from http://www.vim.org/download.php
If you are on Linux, you can work on vim instead of gvim to check if you are doing the things properly.
Good luck.
What OS do you use?
i think you use win or mac. on linux you may use vim out of the box. if it's mac or win you need to install vim or gvim from vim official site.
after you need to customize you vim to work fine with ruby.
for example
good luck.
When you install gvim in Windows, you have to click a checkbox to install command-line binaries. Try reinstalling gvim and clicking that checkbox.

Resources