BranchesTags

Repository files navigation

Vimpire – a Clojure environment for Vim

Vimpire is the undead body of VimClojure which returned into the Clojuresphere.

 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin to make life easier for people already familiar with Vim. So you should be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way to set up a correct classpath! This is the responsibility of the build system of the given project. So before using the dynamic server make yourself comfortable with Clojure, the JVM and Vim.

Requirements

The plugin is ready to be used as a package. Regarding package managers you'll have to figure things out yourself.

It uses channels, so you'll need a Vim 8 or later.

On the Clojure side, you have to provide a socket repl. That means either Clojure 1.8 or you'll have to backport the functionality yourself.

Here be Dragons

After starting Vim and ideally before editing Clojure code you have to start the backend server connection.

 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely zero config and self contained. Also, there is no conflict of several Vimpire instances connecting to the same backend server. They share code in case of being of the same version. Otherwise they are completely separated.

When you got fangs, the connection is ready. Be aware that the first connect is slow, because things have to be prepared like starting the side-loader and injecting the venom. Don't bother me with trivial nonsense like “start-up time.”

Demos

I created a small set of short demos:

FAQs

  • Hey, I'd like nifty feature X to be supported!
    Have fun implementing it. I'll support in providing extension points to reuse Vimpire's infrastructure, but I don't care about including it in Vimpire itself.

  • Hey, why are there no default bindings set up?
    Obviously the opinions are too different on this one. So pick your own style.

  • Hey, why is my repl messed up when I delete the prompt?
    Because it's a buffer and not a terminal.

  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    Don't have toplevel commands. Put them in a (defn main …) and use clj -m to run the script. Starting the rockets on the toplevel is bad style. There are exceptions. I don't optimise for exceptions.

  • Hey, your plugin sucks because X!
    Then don't use it.

Sources

The ASCII art was taken from here. Take care. It tries to play a midi.

-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About

A Clojure IDE for Vim

Resources

Readme
License
Activity

Stars

24 stars

Watchers

3 watching

Forks

1 fork
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
BranchesTags
Repository files navigation
Vimpire – a Clojure environment for Vim
Vimpire is the undead body of VimClojure which returned into the
Clojuresphere.
 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin
to make life easier for people already familiar with Vim. So you should
be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way
to set up a correct classpath! This is the responsibility of the build
system of the given project. So before using the dynamic server make
yourself comfortable with Clojure, the JVM and Vim.
Requirements
The plugin is ready to be used as a package. Regarding package managers
you'll have to figure things out yourself.
It uses channels, so you'll need a Vim 8 or later.
On the Clojure side, you have to provide a socket repl. That means
either Clojure 1.8 or you'll have to backport the functionality yourself.
Here be Dragons
After starting Vim and ideally before editing Clojure code you have to
start the backend server connection.
 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely
zero config and self contained. Also, there is no conflict of several
Vimpire instances connecting to the same backend server. They share code
in case of being of the same version. Otherwise they are completely
separated.
When you got fangs, the connection is ready. Be aware that the first
connect is slow, because things have to be prepared like starting the
side-loader and injecting the venom. Don't bother me with trivial
nonsense like “start-up time.”
Demos
I created a small set of short demos:
FAQs
  • Hey, I'd like nifty feature X to be supported!
    
Have fun implementing it. I'll support in providing extension points to
reuse Vimpire's infrastructure, but I don't care about including it in
Vimpire itself.
  • Hey, why are there no default bindings set up?
    
Obviously the opinions are too different on this one. So pick your own
style.
  • Hey, why is my repl messed up when I delete the prompt?
    
Because it's a buffer and not a terminal.
  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    
Don't have toplevel commands. Put them in a (defn main …) and use
clj -m to run the script. Starting the rockets on the toplevel is bad
style. There are exceptions. I don't optimise for exceptions.
  • Hey, your plugin sucks because X!
    
Then don't use it.
Sources
The ASCII art was taken from here.
Take care. It tries to play a midi.
-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About
A Clojure IDE for Vim
Resources
Readme
License
Activity
Stars
24 stars
Watchers
3 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Vimpire – a Clojure environment for Vim
Vimpire is the undead body of VimClojure which returned into the
Clojuresphere.
 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin
