GithubHelp home page GithubHelp logo

vim-tabby's People

Contributors

github-actions[bot] avatar icycodes avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

arobase-che

vim-tabby's Issues

Load tabby on demand

How can I set it up so that the plugin is completely disabled by default and load it with some setup function (via keymap or autocommands)
And a way to disable it would be nice as well. Or a toggle

Tabby agent script not found

NVIM v0.7.2
When I run :Tabby I get error "Tabby agent script not found".
But Tabby work when I comment out "let g:tabby_node_script" in globals.vim and set absolute path to tabby-agent.js to tabby_node_script in init.vim.
It seems the problem is in the expand function.

recipe to integrate with vim-cmp ?

Anyone have a recipe to integrate with vim-cmp? Right now they both use Tab which conflicts: I see the tabby completion, but then the vim-cmp completions also show, and end up preferred for selection. vim-cmp, though, is extensible, so it should be possible to add tabby as a completion provider.

Undefined Variables

Hello,

I'm trying to test out TabbyML running in docker, but I keep getting these errors,

Error detected while processing CursorMovedI Autocommands for "*"..function tabby#OnCursorMoved[1]..<SNR>4
4_GetCompletionContext[1]..<SNR>44_GetLanguage:                                                           
line    2:                                                                                                
E121: Undefined variable: g:tabby_filetype_dict                                                           
Press ENTER or type command to continue                                                                   
Error detected while processing CursorMovedI Autocommands for "*"..function tabby#OnCursorMoved[1]..<SNR>4
4_GetCompletionContext[1]..<SNR>44_GetLanguage:                                                           
line    2:                                                                                                
E116: Invalid arguments for function has_key

My lazy plugin config:

return {
  {
    "TabbyML/vim-tabby",
    event = "BufRead",
    init = function() vim.g.tabby_keybinding_accept = "<Tab>" end,
  },
}

Let me know how I can help

Configuration options for Debounce

I was hoping this would be an option in ~/.tabby-client/agent/config.toml.

But this didn't mention anything.
So maybe it is IDE-specific.

If that's the case, please add the configuration option for the nvim plugin.

As you can tell, I'd prefer fewer auto-completion prompts when I type, and this seems like a standard enough configuration.

Tabby keeps finding old version of node

Hi there,

I was trying to get tabby running in NeoVim (v0.9.4) and I successfully installed the plugin using packer.
Now :Tabby keeps telling me that my node.js version is too old (6.6.8). The problem is I would not know where Tabby finds this node version, as the only version I have installed is v21.5.0.
I further tried pointing tabby directly to this /usr/bin/node binary with v21 using the configuration described in the README, but :Tabby keep insisting on finding only version 6.6.8. Re-installing the plugin does not change the behavior.

Any hints how to solve this or where to look for more detailed errors or logs?

Kind regards,
Dominik

Better code readability and source code.

Hi, thank you for the project.

Just a few recommendations and concerns.
the issues are:

  • tabby-agent.js is unreable.

  • wasm files do not have sorce code

Could you make the agent code readable and the wasm compiled when pulled with source code?

nvim: stuck in "initializing" status

Issue

I'm using nvim with AstroVim and Lazy.

It seems that tabby is half-loaded

in Lazy tabby is loaded:

Loaded(36)
...
    ● vim-tabby 3.67ms  Tabby

When I try to know tabby' status, I get "initializing", but it doesn't go any further.

:Tabby
Tabby is initializing.

Temporary solution

if I run :doau VimEnter
then tabby initialise. so I believe the VimEnter event is not trigger by default with nvim.

Other info

When I try other commands like version or help, I get some errors:

:Tabby version
Error detected while processing function tabby#commands#Main[8]..5:
line    1:
E121: Undefined variable: g:tabby_version
:Tabby help
Error detected while processing function tabby#commands#Main[8]..6[3]..BufLeave Autocommands for "*"..function tabby
#OnInsertLeave[1]..tabby#Dismiss[2]..tabby#virtual_text#Clear:
line   12:
E121: Undefined variable: s:nvim_namespace
E116: Invalid arguments for function nvim_buf_clear_namespace
E121: Undefined variable: s:nvim_namespace
E116: Invalid arguments for function nvim_buf_clear_namespace

is there a log somewhere to know why the plugin is stuck?

Wrong behavior when <tab> is already mapped

Add this to your vimrc:

imap <tab> <nop>

When Vim is opened, <tab> is remapped by Tabby, which takes into account the existing mapping:

:verbose imap <tab>
i  <Tab>       & tabby#Accept("\<nop>")
        Last set from ~/.vim/pack/plugins/start/tabby/autoload/tabby/keybindings.vim line 19

But pressing Tab now may result in <nop> (the five-character string) being inserted literally into the buffer.

I noticed that because Tabby conflicts with my MUcomplete plugin, which maps <tab> to an internal plug. Then, pressing Tab inserts the plug literally into the buffer. For comparison, copilot.vim does not have this issue and coexists with MUcomplete without problems.

Proxy support

I want to use the vim plugin behind a cooporate proxy but the docs say:

Please note that Tabby extensions for IDEs currently do not support proxy settings. If you need to access your Tabby server through a 
proxy, consider setting up a reverse proxy and using the reverse proxy URL as the endpoint for the Tabby IDE extension.

The logs show an fetch failed: connect ECONNREFUSED x.x.x.x:443

Please provide proper proxy support for the plugin ❤️

~/.tabby-client/config.toml not working as expected

I have been playing with Tabby from Neovim, and up until today have been specifying my endpoint url in my vim config with a line like this: vim.g.tabby_server_url = "http://0.0.0.0:8088". I see the docs now say to put this in ~/.tabby-client/agent-config.toml in a [server] key like this:

[server]
endpoint = "http://0.0.0.0:8088" 

But :Tabby status now says "cannot connect to server"

I'm not sure how to get much more feedback from tabby via logs or anything so I'll try to provide anything helpful with some instruction!

Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.