ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Linter Inline Errors

by alexkuz ST3

Shows linting errors inline with Phantom API

Details

Installs

  • Total 4K
  • Win 3K
  • OS X 910
  • Linux 578
Dec 7 Dec 6 Dec 5 Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 Oct 24 Oct 23
Windows 0 2 0 3 1 5 1 1 3 3 0 1 3 2 2 1 1 0 4 0 3 7 3 4 2 6 5 4 3 4 2 1 3 1 1 3 5 1 2 0 1 2 0 2 2 2
OS X 0 1 0 0 2 0 1 1 1 1 0 0 0 0 0 1 1 1 1 1 0 0 1 2 2 0 3 0 2 0 2 0 1 4 1 0 0 0 0 0 2 1 0 2 1 0
Linux 0 1 0 1 1 0 0 0 0 1 0 1 1 0 0 2 0 0 1 0 0 0 1 0 0 1 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 1 1 2

Readme

Source
raw.​githubusercontent.​com
This is an experimental package and apparently it does not work very well. Don’t expect much of it.

If you still need decent error displaying (I bet you do), consider using SublimeLinter v4

SublimeLinter-inline-errors

Shows linting errors inline with Phantom API

Much experimental. Very beta.

Works like this:

Or this:

Installation

  • Open Package Control: Install Package
  • Find and install SublimeLinter Inline Errors package

Settings

{
  // Show warning hints
  "show_warnings": true,

  // Show error hints
  "show_errors": true,

  // Show summary on top of the view
  "show_summary": true,

  // Hint font size
  "font_size": "0.9rem",

  // If true, shows hint inline, otherwise below the line
  "show_inline_text": true,

  // Hint behaviour when caret is on hinted line
  //
  // "inline" - shows inline hint
  // "below" - shows hint below the line
  // "none" - hides hint
  "hint_on_selected_line": "none",

  // Most left position for the hint in line (unless viewport is narrower than that)
  "min_offset": 100,

  // Max width for the block shown below the line
  "max_block_width": 80,

  // Minimal gap between the text line and the hint
  "min_gap": 5,

  // Theme file for inline hints
  "inline_theme": "Packages/SublimeLinter Inline Errors/themes/inline.html",

  // Theme file for below-the-line hints
  "below_theme": "Packages/SublimeLinter Inline Errors/themes/below.html",

  // Theme file for summary hints
  "summary_inline_theme": "Packages/SublimeLinter Inline Errors/themes/summary-inline.html",

  // Theme file for summary hints
  "summary_below_theme": "Packages/SublimeLinter Inline Errors/themes/summary-below.html",

  // Symbol used as a warning hint prefix
  "warning_symbol": "⚠️",

  // Symbol used as an error hint prefix
  "error_symbol": "⛔",

  // Symbol used in the offset
  "offset_symbol": " ",

  // Offset symbol color (set your background color here to hide the offset symbols)
  "offset_color": "553333",

  // Inline warning text color
  "inline_warning_color": "DDCC66",

  // Inline warning background color
  "inline_warning_background_color": "",

  // Inline error text color
  "inline_error_color": "DD6666",

  // Inline error background color
  "inline_error_background_color": "",

  // Below-the-line warning text color
  "below_warning_color": "FFFFFF",

  // Below-the-line warning background color
  "below_warning_background_color": "BBAA33",

  // Below-the-line error text color
  "below_error_color": "FFFFFF",

  // Below-the-line error background color
  "below_error_background_color": "993333",

  // Summary text color
  "summary_color": "FFFFFF",

  // Summary background color
  "summary_background_color": "993333",

  // Maximum number of words in inline hint
  "inline_max_words": 30,

  // Prints debug messages in console
  "debug": false
}

Known issues

  • By default, inline hint is hidden for a current line, since Phantom window can mess up with your code while you editing it. If you feel lucky, you can always show inline hint by setting hint_on_selected_line: "inline"
  • If you click between code line and the hint, nothing happens (it should put cursor at the end of a line). It's a bit annoying. Unfortunately, there's no way to make phantom transparent for pointer events (so the click would be handled by the editor), making a hidden link there to handle the click manually also doesn't work well.