to make life easier for people already familiar with Vim. So you should
be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way
to set up a correct classpath! This is the responsibility of the build
system of the given project. So before using the dynamic server make
yourself comfortable with Clojure, the JVM and Vim.
Requirements
The plugin is ready to be used as a package. Regarding package managers
you'll have to figure things out yourself.
It uses channels, so you'll need a Vim 8 or later.
On the Clojure side, you have to provide a socket repl. That means
either Clojure 1.8 or you'll have to backport the functionality yourself.
Here be Dragons
After starting Vim and ideally before editing Clojure code you have to
start the backend server connection.
 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely
zero config and self contained. Also, there is no conflict of several
Vimpire instances connecting to the same backend server. They share code
in case of being of the same version. Otherwise they are completely
separated.
When you got fangs, the connection is ready. Be aware that the first
connect is slow, because things have to be prepared like starting the
side-loader and injecting the venom. Don't bother me with trivial
nonsense like “start-up time.”
Demos
I created a small set of short demos:
FAQs
  • Hey, I'd like nifty feature X to be supported!
    
Have fun implementing it. I'll support in providing extension points to
reuse Vimpire's infrastructure, but I don't care about including it in
Vimpire itself.
  • Hey, why are there no default bindings set up?
    
Obviously the opinions are too different on this one. So pick your own
style.
  • Hey, why is my repl messed up when I delete the prompt?
    
Because it's a buffer and not a terminal.
  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    
Don't have toplevel commands. Put them in a (defn main …) and use
clj -m to run the script. Starting the rockets on the toplevel is bad
style. There are exceptions. I don't optimise for exceptions.
  • Hey, your plugin sucks because X!
    
Then don't use it.
Sources
The ASCII art was taken from here.
Take care. It tries to play a midi.
-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About
A Clojure IDE for Vim
Resources
Readme
License
Activity
Stars
24 stars
Watchers
3 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Vimpire – a Clojure environment for Vim
Vimpire is the undead body of VimClojure which returned into the
Clojuresphere.
 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin
to make life easier for people already familiar with Vim. So you should
be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way
to set up a correct classpath! This is the responsibility of the build
system of the given project. So before using the dynamic server make
yourself comfortable with Clojure, the JVM and Vim.
Requirements
The plugin is ready to be used as a package. Regarding package managers
you'll have to figure things out yourself.
It uses channels, so you'll need a Vim 8 or later.
On the Clojure side, you have to provide a socket repl. That means
either Clojure 1.8 or you'll have to backport the functionality yourself.
Here be Dragons
After starting Vim and ideally before editing Clojure code you have to
start the backend server connection.
 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely
zero config and self contained. Also, there is no conflict of several
Vimpire instances connecting to the same backend server. They share code
in case of being of the same version. Otherwise they are completely
separated.
When you got fangs, the connection is ready. Be aware that the first
connect is slow, because things have to be prepared like starting the
side-loader and injecting the venom. Don't bother me with trivial
nonsense like “start-up time.”
Demos
I created a small set of short demos:
FAQs
  • Hey, I'd like nifty feature X to be supported!
    
Have fun implementing it. I'll support in providing extension points to
reuse Vimpire's infrastructure, but I don't care about including it in
Vimpire itself.
  • Hey, why are there no default bindings set up?
    
Obviously the opinions are too different on this one. So pick your own
style.
  • Hey, why is my repl messed up when I delete the prompt?
    
Because it's a buffer and not a terminal.
  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    
Don't have toplevel commands. Put them in a (defn main …) and use
clj -m to run the script. Starting the rockets on the toplevel is bad
style. There are exceptions. I don't optimise for exceptions.
  • Hey, your plugin sucks because X!
    
Then don't use it.
Sources
The ASCII art was taken from here.
Take care. It tries to play a midi.
-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About
A Clojure IDE for Vim
Resources
Readme
License
Activity
Stars
24 stars
Watchers
3 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
BranchesTags
Repository files navigation
Vimpire – a Clojure environment for Vim
Vimpire is the undead body of VimClojure which returned into the
Clojuresphere.
 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin
