The handle is invalid - sublimetext2

I am using Sublime Text 2. Whenever I start Sublime Text from the command line, and run the code I am working, I always get:
[Error 6] The handle is invalid
But when I start Sublime from "windows + r", everything goes as it should. Why?
I am using portable version of Sublime and my working dir is D (for I do not own the computer I am using).

I start mine with from git bash with the alias
alias subl="start sublime_text.exe"
with double-quotes and it works perfectly.
If I do it any other way it doesn't work quite right and I get the same error as above in the console of Sublime Text 2.

Related

Why is Sublime HTML Prettify not working

I've installed Sublime-HTMLPrettify as shown here https://github.com/victorporof/Sublime-HTMLPrettify
but when I try and use the command (e.g. by right clicking on a selected section of HTML) it doesn't do anything.
Is there something I'm missing?
==== PLATFORMS
SublimeText 2
OS X 10.11.3 (15D21)
Node.js is at /usr/local/bin/node and I can access it from the CLI using node.
Which version of Sublime Text you are using? and in which OS you have installed it?
For your tag I supposed Sublime Text 2.
Ensure you have node.js on System Paths and take a note from the commands and configurations that the description file of sublime-htmlprettify are only for Sublime Text 3
Hope this help you.

Sublime Text 2/3 - tag multiplier not working on tab

I have just found something on my new Ubuntu installation that has not happened before. I will explain
Normally if i do this code:
div*3 and press tab
I get:
<div></div><div></div><div></div>
But now when I do the same thing, I get nothing. It just "tabs" over the line. This never happened before so if someone knows the answer I would be very thankful.
All this is happening with Emmet already installed
Sublime Text 3: 3059
Ubuntu 12.04 64 Bits
Same is also happening on Sublime Text2.
Sublime Text does not come with the Emmet package by default. You will need to install Package Control first - remember that there are different versions for ST2 and ST3. After it has been installed and you've restarted Sublime Text, open the Command Palette with CtrlShiftP, search for Package Control: Install Package, type in emmet, hit Enter, and it will be installed for you.

Hart'ls Ruby Tutorial - Subl Gemfile not recognized

I'm brand new to Ruby and Rails, so sorry if this is a totally ridiculous question. The tutorial book that I'm reading says that I should be able to launch a Gemfile in Sublime Text directly from the command prompt using the subl Gemfile command. When I try this, I get an error that says "subl is not recognized as an internal or external command, operable program, or batch file".
I am in the right directory where the Gemfile is located.
Ruby is definitely installed and I am using the command prompt with Ruby and Rails.
i have the sublime text 2 and i added the path as i found,but no solution.i even tried :sublime_text Gemfile
i have tried so many different solutions but no result.
i'm using windows
Thank you in advance
the reason it isn't working isn't a rails question, it is because you haven't set up sublime to work using the command "subl" in your terminal. Try these commands. If you wish to understand the error better, just type in any gibberish into the terminal. It will tell you a similar thing.
sudomkdir /usr/local
sudomkdir /usr/local/bin
sudo ln-s/Applications/Sublime\Text\2.app/Contents/SharedSupport/bin/subl /usr/local/bin/subl
EDIT
Sublime Text from Command Line (Win7)
https://teamtreehouse.com/forum/sublime-text-command-line-shortcut-windows
https://teamtreehouse.com/forum/ruby-on-rails-subl-command-not-found
Otherwise, you can refer to this
subl is Mac only.
For Windows, you need to add C:\Program Files (x86)\Sublime Text 2 to your Environment path,
This will work on Windows 7:
Right click My Computer, Properties, then Advanced System Settings, then Environment Variables.. Go down to System Variables, and edit PATH, you'll need to add the Path to Sublime.
Then you should be able to run sublime_text my-file from the command line. (Since the .exe is called sublime_text.exe

Run a sublime plugin from the command line?

how can I run a sublime plugin from the command line?
I have read of a subl --command but it seems to be for osx and i'm on windows. http://www.sublimetext.com/docs/2/osx_command_line.html I see nothing there to call a plugin, and the commands don't seem to work for sublime_text.exe
i'm on Windows, with sublime_text.exe
Sublime Text plugins do not offer command line interfaces.
Many times Sublime Text plugins wrap an external command (csslint, jshint, etc.) which is run as a subprocess by the plugin. Because your question does not specify which plugin you want to run it is impossible to tell whether or not this plugin is based on an external program.
I'd rather suggest you to ask your question in more sense "How do I solve problem X from the command line" as it sounds you are approaching the problem from the wrong angle.

Sublime Text 2 build command ignores the shebang

The Sublime text 2.0.1 (Mac OSX) build command ignores the shebang line a the top of my python file.
The shebang line has the full path to my python 3.2 installation :
#!/usr/local/bin/python3
However the python version being used is always 2.7.2. I'm maintaining code for both 2.7 and 3.2 and so must rely on the shebang line to be used.
Is there a way to configure the Sublime text 2 build system to look at the shebang?
Sublime does not use the shebang to determine the execution, it uses your build rule. You could customize the Python build rule to add variants for python2 and python3.
Official instructions for adding build variants.
Simplified example of build variants from another SO question.
Note that with build variants, the default is run by Command+B (Mac) or Control+B (Windows and Linux). The second variant can be run Command+Shift+B (Mac) or Control+Shift+B (Windows and Linux).
Have a look at Sublime Text Shebang plugin.
It adds a few commands that allow to run scripts, based on the shebang line, but the output will be placed on a new buffer, not in the console.