Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add `:CodefmtInfo` command to report diagnostics to help users check config / diagnose problems

Open
#234 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
vim
Domain
cli, developer-experience

Research direction

Start with the proposed :CodefmtInfo command and trace how the current buffer, formatter selection, configuration, and last invocation can be accessed. Done means the command produces a report covering the context and diagnostic fields shown in the issue, including the executed command, exit code, and stderr when available.

Written by the indexing model from the issue text.

Description

enhancement

We should have a command called something like :CodefmtInfo that can dump a report on how it's configured wrt the current context and maybe the last known invocation.

For example:

:CodefmtInfo

Current buffer: foo.py
Autoformat [enabled|disabled] [using formatter yapf]
Selected formatter: [yapf]
All available formatters: yapf, black, isort, autopep8

Last invocation at [TIMESTAMP]:
Executed command: yapf -blah ...
Exit code: [0|...]
[Stderr: ...]
Dominant language
Vim Script
Stars
1.1k
Forks
102
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/vim-codefmt

All issues in google/vim-codefmt

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.