I'm new to SublimeText and Python3, so I don't really know how to turn Sublime autocomplete on. I installed Anaconda from Package Control, but I don't know how to use it. Some autocomplete shows up, but I don't think it's Anaconda's. That autocomplete keeps on poping up, then dissapearing. I can't read what it says and it hurts my eyes. How can i properly set up the autocomplete?
in case you are still looking for the answer, I had a similar problem. I had both SublimeJEDI autocompletion as well as Anaconda.
The flashing behavior is a result of you having two separate autocompletes fighting for the same space.
Turning off SublimeJEDI solved this for me - I couldn't find a way to turn off Anaconda's.
Related
I go to :
and install :
with these settings :
and have no idea why hex is not my SBT3 still not display as its color form. 😥
I've also tried : CSS
Reboot the IDE & even reboot the Mac OS X ... still not working.
Did I forgot to turn on some settings?
Can someone please help me ?
Edit
ColorHelper works on the first try, right after install. Huge thanks to : #MattDMo
... but I am still curious if someone really knows what I did wrong.
Over the past few years I began having more and more problems with the different color highlighting packages available for Sublime, including Color Highlighter, which hasn't been updated in at least 3 years, and Color Highlight at 2½ years. Someone recommended ColorHelper, and I've been happy with it ever since. Make sure you completely uninstall Color Highlighter and/or Color Highlight first, as I think I had issues with it before I did that. ColorHelper is in regular development with the release of the new v3, which apparently is a complete rewrite, and is easy to set up and use out of the box. There are a ton of customization options if you want to get into the weeds, and the author has been very responsive with some config issues I had recently. I would highly recommend it.
Recently, I installed the arch community package "mathjax" to be able to render some mathematical formulas in a jupyter notebook.
It works for the notebooks, but after the installation, other things are broken, like the rendering of
special symbols in Terminator and Sublime Text 3.
Here is the symbol in question, displayed in Sublime and in the actual prompt in Terminator:
http://imgur.com/a/lYBk1
My question is, how can I keep mathjax from changing these things.
How can this even happen? I thought the package is just relevant to
in-browser Latex rendering.
Ok, so a really bad solution to this is to move the mathjax folder in /usr/share/fonts to a new location and link to this location in the /usr/share/mathjax folder, overwriting the previous link named "fonts".
This fixes the issues with special symbols in Terminator and Sublime.
At least for Jupyter Notebooks, this does not seem to be breaking the rendering of formulas.
This is just a temporary solution, so I hope someone can find a better one.
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.
Depending on the font I use, I might see a quarter of a cursor (lower right rectangle not flashing) in the wrong place, or no cursor at all. Still, the line I'm on highlights and the column number is displayed in the lower right.
I've tried a mix of fixed-width fonts at a mix of sizes (11-14), including the default Monospace, MacVim's Menlo, the awful Courier, and another q-a site's suggested Consolas.
Any ideas how to get the cursor to show up would be great. Alternate ways to get Vi keybindings in NetBeans also acceptable, though it seems jVi is the most current / active effort.
NetBeans 7.1.2
EDIT:
Image showing no cursor with highlighting
Image showing actually two partial cursors, which I'd never seen before:
There is a problem with the Mac Retina, which is like this problem. The latest jVi release has a workaround, you need to turn on the option
Tools > Options > jViConfig > Platform > MacRetinaCursorXorBug
I had the same problem in Netbeans 8.0.2. Workaround for this is to disable following option:
Tools->Options->jVi config->platform->use modal frame
I found the solution here which solves other problems with cursor too. I hope this will help you.
Cheers
ubuntu - 14.04
java 1.7.0_121
netbeans - 8.2
jvi - 1.5.4
i had the same issue and 'use model frame' was already enabled. Enabling 'MacRetinaCursorXorBug' fixed the issue. i have set the frequency of the cursor to 500 to be on the safer side.
Enabling the option MacRetinaCursorXorBug under Tools > Options > jViConfig > Platform was the only working solution for me among a bunch of other suggested workarounds. So it's important to mention that this setting could be required even on non Mac Systems.
(Tested on environment: Netbeans IDE 8.0.2, Ubuntu 15.04 with Kernel 3.19.0-16, XFCE-Desktop 4.12, VirtualBox 4.3.28)
Setting the blink rate to 500 as suggested by develucas fixed this for me on Ubuntu and Netbeans 8.1, though it still disappears whilst moving it reappears shortly after it becomes stationary, makes jvi useable again.
I tend to maximize a terminal to one screen, and vertically split several windows in Vim. Everything works fine for the first few windows on the left, but clicking past about the 220th column in the terminal doesn't work correctly. Any mouse clicks past column 220 seem to be wrapping around to column 1. I've tested in xterm, urxvt, and Gnome terminal with and without tmux/screen; always the same behavior. If I greatly increase the size of the font in Gnome terminal, I can click on the last column (although it is no longer past column #220).
If I run a command in a terminal that prints to standard output, I can click all the way to the right of the terminal. The problem does seem to be related to Vim.
I have set mouse=a in .vimrc. I'll post the entire file on request, but it doesn't seem to have anything else related to the mouse.
It's probably irrelevant, but I'm running Xmonad+Gnome. Thanks in advance.
This has been fixed in Vim 7.3.632. See :h sgr-mouse. Or just put this in your ~/.vimrc:
set ttymouse=sgr
If you want to be compatible with versions that don't have mouse_sgr compiled in, use:
if has("mouse_sgr")
set ttymouse=sgr
else
set ttymouse=xterm2
end
To see if your version of Vim has mouse_sgr, run vim --version from the command-line, or in Vim, enter :version, and look for +mouse_sgr.
If you're using older versions of screen, or terminal emulators that don't support SGR, you may need to upgrade or switch. These settings work with all new versions of screen, tmux, gnome-terminal, PuTTY/KiTTY, iTerm2, and Terminal.app, using TERM=xterm-256color or screen-256color.
Update: If you're using neovim, SGR support is enabled by default.
Edit:
I deleted the bug report, as that tracker was for the website, not the text editor.
In looking in the correct place for an existing bug report, I found this:
http://groups.google.com/group/vim_dev/browse_thread/thread/4c137e64d2032441/b3993eaa89589619?lnk=gst&q=mouse#b3993eaa89589619
To summarize, it was an xterm limitation that has been lifted. However, Vim does not yet support columns longer than 223.
Original:
This seems to be a bug, as supported by comments made by redstreet. I filed a bug report:
https://sourceforge.net/tracker/?func=detail&aid=3389331&group_id=27891&atid=391887
A few years later, the bug still seems to be present.
The solution I found is neovim: a modern refactor of vim. Among other features, this bug has been resolved.
I simply copied my .vimrc into .nvimrc, and my plugins just worked with nvim. Maybe I'll just keep using that.