cli/dev/website/docs/config/editor.md

parent, nav_order, description

parent	nav_order	description
Configuration	100	How to configure a custom editor for dev's /editor command

Editor configuration

Dev allows you to configure your preferred text editor for use with the /editor command. The editor must be capable of running in "blocking mode", meaning the command line will wait until you close the editor before proceeding.

Using --editor

You can specify the text editor with the --editor switch or using editor: in dev's yaml config file.

Environment variables

Dev checks the following environment variables in order to determine which editor to use:

1. DEV_EDITOR
2. VISUAL
3. EDITOR

Default behavior

If no editor is configured, dev will use these platform-specific defaults:

• Windows: notepad
• macOS: vim
• Linux/Unix: vi

Using a custom editor

You can set your preferred editor in your shell's configuration file (e.g., .bashrc, .zshrc):

export DEV_EDITOR=vim

Popular Editors by Platform

macOS

1. vim

   export DEV_EDITOR=vim
   

2. Emacs

   export DEV_EDITOR=emacs
   

3. VSCode

   export DEV_EDITOR="code --wait"
   

4. Sublime Text

   export DEV_EDITOR="subl --wait"
   

5. BBEdit

   export DEV_EDITOR="bbedit --wait"
   

Linux

1. vim

   export DEV_EDITOR=vim
   

2. Emacs

   export DEV_EDITOR=emacs
   

3. nano

   export DEV_EDITOR=nano
   

4. VSCode

   export DEV_EDITOR="code --wait"
   

5. Sublime Text

   export DEV_EDITOR="subl --wait"
   

Windows

1. Notepad

   set DEV_EDITOR=notepad
   

2. VSCode

   set DEV_EDITOR="code --wait"
   

3. Notepad++

   set DEV_EDITOR="notepad++ -multiInst -notabbar -nosession -noPlugin -waitForClose"
   

Editor command arguments

Some editors require specific command-line arguments to operate in blocking mode. The --wait flag (or equivalent) is commonly used to make the editor block until the file is closed.

Troubleshooting

If you encounter issues with your editor not blocking (returning to the prompt immediately), verify that:

1. Your editor supports blocking mode
2. You've included the necessary command-line arguments for blocking mode
3. The editor command is properly quoted if it contains spaces or special characters, e.g.:

   export DEV_EDITOR="code --wait"