I installed the toggle neo vintageous plugin for sublime text and set the key to ctrl+Alt+t, to toggle neovintageous. When I toggle it on it works, but when I toggle it of I get this error message:
Error loading syntax file
"Packages/NeoVintageous/res/Command-linemode.sublime-syntax":Unable to
read Packages/NeoVintageous/res/Command-linemode.sublime-syntax
Does any one know what it means, although it still toggles off after the error message, but I don't know why it keeps popping up whenever i try to do that
Error loading syntax file "Packages/NeoVintageous/res/Command-linemode.sublime-syntax":Unable to read Packages/NeoVintageous/res/Command-linemode.sublime-syntax
Generically speaking, this error message is telling you that there is something somewhere in Sublime (an open file or other widget) that thinks that it should be using a specific syntax definition, but that syntax definition can't be found. The syntax file named is the one that's causing the error.
If we examine the filename it mentions (Packages/NeoVintageous/res/Command-linemode.sublime-syntax) we can determine that the syntax file is in the NeoVintageous package itself.
In Sublime, any package that's installed is always "turned on" and active unless it's name appears in the ignored_packages setting, which tells Sublime that even though the package exists, it should pretend that it doesn't.
It's not explicitly stated anywhere in the README for this package, but all it's doing is modifying that setting on your behalf to either add or remove the NeoVintageous plugin to the setting.
When you add a package to the list of ignored packages when it's already loaded, Sublime responds by unloading the package from memory and acting like it does not exist.
So, taken all together, the problem that you're having here is that you have NeoVintageous turned on, something in Sublime is using a syntax definition from that package, and then when you toggle the package off, the syntax definition is unloaded and Sublime complains because the syntax it wants to use is no longer available.
I don't use either of those packages personally, but based on the name of the syntax being Command-linemode.sublime-syntax my guess would be that the syntax is being used in the ex command input that you can use to give ex commands to the package (probably to allow for auto complete or something like that).
If that's the case, you can probably stop the error from being displayed by closing the command window before you toggle the state of the package. I would imagine that the error popup would go away and not recur once the command input was closed, so the error is annoying but more or less harmless.
It may be worth raising an issue with the package author to let them know what's happening, if for no other reason than they can document that this will happen or modify this package to not be able to toggle the state of the package off while the syntax is currently in use.
Related
Is there any way to have something like a status bar in Vim with CoC (or just language server in general) that tells you when current buffer is static analysis-wise invalid, eg. has compilation or linting errors?
I am using Vim w/ CoC in an Angular project, and while CoC shows me errors just fine when I have the problematic line in my current view, I don't see those outside of the current scroll position.
Compare
to
I am just one line higher on the second picture and already have no indication of errors. I can jump preemptively to next issue with coc-diagnostic or just rely on compiler output but that's clearly not ideal.
So is there perhaps plugin to be used for this (preferably one which plays nicely with CoC), or is there any better way (workflow-wise) to quickly find out that current buffer is invalid?
Turns out I was unaware of the concept of configuring statusline in vim. Searching for it yielded nice integration options between lightline (which I am using) among others and Coc https://github.com/neoclide/coc.nvim/wiki/Statusline-integration.
I am using Sublime Text-3 version 3.0 build 3143. I have connected to Salesforce using MavensMate and opened the VF Page, but dont see any color when Opened the VisualForce Page in Sublime Text. How to fixed this issue ??
VisualForce isn't something that Sublime supports out of the box, so in order to have things like syntax highlighting, you'll need to install a package that adds that support in.
The de-facto repository of third party add-on packages is Package Control, and doing a search reveals that there is a VisualForce package available.
The description for the package mentions that it provides syntax highlighting for .page files. Assuming that's the kind of file you're trying to open (I'm not familiar with VisualForce at all), this is probably what you want.
In particular, the content represented in your image appears like the following for me once this package is installed (except that I have elided what appears to be an extraneous </apex:outputText> after the email_us label):
For what it's worth, the package also includes completions to make creating such files easier.
Since you mentioned in comments that you're a little unclear on the process, here's a step by step set of instructions on how to get set up for this with Sublime Text 3143.
If you haven't already done so, you need to install Package Control. If it's not installed, the commands in the next step won't be available.
There are official installation instructions for this, but in your build of Sublime Text you can also select Tools > Install Package Control... from the menu or Install Package Control from the Command Palette in order to do the same thing.
If that menu item is not visible in your menu/command palette, then Package Control is already installed; the command is hidden if it's not needed.
Open the Command Palette with Tools > Command Palette or the appropriate key binding for your operation system (visible in that menu entry), then select the command Package Control: Install Package.
This will download the list of all packages and present them to you in a list; it may take a moment to download the whole thing. You'll see a spinner in the status line of the window to tell you the operation is in progress.
When the list of packages appears, select the VisualForce package from the list of packages; you can find it quicker by entering visual to filter the package list down.
Once this is done, the package will be installed; during the installation there will be a spinner in the status line to tell you, and the status line will briefly say that the package was installed once it's done, but it goes quick so if you blink you might miss it.
With the package now installed, you should be able to close your file and open it again to have the appropriate syntax applied to it.
You can also select Set Syntax: VisualForce from the command palette or select View > Syntax > VisualForce from the menu in order to manually set the syntax in the current file to the VisualForce syntax.
You'll need to do this for example when you create a new file since the default syntax is Plain Text and the appropriate syntax won't get set until you save the file with an appropriate extension first otherwise.
The EmacsProEssentials Sublime Text 3 package has a bug in the keybindings:
{"keys": ["ctrl+\\"], "command": "undo"}
Undo is not ctrl+\ in Emacs it is ctrl+/.
The developer is aware of the issue, but I'd like to remap the key in the meantime.
How do I remap the key in a package in Sublime Text 3?
When Sublime loads package resource files, it loads similarly named files from all packages and combines them together. This is done in a specific order, and in that order the User package is always last so that your customizations take precedence.
So the easiest thing to do would be to just use Preferences > Key Bindings (this is under Sublime Text if you're on MacOS) and put the fixed binding in your custom key bindings.
Once you do that, your version of the binding will be active (as will the old one from the package), so things will work the way that you expect.
When the upstream author updates the package you can remove your customized binding, although presumably this is not vital if you're both going to make the same change.
The more involved version of the fix involves using PackageResourceViewer to find and open the packaged version of the sublime-keymap and modify it there, thus overriding it and fixing it at the source.
However if you do that, when the author updates the file your change will still take precedence without any notification otherwise, so you'll be effectively locking yourself into your modified version, which could conceivably cause troubles down the line.
You can mitigate that by also installing OverrideAudit, which will tell you when this sort of thing is happening, but fixing it in your User package is probably the better way regardless.
I am using Sublime Text 3, and I installed the very useful angularJs package which gives great code completion for both JavaScript and HTML files, and I really don't want to disable it, but it stops the default word completion of Sublime Text.
In Preference->Package Settings->AngularJs I set the disable_default_js_completions option to false in both user and default settings, but it still messes with the word completion.
Found other people with the same issue :
https://github.com/angular-ui/AngularJS-sublime-package/issues/69
The only fix seems to be to install a TernJs package for auto-completion to replace the default functionality.
The issue is reported, and you have a temporary solution, i.e., TernJS package installation. I had to install that too in order to see buffer words and such appear in the autocomplete list, it wasn't folding them in even at the lower priority. The completions that show in Show Completions now appear after installing TernJS. I don't think there is a known hotfix, I've contributed to the report, we'll need to wait on a bug fix, or just keep using TernJS. You probably want to install Emmet and Better Completion packages if you haven't already, as well. Between those, AngularJS and TernJS packages, you're pretty covered, minus any specialities you require.
I'm trying to create a custom sublime-build file in MacOS Yosemite, that will execute ghci on console with my code preloaded. That will make my Haskell learning process faster and enjoyable. However, since I'm new to Haskell and Sublime Text, I have no idea what to write in the file.
I know that this code does the same for gnome-terminal:
{
"selector": "source.haskell",
"working_dir": "$file_path",
"cmd": ["gnome-terminal","-x","ghci", "$file"]
}
I found the code here.
check this: https://github.com/SublimeHaskell/SublimeHaskell
USAGE (From their Readme.md):
In short: Press Shift-Ctrl-P and type haskell to explore all commands.
When editing Haskell source files that are part of a Cabal project, automatic error highlighting and enhanced auto-completion are available.
Each time you save, any errors in your program will be listed at the bottom of the window and highlighted in the source code.
All source files in the project are scanned when the change. Any symbols that they export are provided in the auto-complete suggestions.
To use cabal-dev instead of cabal, set use_cabal_dev to true (or use command "Switch Cabal/Cabal-Dev") and specify cabal-dev absolute path. Completion list will be rescanned and build will use cabal-dev.
Stylish-haskell can be used to stylish file or selected text.
Use Ctrl-Shift-R to go to declaration and Ctrl-K-I to show symbol info with documentation. These command are also available through context menu with right-click.
Command 'SublimeHaskell: Browse module' is similar to ghci's browse command
To show inferred types use Show type (ctrl-k ctrl-h ctrl-t) command.
To insert inferred type use Insert type (ctrl-k ctrl-h ctrl-i).
You can jump between the errors and warnings with F4 and Shift-F4. To show hidden error output, use command Show error panel (ctrl-alt-e)