{"id":28146834,"url":"https://github.com/susam/vimer","last_synced_at":"2025-10-29T10:09:04.289Z","repository":{"id":46011659,"uuid":"49067096","full_name":"susam/vimer","owner":"susam","description":"Declutter your desktop by opening files in existing instance of GVim/MacVim","archived":false,"fork":false,"pushed_at":"2024-05-09T08:37:39.000Z","size":45,"stargazers_count":70,"open_issues_count":0,"forks_count":6,"subscribers_count":3,"default_branch":"main","last_synced_at":"2024-05-09T23:42:35.530Z","etag":null,"topics":["batch-script","gvim","linux","macos","macvim","posix","shell-script","vim","windows"],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/susam.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGES.md","contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2016-01-05T13:20:32.000Z","updated_at":"2024-05-09T08:37:42.000Z","dependencies_parsed_at":"2022-09-24T12:20:22.485Z","dependency_job_id":null,"html_url":"https://github.com/susam/vimer","commit_stats":null,"previous_names":[],"tags_count":2,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/susam%2Fvimer","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/susam%2Fvimer/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/susam%2Fvimer/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/susam%2Fvimer/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/susam","download_url":"https://codeload.github.com/susam/vimer/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254243314,"owners_count":22038048,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["batch-script","gvim","linux","macos","macvim","posix","shell-script","vim","windows"],"created_at":"2025-05-14T23:14:39.651Z","updated_at":"2025-10-29T10:08:59.237Z","avatar_url":"https://github.com/susam.png","language":"Shell","readme":"Vimer\r\n=====\r\n\r\nVimer is a convenience wrapper script to open files in an existing\r\ninstance of GVim or MacVim.\r\n\r\n[![Download][SHIELD_WIN]][DOWNLOAD_WIN]\r\n[![Download][SHIELD_LIN]][DOWNLOAD_LIN]\r\n[![Build Status][BUILD_IMG]][BUILD_URL]\r\n[![Coverage Status][COVERAGE_IMG]][COVERAGE_URL]\r\n\r\nThe Windows script has been tested on Windows 7 only.  However, it\r\nshould work fine on other recent versions of Windows too.\r\n\r\nThe Linux/Mac script has been tested with [bash][], [ksh][] and\r\n[zsh][] on Debian and Mac as well as with [dash][], [posh][] and\r\n[yash][yash] on Debian.  It should work fine on any POSIX compliant\r\nsystem with a POSIX compliant shell.\r\n\r\n[SHIELD_WIN]: https://img.shields.io/badge/download-vimer%2ecmd%20for%20Windows-brightgreen.svg\r\n[SHIELD_LIN]: https://img.shields.io/badge/download-vimer%20for%20Linux%2fMac-brightgreen.svg\r\n[DOWNLOAD_WIN]: https://github.com/susam/vimer/releases/download/0.2.0/vimer.cmd\r\n[DOWNLOAD_LIN]: https://github.com/susam/vimer/releases/download/0.2.0/vimer\r\n\r\n[BUILD_IMG]: https://travis-ci.org/susam/vimer.svg?branch=master\r\n[BUILD_URL]: https://travis-ci.org/susam/vimer\r\n[COVERAGE_IMG]: https://coveralls.io/repos/github/susam/vimer/badge.svg?branch=master\r\n[COVERAGE_URL]: https://coveralls.io/github/susam/vimer?branch=master\r\n\r\n[bash]: https://packages.debian.org/stable/bash\r\n[ksh]: https://packages.debian.org/stable/ksh\r\n[zsh]: https://packages.debian.org/stable/zsh\r\n[dash]: https://packages.debian.org/stable/dash\r\n[posh]: https://packages.debian.org/stable/posh\r\n[yash]: https://packages.debian.org/stable/yash\r\n\r\n\r\nContents\r\n--------\r\n\r\n* [Necessity](#necessity)\r\n* [Current Development Status](#current-development-status)\r\n* [Getting Started](#getting-started)\r\n* [Troubleshooting](#troubleshooting)\r\n* [Context Menu](#context-menu)\r\n  * [Windows](#windows)\r\n  * [Xfce on Linux](#xfce-on-linux)\r\n  * [GNOME on Linux](#gnome-on-linux)\r\n  * [Mac](#mac)\r\n* [License](#license)\r\n* [Support](#support)\r\n\r\n\r\nNecessity\r\n---------\r\n\r\nThis project was written to address the following needs.\r\n\r\n 1. Running `gvim foo.txt` on Windows or Linux, or `mvim foo.txt` on\r\n    Mac, opens the file in a new GVim or MacVim window.  Launching\r\n    GVim or MacVim from the shell in this manner again and again can\r\n    easily clutter the desktop with too many windows.  Moreover, if\r\n    the file being opened is already open in another instance of GVim\r\n    or MacVim, the editor warns about an existing swap file and\r\n    requires the user to take action for it.  This can be distracting\r\n    sometimes.\r\n\r\n    Of course, one can open and edit all files from within a single\r\n    GVim or MacVim instance with the editor commands such as `:e` or\r\n    `:tabe` to avoid these problems, but it is still useful to be able\r\n    to edit files from the shell, especially while navigating\r\n    directories in the shell.\r\n\r\n    Vimer offers a way to edit files from the shell such that every\r\n    file being edited opens in a new buffer in the same instance of\r\n    GVim or MacVim.  If a file being opened is already open in GVim or\r\n    MacVim, no warning occurs; instead the editor silently displays\r\n    the specified file.\r\n\r\n 2. The problems discussed in the previous point can also be solved\r\n    using a simple wrapper script on Windows, say, myvim.cmd.\r\n\r\n    ```bat\r\n    @echo off\r\n    gvim --remote-silent %*\r\n    ```\r\n\r\n    Or using alias on Linux.\r\n\r\n    ```sh\r\n    alias myvim=\"gvim --remote-silent\"\r\n    ```\r\n\r\n    Here is a similar alias for Mac.\r\n\r\n    ```sh\r\n    alias myvim=\"mvim --remote-silent\"\r\n    ```\r\n\r\n    But this solution is not without flaws.  Of course, it takes care\r\n    that a command like `myvim foo.txt bar.txt` opens both files in\r\n    two buffers in the same instance of GVim or MacVim.  However the\r\n    following annoying behaviour occurs.\r\n\r\n      - Running `myvim` without arguments leads to an error: `Argument\r\n        missing after: \"--remote-silent\"`.\r\n\r\n      - Trying to pipe standard output of one command into the\r\n        standard input of GVim or MacVim with a command like `ls |\r\n        myvim -` results in an empty buffer for a file named `-`.  The\r\n        reason for this is documented in the editor's documentation.\r\n        Enter `:help remote` in the editor to read it.\r\n\r\n    Vimer offers a litle more elaborate wrapper script that handles\r\n    these special cases better.\r\n\r\n      - `vimer foo.txt bar.txt` opens both files in the same instance\r\n         of GVim or MacVim.\r\n\r\n      - `vimer` launches a new instance of GVim or MacVim.\r\n\r\n      - `ls | vimer -` shows the output of `ls` in an existing\r\n        instance of GVim or MacVim if it exists.\r\n\r\n 3. Vim provides a context menu option called *Edit with Vim* that\r\n    opens a file in a new buffer in an *existing* tab page in an\r\n    existing instance of GVim.  However, it doesn't provide a context\r\n    menu option that opens a file in a *new* tab page in an existing\r\n    instance of GVim.  Vimer fills this gap by creating a context menu\r\n    option for files called *Edit with GVim tab* that opens a file in\r\n    a new tab page in an existing instance of GVim.  This feature is\r\n    available only for Windows.\r\n\r\n\r\nCurrent Development Status\r\n--------------------------\r\n\r\nYou might notice that this project has not received a new release for\r\nmany years now.  This is due to the following three reasons:\r\n\r\n  - This project worked well for me as long as I used Vim actively.\r\n\r\n  - I use Emacs as my primary computing environment these days.  As a\r\n    result I use this project only occassionally these days.  When I\r\n    do use Vim, this project works well for me.\r\n\r\n  - In the initial few releases of this, I took great care to run the\r\n    test suite in the [test/](test/) directory with various shells.  I\r\n    do not have the time and resources to perform such testing\r\n    anymore.  As a result, I am reluctant to make any changes to this\r\n    project anymore.\r\n\r\nDue to the points mentioned above, I do not accept pull requests to\r\nthis project.  If this project works for you, that's great!  However,\r\nif it does not, I hope you will be able to dive into the Vimer script\r\nthat you use and update the script to suit your needs.\r\n\r\nAlternatively, you could also use Konfekt's fork of Vimer available at\r\n[github.com/konfekt/vimer](https://github.com/konfekt/vimer) which\r\nprovides certain enhancements pertaining to locating the Vim\r\nexecutable more flexibly.\r\n\r\n\r\nGetting Started\r\n---------------\r\n\r\nVimer is a single-file executable script.\r\n\r\nDownload [`vimer.cmd`][DOWNLOAD_WIN] for Windows, or\r\n[`vimer`][DOWNLOAD_LIN] for Linux or Mac.\r\n\r\nCopy it to a directory specified in the PATH environment variable.  On\r\nLinux or Mac, make the script executable: `chmod u+x vimer`.\r\n\r\nThe following list describes some of the ways Vimer may be used.\r\n\r\n 1. Launch a new instance of GVim or MacVim.\r\n\r\n    ```sh\r\n    vimer\r\n    ```\r\n\r\n 2. Edit files.\r\n\r\n    ```sh\r\n    vimer foo.txt bar.txt baz.txt\r\n    ```\r\n\r\n    If an instance of GVim or MacVim is already running, this command\r\n    opens the files in separate buffers in the same instance of the\r\n    editor.  Otherwise, they are opened in separate buffers in a new\r\n    instance of the editor.\r\n\r\n 3. If the `-t` option is specified, then files are opened in separate\r\n    tab pages in an existing instance of GVim or MacVim if it exists.\r\n    If no instance of GVim or MacVim already exists, the files are\r\n    opened in separate tabs in a new instance of the editor.\r\n\r\n    ```sh\r\n    vimer -t foo.txt bar.txt baz.txt\r\n    ```\r\n\r\n 4. Pipe the standard output of a command into the standard input of\r\n    GVim or MacVim.  Use the `-t` option to open it in a separate tab.\r\n\r\n    ```sh\r\n    ls -l | vimer -\r\n    ls -l | vimer -t -\r\n    ```\r\n\r\n 5. Launch a new instance of GVim or MacVim with a specific server\r\n    name.\r\n\r\n    ```sh\r\n    vimer -s FOO\r\n    ```\r\n\r\n    If the specified server name is already being used by another\r\n    instance of the editor, a number postfix is applied (e.g. `FOO1`,\r\n    `FOO2`, etc.) until a free name is encountered.\r\n\r\n 6. Edit files in GVim or MacVim with a specific server name.\r\n\r\n    ```sh\r\n    vimer -s FOO foo.txt bar.txt baz.txt\r\n    ```\r\n\r\n    If an instance of GVim or MacVim with the specified server name is\r\n    already running, this command opens the files in that instance of\r\n    the editor.  If such an instance of the editor does not exist,\r\n    then the first server with the number postfix will be used.\r\n\r\n    If there is no existing instance of the editor with a matching\r\n    server name or a server name with number postfix, the files are\r\n    opened in separate buffers in a new instance of the editor with\r\n    the specified server name, or a server name with number postfix.\r\n\r\n 7. Enable a context menu option called *Edit with GVim* for files on\r\n    Windows.\r\n\r\n    ```bat\r\n    vimer --enable\r\n    ```\r\n\r\n    After executing the above command, on right clicking a file, an\r\n    option called *Edit with GVim* should appear in the context menu.\r\n    Selecting this option opens the file in an existing instance of\r\n    GVim if it exists.  If no existing instance of GVim already\r\n    exists, then the file is opened in a new instance of GVim.\r\n\r\n    A similar context menu option called *Edit with existing Vim* is\r\n    already provided by the GVim installer for Windows.  But this\r\n    option is provided in Vimer anyway because combining this option\r\n    with `-t` creates a context menu option to open files in separate\r\n    tab pages, as explained in the next point.  Such a context menu\r\n    option is not provided by the GVim installer for Windows.\r\n\r\n 8. Enable a context menu option called *Edit with GVim tab* for files\r\n    on Windows.\r\n\r\n    ```bat\r\n    vimer -t --enable\r\n    ```\r\n\r\n 9. Disable context menu options on Windows.\r\n\r\n    ```bat\r\n    vimer --disable\r\n    vimer -t --disable\r\n    ```\r\n\r\n    The `--enable` and `--disable` options are not supported for Linux\r\n    and Mac.  See the [Context Menu](#context-menu) section below to\r\n    read how to create such context menu option in other desktop\r\n    environments.\r\n\r\n10. For more details on how to use Vimer, execute the following\r\n    command.\r\n\r\n    ```sh\r\n    vimer --help\r\n    ```\r\n\r\nUsers who are very used to typing `vi`, `vim`, `gvim` or `mvim` to run\r\nthe editor and find it difficult to type `vimer` might want to rename\r\nthis script.  For example, a user very used to typing `vi`, might want\r\nto rename this script from `vimer.cmd` to `vi.cmd` on Windows, or to\r\n`vi` on Linux or Mac.\r\n\r\n\r\nTroubleshooting\r\n---------------\r\n\r\n 1. When the script is executed from a 32 bit [Console2][C2] window\r\n    running on a 64 bit Windows operating system, the script fails\r\n    with the following error.\r\n\r\n    ```\r\n    ERROR: The system was unable to find the specified registry key or value.\r\n    ```\r\n\r\n    To work around the issue, execute the script in the native Windows\r\n    Command Prompt, or install the 64 bit Console2 application and\r\n    execute the script from a 64 bit Console2 window.\r\n\r\n 2. After the script is renamed to `gvim` on Linux or `mvim` on Mac,\r\n    running `gvim` or `mvim` with a filename as argument may still\r\n    open the file in a new instance of the editor, not in an existing\r\n    instance of the editor, even if such an instance already exists.\r\n\r\n    If this happens, it is very likely that the `gvim` or `mvim`\r\n    command is still running GVim or MacVim, respectively, not Vimer.\r\n\r\n    To confirm, execute the following command on Linux.\r\n\r\n    ```sh\r\n    gvim --version\r\n    ```\r\n\r\n    Or the following command on Mac.\r\n\r\n    ```sh\r\n    mvim --version\r\n    ```\r\n\r\n    If the string \"VIM\" appears in the first line of the output, it is\r\n    GVim or MacVim.\r\n\r\n    If it is confirmed that running `gvim` on Linux, or `mvim` on Mac\r\n    executes GVim or MacVim, respectively, ensure that the path where\r\n    this script is located appears before the path where GVim or\r\n    MacVim is located in the PATH environment variable.\r\n\r\n    Further, on Linux or Mac, set the `VIM_CMD` environment variable\r\n    to the absolute path of GVim or MacVim.  For more details about\r\n    this, see the next point.\r\n\r\n 3. When the script is renamed to `gvim` on Linux or `mvim` on Mac,\r\n    and `gvim` or `mvim` is run, the shell may hang.  If the `VIM_CMD`\r\n    environment variable is not set, internally, the script invokes\r\n    the `gvim` command on Linux or the `mvim` command on Mac to edit\r\n    files.  But when this script itself is named as `gvim` on Linux or\r\n    `mvim` on Mac, invoking `gvim` or `mvim`, respectively, ends up\r\n    invoking itself thereby resulting in an infinite recursion.\r\n\r\n    To resolve the issue, set the `VIM_CMD` environment variable to\r\n    the absolute path of GVim.  Here is an example for Linux.\r\n\r\n    ```sh\r\n    export VIM_CMD=/usr/bin/gvim\r\n    ```\r\n\r\n    Here is an example for Mac.\r\n\r\n    ```sh\r\n    export VIM_CMD=/usr/local/bin/mvim\r\n    ```\r\n\r\n    Consider adding this to the shell's initialization file (e.g.\r\n    ~/.bashrc) so that this environment variable is persistent and\r\n    available across shell sessions.\r\n\r\n    As a workaround, consider renaming the script to something other\r\n    than `gvim` or `mvim`, perhaps `vi` which is short and sweet and\r\n    has the additional advantage that no matter what system it is, one\r\n    only has to remember to type `vi` to edit files.\r\n\r\n[C2]: http://sourceforge.net/projects/console/\r\n\r\n\r\nContext Menu\r\n------------\r\n\r\nThis section descibes how to add context menu option for files that\r\nopens files in an existing instance of GVim or MacVim in various\r\ndesktop environments.  This section does not require the use of Vimer.\r\n\r\nThe steps provided in the sections below create a context menu option\r\nto edit files in new buffers.  To edit files in new tabs instead, use\r\nthe `--remote-tab-silent` option instead of the `--remote-silent`\r\noption in the sections below.\r\n\r\n\r\n### Windows ###\r\n\r\nThe following steps have been found to work fine on Windows XP and\r\nWindows 7.  These steps probably work fine on other versions of\r\nWindows too.\r\n\r\n 1. Run the following command.\r\n\r\n    ```bat\r\n    regedit\r\n    ```\r\n\r\n 2. Go to `HKEY_CLASSES_ROOT\\*\\shell`.  Right click on the node named\r\n    `shell`, select *New* \u003e *Key*.  Name the new key as `Edit with\r\n    GVim`.\r\n\r\n 3. Then right click on the new node, select *New* \u003e *Key* and name\r\n    the new node as `command`.\r\n\r\n 4. Now `HKEY_CLASSES_ROOT\\*\\shell\\Edit with GVim\\command` should be\r\n    the current node.  On the right-hand pane, double click on\r\n    *(Default)* and enter the command to edit a file in existing GVim.\r\n    Here is an example.\r\n\r\n    ```bat\r\n    \"C:\\Program Files (x86)\\Vim\\vim74\\gvim.exe\" --remote-silent \"%1\"\r\n    ```\r\n\r\n 4. Click *OK*.\r\n\r\nTo remove this context menu option, run `regedit`, go to\r\n`HKEY_CLASSES_ROOT\\*\\shell`, right click on the node for this context\r\nmenu, select *Delete* and click *Yes*.\r\n\r\nAlternatively, run `vimer --enable` to automatically find the path to\r\n`gvim.exe` and create the registry value described above.  To remove\r\nthis registry value, run `vimer --disable`.  To enable or disable\r\nsimilar registry value that creates a context menu option to edit\r\nfiles with existing GVim in a new tab page, run `vimer --tab --enable`\r\nor `vim --tab -disable`, respectively.\r\n\r\n\r\n### Xfce on Linux ###\r\n\r\nThe following steps have been found to work fine on Xfce 4.10 on\r\nDebian 8.0.  These steps probably work fine on Xfce 4 on any Linux\r\ndistribution.\r\n\r\n 1. Run *Thunar*, i.e. *Applications Menu* \u003e *File Manager*.\r\n\r\n 2. From the menu, go to *Edit* \u003e *Configure custom actions*.\r\n\r\n 2. Click the plus icon to add a new custom action..\r\n\r\n 3. Enter the following details.\r\n      - Name: `Edit with GVim`\r\n      - Command: `gvim --remote-silent %F`\r\n      - Icon: vim\r\n\r\n 4. Go to *Apperance Conditions* tab and select *Directories*, *Text\r\n    Files* and *Other Files*.\r\n\r\n 5. Click *OK*.  Click *Close*.\r\n\r\nTo remove this context menu option, follow step 1 again, select the\r\ncontext menu option, click the bin icon to delete the currently\r\nselected action and click *Delete*.\r\n\r\n\r\n### GNOME on Linux ###\r\n\r\nThe following steps have been found to work fine on GNOME 2.28.2 on\r\nCentOS 6.5 and GNOME 3.4.1 on Debian 8.2 (Jessie).  These steps\r\nprobably work fine on GNOME 2 and GNOME 3 on any Linux distribution.\r\nThe steps below need to be performed in a shell.\r\n\r\n 1. On GNOME 2, go to the ~/.gnome2/nautilus-scripts/ directory.\r\n\r\n    ```sh\r\n    cd ~/.gnome2/nautilus-scripts/\r\n    ```\r\n\r\n    On GNOME 3, go to ~/.local/share/nautilus/scripts/ instead.\r\n\r\n    ```sh\r\n    cd ~/.local/share/nautilus/scripts/\r\n    ```\r\n\r\n 2. Now create an executable script that contains the shell command to\r\n    edit files in an existing instance of GVim if it exists.\r\n\r\n    ```sh\r\n    echo 'gvim --remote-silent \"$@\"' \u003e \"Edit with GVim\"\r\n    chmod u+x \"Edit with GVim\"\r\n    ```\r\n\r\nAfter following these steps, open Nautilus (File Browser on GNOME 2,\r\nor Files on GNOME 3), right click on a file, select Scripts \u003e Edit\r\nwith GVim.\r\n\r\nTo remove this context menu option, delete the script for the context\r\nmenu option from ~/.gnome2/nautilus-scripts (GNOME 2) or\r\n~/.local/share/nautilus/scripts (GNOME 3).\r\n\r\n\r\n### Mac ###\r\n\r\nThe following steps have been found to work fine on Mac 10.9.5\r\n(Mavericks).\r\n\r\n 1. Go to *Launchpad*, search for *Automator*, then click on it to\r\n    launch it.  It should display a dialog box to choose a type for\r\n    the new document.  If this is not displayed, click *New Document*\r\n    to display it.\r\n\r\n 2. Select *Service* and click *Choose*.\r\n\r\n 3. In the *Service receives selected* drop-down list, select *files\r\n    or folders*.\r\n\r\n 4. Under *Library*, select *Utilities* and double click *Run Shell\r\n    Script*.\r\n\r\n 5. In the new pane that appears, go to the *Pass Input* drop-down\r\n    list and select *as arguments*.\r\n\r\n 6. Erase all the code in the text box and enter the shell command to\r\n    edit files in an existing instance of MacVim if it exists.  Note\r\n    that the absolute path to MacVim should be used in the command.\r\n\r\n    ```sh\r\n    /usr/local/bin/mvim --remote-silent \"$@\"\r\n    ```\r\n\r\n 7. From the menu, select *File* \u003e *Save*.  Enter `Edit with MacVim`\r\n    as the service name and click *Save*.\r\n\r\n 8. From the menu, select *Automator* \u003e *Quit Automator*.\r\n\r\nTo remove this context menu option, launch Finder, select *Go* \u003e *Go\r\nto Folder*, enter `~/Library/Services`, right click on the workflow\r\nfor this context menu option and select *Move to Trash*.\r\n\r\n\r\nLicense\r\n-------\r\n\r\nThis is free and open source software.  You can use, copy, modify,\r\nmerge, publish, distribute, sublicense, and/or sell copies of it,\r\nunder the terms of the MIT License.  See [LICENSE.md][L] for details.\r\n\r\nThis software is provided \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\r\nexpress or implied.  See [LICENSE.md][L] for details.\r\n\r\n[L]: LICENSE.md\r\n\r\n\r\nSupport\r\n-------\r\n\r\nTo report bugs, suggest improvements, or ask questions, please create\r\na new issue at \u003chttp://github.com/susam/vimer/issues\u003e.\r\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsusam%2Fvimer","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsusam%2Fvimer","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsusam%2Fvimer/lists"}