Visual Studio Code Perl

That gives the Visual Studio Code extension a chance to control this behaviour at runtime, does not affect code that does not use fork, can be recognised by the extension by looking at the callstack. This behaviour is the default and can be configured explicitly using:% perl -d:vscode=fork=break. To disable this behaviour:% perl -d:vscode=fork=.


Displays a code outline tree in the explorer pane.

To activate find and expand the 'Code Outline' section near the bottom of the Explorer tab. Ticktick cancel premium.

Language Support

For the outline to work, the language support plugins need to support symbol information.

For the outline to form a tree structure, the language support plugins need to report the entire definition range as part of symbol.

See VS Code issue #34968 and language server protocol issue #132 for a discussion.

Here is a list of languages known to work with Code Outline:

C++C/C++, cquery
HTMLComes with VS Code
JavaLanguage Support for Java(TM) by Red Hat
JavaScriptComes with VS Code
JSONComes with VS Code
MarkdownComes with VS Code
PHPPHP Symbols
TypeScriptComes with VS Code
YAMLYAML Support by Red Hat

Please report any missing extensions and I'll update the list.

Extension Settings

Default settings:

  • doSort: sort the outline.
  • expandNodes: kinds of nodes to be expanded automatically.
  • sortOrder: order to the sort symbols.
  • topLevel: wich symbols include at the topmost scope.

Known Issues

Depending on other extensions you have installed the symbol list may initially return an empty list. Use the 'Refresh' button next to the title to fix this.

Visual Studio Code Perl

Vs Code Vs Visual Studio

  1. Extension for Visual Studio Code - WIP: Provide outline view for Perl.
  2. Perl 6 language support for the Atom IDE powered by App::Perl6LangServer. This Language integration is built on top of atom-languageclient. Features: Diagnostics (i.e. Syntax check errors using perl6 -c).
  3. Perl.logFile: If set, log output is written to the given logfile, instead of displaying it in the vscode output pane. Log output is always appended. Only use during debugging of LanguageServer itself.