Skip to content

Open to changing Clojure keyword_patterns? #1015

@Olical

Description

@Olical

Hi there! One of the main Clojure + Vim completion tools, async-clj-omni, has been recommending the following configuration to improve Deoplete + Vim + Clojure for some years now.

let g:deoplete#keyword_patterns = {}
let g:deoplete#keyword_patterns.clojure = '[\w!$%&*+/:<=>?@\^_~\-\.#]*'

I've been using the following in my dotfiles for years using the new config framework functions.

call deoplete#custom#option('keyword_patterns', {'clojure': '[\w!$%&*+/:<=>?@\^_~\-\.#]*'}) 

I was just wondering if you'd be open to changing the Clojure defaults to these values? That's if there are any language defaults for Deoplete... I couldn't actually find them.

I only bring this up because, as a Clojure tool author (Conjure) I have built in integration with Deoplete. Essentially every Clojure autocomplete in Vim developer tries to get their users to set this configuration, it makes Deoplete + Clojure work so much better.

If you have no framework for this kind of default or you're not happy with the change I totally understand. I'm happy to make the change, I just wanted to ask you about this before doing anything 🙂

I hope you're having a great weekend so far!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy