Hi, thank you for the plugin, it seems very cool.

I have an error when I run (coc-codeaction-line) then Add docstring for "Line or Selected" by pydocstring:

Error on request (doCodeAction): Vim(return):Error invoking 'doCodeAction' on channel 3 (coc):
TypeError: document.getText is not a function

note that CocCommand pydocstring.runFile works well.

Config: nvim : v0.8.0-dev+448-g7b2b44bce coc-pydocstring: 0.7.3 coc is up to date

doc is installed by CocCommand pydocstring.install

I run nvim in a container so would like to be able to get doq installed when building the image using a command like:

RUN nvim --headless -c ":CocCommand pydocstring.install" +qa

Is there a way to tell if nvim is running in headless mode and call doqInstall directly instead of installWrapper?

test.py

def f(x: int) -> int:
    """f.

    :param x:
    :type x: int
    :rtype: int
    """
    return x

change test.py to

def f(x: float) -> float:
    """f.

    :param x:
    :type x: int
    :rtype: int
    """
    return x

Now use codeaction pydocstring

def f(x: float) -> float:
    """f.

    :param x:
    :type x: float
    :rtype: float
    """
    """f.

    :param x:
    :type x: int
    :rtype: int
    """
    return x

Expected behaviour:

def f(x: float) -> float:
    """f.

    :param x:
    :type x: float
    :rtype: float
    """
    return x

Thanks!

The executable in windows is not ~/AppData/Local/coc/extensions/coc-pydocstring-data/doq/venv/bin/doq, it should be ~/AppData/Local/coc/extensions/coc-pydocstring-data/doq/venv/Scripts/doq.exe.

See here the code action title text says "Add docstiring..." should be "docstring"

https://github.com/yaegassy/coc-pydocstring/blob/9bb2a0a64a54351ebb15acce6ffa98fb6ef84695/src/action.ts#L83

test.py

def f(x):
    return x

after coc-pydocstring:

def f(x):
    """f.

    :param x:
    """
    return x

A blank line occurs after return x.

Can it be deleted?

Thanks!

Please add some minimal mapping and remapping and usage documentation

At the time of me writing this I have absolutely no idea whatever what the mappings are for per-line, per-selection or vim gestures to call coc-pydocstring. I've already walked through the coc-pydocstring-data which appears to contain only the virtualenv used by your plugin to wrap calls to doq. I've already walked through the node-modules/coc-pydocstring path even though I don't really know anything about coc modules and know little about the node-coc-neovim plugin stack, which makes this exploration very slow for me.

I still haven't figured out where the vimscript command mappings are, there is no vim documentation that I can find, and absolutely no hint that these commands even exist other than the brief mention in the README.md.

I love your plugin, you've done a better job than I could have done with implementation of a coc plugin, but I can't use anything except :CocCommand pydocstring-file to make it work. I don't even know what the hooks are in order to create my own mappings. Even the animated gif is missing any kind of OSD keypress magic to show the viewer what keys are being pressed by the author.

Thank you for your hard work and contribution!

Breaking change, Range discrimination in coc.nvim itself.

This change makes it difficult to determine the current line and range designation, so we will combine the "Line" and "Selected" actions into one.

Related commit:

• https://github.com/neoclide/coc.nvim/commit/cad8c6b1f0b280404ff627d08e62fcc17dabed35
• https://github.com/neoclide/coc.nvim/commit/91c1114046b199f5ae7deb4dd50dbd62fcd3240f

There is a problem that if the built-in installer is run while the project's virtual environment is activated, it will use the python commands of that project.

If the python3/python command detected is a symbolic link, resolve the link and change it to use the system global absolute path.