to make life easier for people already familiar with Vim. So you should
be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way
to set up a correct classpath! This is the responsibility of the build
system of the given project. So before using the dynamic server make
yourself comfortable with Clojure, the JVM and Vim.
Requirements
The plugin is ready to be used as a package. Regarding package managers
you'll have to figure things out yourself.
It uses channels, so you'll need a Vim 8 or later.
On the Clojure side, you have to provide a socket repl. That means
either Clojure 1.8 or you'll have to backport the functionality yourself.
Here be Dragons
After starting Vim and ideally before editing Clojure code you have to
start the backend server connection.
 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely
zero config and self contained. Also, there is no conflict of several
Vimpire instances connecting to the same backend server. They share code
in case of being of the same version. Otherwise they are completely
separated.
When you got fangs, the connection is ready. Be aware that the first
connect is slow, because things have to be prepared like starting the
side-loader and injecting the venom. Don't bother me with trivial
nonsense like “start-up time.”
Demos
I created a small set of short demos:
FAQs
  • Hey, I'd like nifty feature X to be supported!
    
Have fun implementing it. I'll support in providing extension points to
reuse Vimpire's infrastructure, but I don't care about including it in
Vimpire itself.
  • Hey, why are there no default bindings set up?
    
Obviously the opinions are too different on this one. So pick your own
style.
  • Hey, why is my repl messed up when I delete the prompt?
    
Because it's a buffer and not a terminal.
  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    
Don't have toplevel commands. Put them in a (defn main …) and use
clj -m to run the script. Starting the rockets on the toplevel is bad
style. There are exceptions. I don't optimise for exceptions.
  • Hey, your plugin sucks because X!
    
Then don't use it.
Sources
The ASCII art was taken from here.
Take care. It tries to play a midi.
-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About
A Clojure IDE for Vim
Resources
Readme
License
Activity
Stars
24 stars
Watchers
3 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Vimpire – a Clojure environment for Vim
Vimpire is the undead body of VimClojure which returned into the
Clojuresphere.
 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin
to make life easier for people already familiar with Vim. So you should
be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way
to set up a correct classpath! This is the responsibility of the build
system of the given project. So before using the dynamic server make
yourself comfortable with Clojure, the JVM and Vim.
Requirements
The plugin is ready to be used as a package. Regarding package managers
you'll have to figure things out yourself.
It uses channels, so you'll need a Vim 8 or later.
On the Clojure side, you have to provide a socket repl. That means
either Clojure 1.8 or you'll have to backport the functionality yourself.
Here be Dragons
After starting Vim and ideally before editing Clojure code you have to
start the backend server connection.
 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely
zero config and self contained. Also, there is no conflict of several
Vimpire instances connecting to the same backend server. They share code
in case of being of the same version. Otherwise they are completely
separated.
When you got fangs, the connection is ready. Be aware that the first
connect is slow, because things have to be prepared like starting the
side-loader and injecting the venom. Don't bother me with trivial
nonsense like “start-up time.”
Demos
I created a small set of short demos:
FAQs
  • Hey, I'd like nifty feature X to be supported!
    
Have fun implementing it. I'll support in providing extension points to
reuse Vimpire's infrastructure, but I don't care about including it in
Vimpire itself.
  • Hey, why are there no default bindings set up?
    
Obviously the opinions are too different on this one. So pick your own
style.
  • Hey, why is my repl messed up when I delete the prompt?
    
Because it's a buffer and not a terminal.
  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    
Don't have toplevel commands. Put them in a (defn main …) and use
clj -m to run the script. Starting the rockets on the toplevel is bad
style. There are exceptions. I don't optimise for exceptions.
  • Hey, your plugin sucks because X!
    
Then don't use it.
Sources
The ASCII art was taken from here.
Take care. It tries to play a midi.
-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About
A Clojure IDE for Vim
Resources
Readme
License
Activity
Stars
24 stars
Watchers
3 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Vimpire – a Clojure environment for Vim
Vimpire is the undead body of VimClojure which returned into the
Clojuresphere.
 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin
to make life easier for people already familiar with Vim. So you should
be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way
to set up a correct classpath! This is the responsibility of the build
system of the given project. So before using the dynamic server make
yourself comfortable with Clojure, the JVM and Vim.
Requirements
The plugin is ready to be used as a package. Regarding package managers
you'll have to figure things out yourself.
It uses channels, so you'll need a Vim 8 or later.
On the Clojure side, you have to provide a socket repl. That means
either Clojure 1.8 or you'll have to backport the functionality yourself.
Here be Dragons
After starting Vim and ideally before editing Clojure code you have to
start the backend server connection.
 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely
