Smalltalk syntax highlighting in Sublime? - sublimetext3

I'm trying to get sublime to highlight smalltalk .st files but am running into some trouble.
A quick search found this package, but after adding the repository like it says in the README, I don't see the package that its supposed to add when doing Package Control: install package.
I also tried looking into this one but am completely lost when it says This syntax file can be converted to .tmLanguage using PackageDev 'Convert to PList'. Place the converted file in Packages/Smalltalk/Smalltalk.tmLanguage and reopen any .st file.
Can anybody help me out please? I'm running ST3 on MacOSX.

The installtion instructions using Package Control did not work for me either, but you can take the language file, Smalltalk.tmLanguage, from Smalltalk syntax for Sublime Text 3 and use the manual installation instructions you cited:
Place the file in Packages/Smalltalk/Smalltalk.tmLanguage
As you asked about macOS, on macOS this means:
/Users/<your user name>/Library/Application Support/Sublime Text 3/Packages/Smalltalk/Smalltalk.tmLanguage
The Library folder might be hidden by default. Use the Terminal or Finder's Go ▶︎ Go To Folder… to access it.

For Smalltalk/X you can download a highlighting package at - sublime highlighting for smalltalk/X called Smalltalk.sublime-package.
You can copy it to the path provided by #MartinW above.

Related

How to find where a linter is installed in order to work for SublimeLinter in Sublime 3?

So, I have installed cpplint in Sublime 3 via the Package Control, in a Windows 8.1 64bits machine.
However, it seems that cpplint cannot be found, as discussed in this troubleshooting page:
http://www.sublimelinter.com/en/latest/troubleshooting.html
More specifically, the page says that:
If the result says that the linter could not be found, that means the linter executable is in a directory which is not in your PATH, and SublimeLinter will not be able to find it. At this point you will have to find out what directory the executable was installed in from the linter’s documentation. Once you find that, you will need to augment your PATH by following the steps in Augmenting PATH below.
However, after hours trying I just can't find the"directory the executable was installed", in order to include in PATH. Yes, I found many questions about this online, but the only ones that have answers are giving solutions to Linux systems.
Any help would be very much appreciated.
In the sublime editor select Preferences -> Browse Packages
A folder will open listing the installed packages.

Emmet error PyV8 binaries (tried manual already)

I've read the docs and tried to install the binaries manually by, both in
C:\Users\Username\Sublime Text Build 3065\Data\Installed Packages\PyV8
and
C:\Users\Username\Sublime Text Build 3065\Data\Packages\PyV8
I've tried the "For Sublime Text 2 (python 2.6) version and also the "For Sublime Text 3 (Python 3.3) version. I am running python 2.7 so it should be the former, but I tried the latter just in case since it specifies 2.6 and not 2.7.
I continually get the same error despite following the instructions provided online.
Well, this is with Sublime Text 3083, latest emmet and Pyv8 binaries and Python 3.3.0 (it should work with latest Python also)
Install Python and Sublime if you haven't done that yet! ;)
Download emmet-sublime-master.zip at github. Forget Package-Control! In fact if you have emmet installed via Package Control just remove it.
Go to: c:\Users-your user-\AppData\Roaming\Sublime Text 3\Packages\
Create a 'Emmet' folder, respect the caps.
Decompress the emmet-sublime-master.zip inside the Emmet folder.
Download your pyv8 binary at github.
Create a 'PyV8' folder (outside Emmet folder, c:\Users-your user-\AppData\Roaming\Sublime Text 3\Packages).
Inside PyV8 create a folder with the exact same name of the pyv8 binary you just downloaded (example: pyv8-win64-p3)
Decompress the binary there.
Restart Sublime Text 3.
It should work!

Specifying coqtop path for CoqIDE Vim plugin on Windows 8.1

I am trying to make the CoqIDE Vim plugin work on Windows 8.1. When I source the plugin from Vim, I get this error message:
coqtop.opt: command not found.
So I looked up the plugin documentation, and found the part that seems relevent:
"coqtop" should be accessible on PATH. If "coqtop" is not in your PATH, add 'let CoqIDE_coqtop = "/path/to/coqtop"' in your "~/.vimrc".
I'm not sure what this means, but I'm guessing that there is some file or directory named coqtop that must be made visible to vim. So I opened my Coq installation directory and searched for coqtop. The search hits are:
coqtop
coqtop.cmi
coqtop.1
coqtop.byte.1
coqtop.opt.1
The obvious first candidate here is coqtop. When I click it, it opens an interactive Coq console. But when I use the let CoqIDE_coqtop command to link this file to Vim and load the plugin again, I get:
C:Program Files (x86)Coq^Hincoqtop.exe: command not found.
Another thing that looks problematic is the file type. As you can see from the error message above, the coqtop file has an .exe extension, which is specific to MS-DOS and Windows. But I don't think the plugin was written to work with .exe files...
I also tried using all the other search hits as coqtop, to no avail.
Does this mean that the plugin is useless on Windows? If someone can confirm that I'll just give up and use other IDEs. But if possible I'd really, really like to keep using Vim.

Vimball error, unrecognized character in path

I have a problem with installing SuperTab from vimball. I get an error:
E739: Cannot create directory: C:\Users\Pawe<b3>\vimfiles
I guess the problem is the directory name which is C:\Users\Paweł\vimfiles. Is there a way to solve it without changing directory name? Btw: I have set encoding=UTF-8 in my vimrc.
Edit:
The way I install it is so: download .vmb file, open it with vim (using context menu: 'edit with vim') and then I write :so %. And the error occurs.
Using :set verbose=20 I get http://pastebin.com/BLaeLzuU (those are things I found interesting).
And here's the wider story. I was trying to install plugins using vimballs, because I failed running plugins with pathogen (identical case as here: https://github.com/tpope/vim-pathogen/issues/110. In fact my output of :scritpnames is here: http://pastebin.com/YBTBvsvz). To tell you the truth I even tried to copy folder plugin form plugins git repo to my ~\vimfiles. With no success (they are not mentioned in scriptnames). And so I don't have any clue what is going on. Only that output from vimball tells me that it could be the path name. Other then that, I'm hopeless.
Btw: using Windows 8 if that's a deal breaker.
Eventually I have renamed the user name and user folder because the directory name was a problem for other aplications too. Here are the instructions: https://superuser.com/questions/495290/how-to-rename-user-folder-in-windows-8

Package Control no module named package_control.add_repository_channel_command

I've updated to the most recent version of Package Control for Sublimetext 3 via Git, but none of the commands work. The menu items are still present, strangely enough. When I open the log with Ctrl+`, I see this error:
ImportError: No module named 'Package Control.package_control.add_repository_channel_command'
How can I get it to work again?
Apparently the Package Control .sublime-package file is outdated, and in this case, referencing a python module that has been moved to a different python package (from package_control to package_control.commands).
This can be easily fixed by deleting Installed Packages/Package Control.sublime-package.
I use sublime text 3
From this site, I Follow these steps:
Go to http://wbond.net/sublime_packages/package_control/installation
& copy the long command there.
Open the Sublime Text 2 console by
pressing Ctrl+.
Paste the command you copied into the Sublime Text
console.
Press Enter.
After Package Control installs, restart
Sublime Text.
Then I got the error like that.
I have tried :
check ignored_packages on set but I found nothing.
Download package manager and copy it to Installed Packages, but not works.
Then I update my sublime to the newest version, then the error is gone.
That is my tips, you should try one of the steps, like what I have tried.

Resources