I'm turning kind of desperate looking for a way to enable spell checking in TeXlipse. Of the application itself I am very fond. I've tried things I found here and on other forums, and on the user manual (http://texlipse.sourceforge.net/manual/spelling.html), but I can't find clear instructions to configure spell checking, i.e. what path directory to choose, where can I find .dict files,… I mean step-by-step instructions from the beginning to the end. The User Manual entry is too vague for me.
I'm using Mac OS X 10.6.6, Eclipse 3.6.2, TeXlipse 1.4.1.
The answers are in the manual:
http://texlipse.sourceforge.net/manual/spelling.html
Get the dictionaries here: sourceforge page
Save them wherever you want. Could be /Users/your_name/documents/dictionaries, for example.
Enable 'Use built in spell checker' in the Texlipse options in eclipse.
Set both directories to whatever you used above.
Enable eclipse's own spellchecker, if it isn't already.
Restart the IDE.
I had a little trouble getting it to work nicely; I keep getting the following error message in the console. There are about 10 posts on the texlipse forum about it with no answers, so presumably it's not a big deal.
running: null
Error running spell checker
Make sure that you set the language for the project under
Properties > Latex Project Properties > Language setting to "en"
after telling it to use the built in spell checker in
Preferences > Texlipse
For me, it turned out to be related to file extensions. I pointed the texlipse spell checker to the same directory that eclipse stores its dictionaries and it didn't work. Then I made my own directory and generated my own dictionary using aspell (as mentioned in the texlipse FAQ), but this time I used a simple "dict" extension instead of the "dictionary" as in the Eclipse installation and it worked.
Related
I recently upgraded to VS Code 1.29.1 on my Ubuntu virtual machine and was very excited to try out the new List all References preview, but I can't seem to invoke it anywhere. It isn't in the context menu, and trying View: Show Reference Search through the Command Palette does nothing.
Image: No "List All References" option in the context menu when highlighting a function name.
Why does the option not appear, and is there anything I can do to enable it?
My working context:
I'm working on Ubuntu 14.01 LTS and this is for a C project; all of the files in the workspace are *.c, *.h, Makefiles, and perl scripts. I have Intellisense for C/C++ enabled with the ms-vscode.cpptools extension. The only other Marketplace extensions I have installed are color/icon theme-related. Symbol searching, go/peek to declaration/definition, quick info, error squiggles, etc. are all working properly.
Things I've tried:
verified that I'm actually using version 1.29.1 via the Help>About menu option (and confirmed multiline regex searching works)
skimmed the GitHub repo for both open and closed issues and didn't find any similar issues
searched the docs and patch notes
tried various .c and .h files within the workspace.
I'm not familiar enough with the extension and language provider architecture to know where to go from here, and I couldn't glean any caveats from the docs about the new List All References feature, so any help is appreciated.
The List All References feature is based on Find All References, which is supposed to be implemented by the language provider. In my case, the ms-vscode.cpptools language provider has not implemented Find All References, so the List All References feature is unavailable.
(I realized the one thing I hadn't checked were the issues in vscode-cpptools.)
Relevant issue: https://github.com/Microsoft/vscode-cpptools/issues/15#issuecomment-438905148
I guess as a PSA, if you're on VSC1.29.1 and don't have the List All References option, look to your language provider.
Why do I have the same suggestions while typing expression?
Example:
I had exactly the same problem. After a week or so, it get really annoying.
basically, as the comments hint to, there are probably multiple linting or intelisense tools. In my case (for python) i had the pylance extension added.
When i disabled this, the problem went away, but features were missing. So i added it back...
For some reason (i dont know why), this fixed the problem !!!
I can only hypothesise that in some way the extension was corrupted. Nevertheless, it worked.
EDIT:
I can also confirm that unchecking this setting appears to work:
Jupyter: Pylance Handles Notebooks
My current system is Windows 11, with python 3.10.
Final edit (8 Dec 2022):
This is resolved here:
Please could you install VS Code 1.74 and the latest Jupyter, PyLance and Python extension and confirm this still exists.
Visual Studio Code provides an API so third-party extensions and built-in modules can contribute suggestions for auto-completion pop-ups. The system is currently designed so suggestions are merely appended—there's no duplicate detection or removal (perhaps because extensions can also take care of sorting suggestions and such algorithm would get on the way). That means that if you have more than one extension or module for a given language you can easily get duplicate entries.
Having several extensions for PHP is not necessarily a bad idea since they can address different needs (for instance, PHP DocBlocker just creates annotations, it doesn't provide auto-completion suggestions) but you have at least two extensions (PHP Intelephense and PHP Intellisense) that do exactly the same things. That's likely to hurt performance (all your workspace files will be scanned several times) and just adds noise.
I suggest you read the extension descriptions carefully to learn what they do exactly and then figure out which ones you need. Remember that extensions can be enabled/disabled in a per-workspace basis.
The following is just my own totally subjective opinion. Among the PHP extensions that provide code intelligence only two of them seem mature enough:
PHP Intelephense
PHP Intellisense
I've tried both. PHP Intelephense works best for me than PHP Intellisense so that's the one I've kept. I've also disabled php.suggest.basic following the installation instructions because basic suggestions didn't add any value to me (they were blind string matching):
Turn off the php.suggest.basic setting for best results.
... as well as taming builtin Emmet support, which was providing really dumb suggestions:
"emmet.showExpandedAbbreviation": "inMarkupAndStylesheetFilesOnly"
YMMV.
TLDR; Installing pre-release version of Jupyter solves (v2022.11...)
Ok, so after some more extensive experimentation I think I found what's causing this in my case. After looking at the processes I noticed that there were two Pylance processes running, and consistently this would only be a problem if I was working in a session with a jupyter notebook open or one that had been opened.
saun89 17740 37.3 0.3 1008004 199492 ? Sl 20:58 0:22 /home/saun89/.vscode-server-insiders/bin/fef85ea792f6627c83024d1df726ca729d8c9cb3/node /home/saun89/.vscode-server-insiders/extensions/ms-python.vscode-pylance-2022.11.32/dist/server.bundle.js --cancellationReceive=file:9178e897a2b78b36bfd167f79b36c3bdad2931d71b --node-ipc --clientProcessId=17651
saun89 18743 257 0.7 1304584 382288 ? Sl 20:59 0:20 /home/saun89/.vscode-server-insiders/bin/fef85ea792f6627c83024d1df726ca729d8c9cb3/node /home/saun89/.vscode-server-insiders/extensions/ms-python.vscode-pylance-2022.11.32/dist/server.bundle.js --cancellationReceive=file:8744a321767eed92821fd737be4dc7dcfb728284e5 --node-ipc --clientProcessId=17651
Pylance basically spins up a service for the workspace, and then spins up a separate service for the notebook.
Output from "Python Language Server" logs:
Disabling Jupyter removes the duplication, and after installing an earlier version of the extension (v2022.4) this appears to have fully resolved the issue. I'm going to go ahead and log the extension bug once I have something reproducible.
As of 11/30/22, Jupyter Extension Pre-Release version v2022.11.1003281132 is the latest version fixes this issue. Click the gear icon next to the extension and you should see "install another version..." Then you can select version v2022.11.1003281132.
I know there are questions like this on SO, but none of the given solutions helped me.
I also tried to ask this question on netbeans forum, but they haven't responded to my questions, probably because they just don't know answers.
SO community is a "bit" bigger than the one on the netbeans forum, so I hope I'll get some clue.
I'm trying to get SASS working in Netbeans 8.0.2 (Ubuntu). I installed sass, it sits in /sur/local/bin/sass. I set up this path in NB options. I set up paths in project properties. And... nothing happens when I save a css file. Shouldn't there be at least a warning message if something's wrong?
Yes, I have "generate extra information (debug)" and "open output on error" checked. The path to the sass executable is also correct.
And yes, I also have "compile Sass files on Save" checked.
In project properties / Input and Output fields I tried relative and full urls. I also tried using ${web.root} variable.
I use Netbeans for PHP, but I don't think it matters.
None of these solutions work for me, especially that most of them is for Windows OS:
How to use SASS with Netbeans 8.0.1
Cannot get SASS to output .css file in Netbeans 8.0
Netbeans - installing SASS
Please help, I've been trying to make it working for the last 4 hours :(
Please tell me at least where can I find an error log or something.
Update:
The log says:
INFO [CPOnSaveHook]: processSavedFile called for Sass type on project
/var/www/html/analytics. INFO
[net.sickill.off.netbeans.NetbeansProject]: fileChanged: ignoring
internal file changes INFO
[org.netbeans.modules.css.prep.process.BaseProcessor]: Not compiling,
file /var/www/html/analytics/src/AppBundle/Resources/scss/admin.scss
not matched within current mappings
[Pair[/var/www/html/analytics/src/AppBundle/Resources/scss,/var/www/html/analytics/web/css]]
But as I said: In project properties / Input and Output fields I tried relative and full urls. I also tried using ${web.root} variable.
I solved my problem.
In the project properties -> css properties -> input/output fields there must not be / (a slash) at the beginning. So it should be e.g. "src/AppBundle/Resources/scss" instead of "/src/AppBundle/Resources/scss" And it should not be a full url (like /var/html/www/project...)
Also, using ${web.root} did not work.
I solved may problem. In project properties -> css prepocessor -> uncheck compile sass files on save:
So, I've been using Sublime for a while as a simple text editor, but I'm venturing into the land of plugins for work and I've run into an issue getting pylint to work. Specifically I have it installed and have the Sublime package manager working, but I'm not sure how to include paths in my sublime settings.
I haven't found very useful documentation on this point, but if you are willing to point me towards it that would be a perfectly acceptable answer. My basic issue is that currently every time I save a file, the following error message shows up:
"Please define the full path to 'lint.py' in the settings"
I understand this error message which is great, I just have no idea where the sublime settings are or what the standard format for defining a path is. Any help would be appreciated.
There are quite complete directions at the SublimeLinter GitHub page that should describe how to set everything up. Briefly, go to Preferences->Package Settings->SublimeLinter->Settings - Default to see where the different settings are defined. Then, open Preferences->Package Settings->SublimeLinter->Settings - User to change anything, as the main settings will be overwritten when the package is updated. Remember that settings files are in JSON format, so you'll need opening and closing curly brackets to enclose settings, and a comma between them:
{
"sublimelinter_delay": 30,
"sublimelinter_mark_style": "none"
}
I haven't gotten the error you have, are you sure you're using the regular SublimeLinter and not the new beta version? I just installed it fresh on my work machine (I've been using it for a while at home) and after restarting ST2 it's working like a charm with Python.
I had the same problem. I found it to be coming from the package "Pylinter". I removed Pylinter and added SublimeLinter, it covers more than python and is well used. I'm enjoying it quite a bit.
From your command line just run:
sudo easy_install pylint
sudo easy_install pep8
After that restart your sublime.
I encounter the same situation today. In my case, that is because I have not installed the 'pylint' in my system yet. It works fine after I installed the 'pylint' through pip.
Just for other people reference.
I'm having a problem with the autocomplete option in Eclipse (Helios).
I've already checked Windows->Preferences->PHP->Editor->Content Assist and everything seems to be correct there.
And when I do get completions when I write "self::" in any of my classes, but this is the only situation I get it.
For example..
"parent::"
or
"$this->"..
Don't work at all.. any ideas?
Btw, I'm working under Lunix, Ubuntu 10.10
Thanks in advance.
A few things to check:
1) .project file contains:
<nature>org.eclipse.php.core.PHPNature</nature>
2) .buildpath contains:
<buildpathentry kind="con" path="org.eclipse.php.core.LANGUAGE"/>
3) Right-click project and go to Configure -> Add PHP Support
4) Are you using a namespace in your code? If so, does completion work without a namespace i.e. in a global namespace
I can also see quite a few open issues in bugzilla related to code completion in PDT. Take a look.
Since it seems that yoy've already tried the basic solutions that are documented across the web (phpnature, add php support, buildpath, etc.) it's probably best to look at the logs and provide any error that occurs when you try to call auto-completion.
You can "tail" the log and check if anything appears when asking for an autocomplete (press Ctrl+Space after writing "$this->" inside a method of a class):
tail myWorkspace/.metadata/.log -f
The error that appears may be usefull for searching google or for including here for others to help!
Seems like updating Eclipse to Build id: 20100917-0705 solved this issue.
If you just upgrade eclipse you should rename/remove workspace/.metadata
some times there is compatibility issues...