zero config and self contained. Also, there is no conflict of several
Vimpire instances connecting to the same backend server. They share code
in case of being of the same version. Otherwise they are completely
separated.
When you got fangs, the connection is ready. Be aware that the first
connect is slow, because things have to be prepared like starting the
side-loader and injecting the venom. Don't bother me with trivial
nonsense like “start-up time.”
Demos
I created a small set of short demos:
FAQs
  • Hey, I'd like nifty feature X to be supported!
    
Have fun implementing it. I'll support in providing extension points to
reuse Vimpire's infrastructure, but I don't care about including it in
Vimpire itself.
  • Hey, why are there no default bindings set up?
    
Obviously the opinions are too different on this one. So pick your own
style.
  • Hey, why is my repl messed up when I delete the prompt?
    
Because it's a buffer and not a terminal.
  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    
Don't have toplevel commands. Put them in a (defn main …) and use
clj -m to run the script. Starting the rockets on the toplevel is bad
style. There are exceptions. I don't optimise for exceptions.
  • Hey, your plugin sucks because X!
    
Then don't use it.
Sources
The ASCII art was taken from here.
Take care. It tries to play a midi.
-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About
A Clojure IDE for Vim
Resources
Readme
License
Activity
Stars
24 stars
Watchers
3 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
BranchesTags
Repository files navigation
Vimpire – a Clojure environment for Vim
Vimpire is the undead body of VimClojure which returned into the
Clojuresphere.
 _..._
.' '.
; __ __ ;
|/ \ / \|
|\| -- ' -- |/|
|(| \o| |o/ |)|
_\| > |/_
.-' | ,.___., | '-.
\ ; V'-'V ; /
`\ \ / /`
`\ '-...-' /`
`\ / \ /`
jgs `\\_//`

Vimpire is not intended to be an easy to use Clojure IDE, but a plugin
to make life easier for people already familiar with Vim. So you should
be familiar with Vim and/or Java. Eg. Vimpire won't help you in any way
to set up a correct classpath! This is the responsibility of the build
system of the given project. So before using the dynamic server make
yourself comfortable with Clojure, the JVM and Vim.
Requirements
The plugin is ready to be used as a package. Regarding package managers
you'll have to figure things out yourself.
It uses channels, so you'll need a Vim 8 or later.
On the Clojure side, you have to provide a socket repl. That means
either Clojure 1.8 or you'll have to backport the functionality yourself.
Here be Dragons
After starting Vim and ideally before editing Clojure code you have to
start the backend server connection.
 :VimpireBite <host>:<port>

No further setup is required. The backend part of Vimpire is completely
zero config and self contained. Also, there is no conflict of several
Vimpire instances connecting to the same backend server. They share code
in case of being of the same version. Otherwise they are completely
separated.
When you got fangs, the connection is ready. Be aware that the first
connect is slow, because things have to be prepared like starting the
side-loader and injecting the venom. Don't bother me with trivial
nonsense like “start-up time.”
Demos
I created a small set of short demos:
FAQs
  • Hey, I'd like nifty feature X to be supported!
    
Have fun implementing it. I'll support in providing extension points to
reuse Vimpire's infrastructure, but I don't care about including it in
Vimpire itself.
  • Hey, why are there no default bindings set up?
    
Obviously the opinions are too different on this one. So pick your own
style.
  • Hey, why is my repl messed up when I delete the prompt?
    
Because it's a buffer and not a terminal.
  • Hey, why is the namespace loaded when I open a file? I got toplevel commands!
    
Don't have toplevel commands. Put them in a (defn main …) and use
clj -m to run the script. Starting the rockets on the toplevel is bad
style. There are exceptions. I don't optimise for exceptions.
  • Hey, your plugin sucks because X!
    
Then don't use it.
Sources
The ASCII art was taken from here.
Take care. It tries to play a midi.
-- Meikel Branmdeyer <mb@kotka.de>
Erlensee, 2018

About
A Clojure IDE for Vim
Resources
Readme
License
Activity
Stars
24 stars
Watchers
3 watching
Forks
1 fork
Report repository
Releases
Packages
Contributors
Languages