Is there any standard path for vim plugins in vrapper. Like vim which as ~/.vim/plugin/ where custom plugins can be placed and commands can be used from VIM
The plugins that I wanted to use are cscope and doxygen
Looking at this pull request for the Sneak plugin and this request to port the Abolish plugin, Vim plugins need to be ported for Vrapper (basically rewriting the plugin functionality in Java, using Eclipse APIs or abstractions offered by Vrapper itself). I don't use Vrapper, but I'd guess that only simple remappings (via :map commands) are possible in the .vrapperrc. Anything beyond that would require a reimplementation of most of Vim's internals and the Vimscript language, and none of that is fully specified (beyond what's mentioned in Vim's :help).
Related
I'm one of the developers of QxCompiler, a node-based javascript compiler and linter for the Qooxdoo project. Like any compiler, it outputs a series of errors and warnings with line numbers but at the moment this is only output to the console. As a developer, you can Alt-Tab round to read the output but it's easy to forget to do that and it would be very useful to use Eclipse's existing code marker system to show the list of errors and highlight them in the source code.
How do I output this to Eclipse so that it will incorporate the errors and warnings into the source code?
What would be really useful is if there is some kind of IDE-neutral standard for formatting the output of the compiler so that it'll work on more than just Eclipse...
here some thoughts:
LSP
If you are interested in bringing up output into multiple IDEs in a neutral way, you should refer to https://en.wikipedia.org/wiki/Language_Server_Protocol where LSP is described. As far as I know it can be used for code completion, outline support etc. Maybe it will fit your requirements.
Eclipse Log plugin
Another option is to send the output to a log file and use plugin for log files in eclipse..
Do as done in Jenkins Editor eclipse plugin
You could also provide a REST API and maybe even a CLI tool. This is how jenkins linter works. There is a jenkins editor plugin for eclipse which does use the CLI tool (REST API) to bring up messages and errors into the eclipse editor.
See https://github.com/de-jcup/eclipse-jenkins-editor/blob/master/jenkins-editor-plugin/src/main/java-eclipse/de/jcup/jenkinseditor/handlers/CallLinterHandler.java for an entry point to look into sources and how it was done.
Some addititional explanations can be found at https://github.com/de-jcup/eclipse-jenkins-editor/wiki/Validate-by-Jenkins-Linter
I have just installed this eclipse plugin. But I found it can neither show a list of functions when typing '.', nor use templates like 'if...else...'.
Read http://www.nodeclipse.org/ carefully
Features Creating default structure for New Node
Project and New Node Source File Generating Express project
with Wizard JavaScript Syntax highlighting Bracket
matching and marking selection occurences with background color
Content Assistant within one file Go to definition with
Ctrl+click when JSDoc is
used Refactoring within one file
(Alt+Shift+R) JSON files highlight and
validation NPM support Debugging - Breakpoint,
Trace, Variables, Expressions, etc... via Eclipse debugger plugin for
V8 Setting project properties for JSHint-Eclipse
automatically; JSHint
settings template
Passing arguments to Node application and Node.js,
specifying environment variables values to use Running
CoffeeScript *.coffee files Running *.js files with
PhantomJS, MongoDB Shell or Java 8 Nashorn jjs util
Bundled together with Markdown Editor, GitHub Flavored Markdown,
StartExplorer (for system explorer and shell), RegEx, Icon Editor,
MongoDB, RestClient Tool and other plugins (20+ in total, check
update site and Nodeclispe Plugin
List) Support for Eclipse Juno, Kepler, Luna M3
As of 0.7 completion work as standard JSDT functionality, that is
for objects defined in the same class,
for objects annotated with with JSDoc
If you want more, do it yourself with help from the other people.
I suggest you that you install tern.java which uses the powerful JavaScript inference engine tern.js. You have a node.js module which provides node.js completion. As Nodeclipse editor is based on JSDT, you can use it with tern.
I want plugin for PhpStorm which can record my actions like this: opening files, changing active window with file content, finding contents etc.
Default Macro doesn't support this actions.
Or I want sources of simple macro plugin. Thanx.
Such plug-in doesn't exist. Sources for the Macro subsystem are available in the IntelliJ IDEA Community git repository.
I have just starting using the nodejs templating engine jade. Unfortunately my IDE eclipse doesn't seem to have support for this syntax and is not highlighting correctly.
Is it possible to add support for .jade files to eclipse?
As current lead of Nodeclipse effort www.nodeclipse.org I announce that Nodeclipse v0.12 has added Minimalist Jade Editor, see http://www.nodeclipse.org/history. Added just before release as I got sick of .jade to be opened outside of Eclipse.
#134 - Minimalist Jade Editor
idea is to define HTML tags and JavaScript keywords as words for highlight in Word.java
and then use it together with EditBox
Nodeclipse scope is growing, now it has Gradle for Android and JavaScript in general that I want to work on for next iteration. Also looking for developers and company willing to support the project. Raise an issue on GitHub/Nodeclipse to continue.
check if this helps
Jade-syntax-highlight
Follow the pattern used for adding HAML support to an Eclipse install, and find a lexer and colorizer for Jade.
There are several vim plugins for Aptana/Eclipse, I'm wondering whether there are any well-integrated ones that also lets you make use of a .vimrc file and a .vim user folder.
Eclimd let's you embed Vim IN Eclipse. It is your real vim loading your own .vimrc. I think the embedding works only on Linux, on other platforms it will open a new gVim instance.
Vrapper does load a .vrapperrc file but it won't support much of your lovingly customized .vimrc: for example I've ported only 16 lines of my 459 lines long .vimrc to my .vrapperrc