editorconfig(1)

πŸ“¦
version 0.12.9+~0.17.1 Β· 3 versions
, in debian trixie, ubuntu noble, ubuntu questing

✨ editorconfig πŸ’…

okay bestie, welcome to editorconfig(1) from the General Commands Manual β€” it's the EditorConfig Command and it is literally here to tell you what your editor should do with your files. no cap. πŸŽ€


🌸 NAME 🌸

editorconfig β€” EditorConfig Command πŸ¦‹


πŸ’– Usage of the editorconfig command line tool πŸ’–

here's the vibe, bestie, straight up:

Usage: editorconfig [OPTIONS] FILEPATH1 [FILEPATH2 FILEPATH3 ...]

so you pass it some paths and it does its thing. obsessed. ✨

now the tea on FILEPATH β˜• β€” it can be a hyphen (-) if you want the path(s) to be read from stdin. and get this, the hyphen can also be specified alongside other file names πŸ‘‘ β€” so in that way, both the file paths coming from stdin and the paths you typed on the command line get used. iconic, fr fr.

and here's the part you gotta remember 🫢: if more than one path is specified on the command line, or the paths are being read from stdin (even if it's only one path read from stdin), the output format becomes INI format instead of those simple key=value lines. the way that changes everything… 😭


πŸŽ€ OPTIONS πŸŽ€

  • -f β€” specify a conf filename that isn't the default .editorconfig. go off, pick your own πŸ’…
  • -b β€” specify version (this one's for the devs, they use it to test compatibility 🧚)
  • -h OR --help β€” print this help message. a little self-care, honestly 🌸
  • --version β€” display version information. main character energy πŸ‘‘

EditorConfig File Format β€” editorconfig-format(5) πŸ“–


lowkey a whole mood: the paths you give it, the format you get back β€” it's giving choices have consequences. πŸ’€

that's the whole page, bestie!! πŸ’– this lil icon was brought to you by EditorConfig πŸ¦‹ and yeah, it's editorconfig(1) β€” catch you in the group chat 🫢✨🌸