lnav

lnav v0.13.2

Bug Fixes:

• Some keys were not recognized correctly because the
  Kitty keyboard protocol handling was broken at the
  last minute.
• The TUI no longer opens if a bad file name is passed.
• The abbreviated month %b time-conversion was not
  always falling back to English locale, which could
  prevent lnav from starting up.
• The top of the LOG view could move in some cases when
  filtering was enabled.
• Some status bar fields were not always showing
  updates.

lnav v0.13.2

Bug Fixes:

• Kitty keyboard handling was broken at the last minute.
• The TUI no longer opens if a bad file name is passed.
• The abbreviated month %b time-conversion was not
  always falling back to English locale, which could
  prevent lnav from starting up.
• The top of the LOG view could move in some cases when
  filtering was enabled.
• Some status bar fields were not always showing
  updates.

lnav v0.13.1

Features:

• Initial support for Windows. Configuration should be stored
  in %APPDATA%. The binary is built using msys2. So, it
  depends on msys-2.0.dll being in the same directory. No other
  dependencies should be needed.
• Removed dependency on ncurses during the build. The terminfo
  files are still used during runtime, but fallback terminfo
  files for common terminals are included in the binary.
• Added the postgres_log format. In addition, you can use
  :annotate on a statement error line (e.g. syntax error
  at or near "null" at character 522) to attach an annotation
  with the statement and a pointer to the location of the error.
• Added the mysql_gen_log, mysql_error_log, and mysql_slow_log
  formats. There is also a mysql_slow_stat

lnav v0.13.1

Features:

• Initial support for Windows. Configuration should be stored
  in %APPDATA%. The binary is built using msys2. So, it
  depends on msys-2.0.dll being in the same directory. No other
  dependencies should be needed.
• Removed dependency on ncurses during the build. The terminfo
  files are still used during runtime, but fallback terminfo
  files for common terminals are included in the binary.
• Added the postgres_log format. In addition, you can use
  :annotate on a statement error line (e.g. syntax error
  at or near "null" at character 522) to attach an annotation
  with the statement and a pointer to the location of the error.

lnav v0.13.1

Features:

• Initial support for Windows. Configuration should be stored
  in %APPDATA%. The binary is built using msys2. So, it
  depends on msys-2.0.dll being in the same directory. No other
  dependencies should be needed.
• Removed dependency on ncurses during the build. The terminfo
  files are still used during runtime, but fallback terminfo
  files for common terminals are included in the binary.
• Added the postgres_log format. In addition, you can use
  :annotate on a statement error line (e.g. syntax error
  at or near "null" at character 522) to attach an annotation
  with the statement and a pointer to the location of the error.

lnav v0.13.0

Interface changes:

• The prompt is now a custom implementation instead of readline.
  Some highlights:

  • In the DB prompt: pressing CTRL+L will reformat the query and
    switch the prompt to multi-line mode; error locations will be
    highlighted.

  • In multi-line mode, you can click and drag the status bar above
    the prompt to resize the prompt.

  • Pressing CTRL+O in the prompt will transfer the prompt to
    contents to Visual Studio Code or the default text editor on
    macOS.
    You can then edit the file and run it from the | prompt with:

    |saved-prompt
    

  • When edi

lnav v0.13.0

Interface changes:

• The prompt is now a custom implementation instead of readline.
  Some highlights:

  • In the DB prompt: pressing CTRL+L will reformat the query and
    switch the prompt to multi-line mode; error locations will be
    highlighted.

  • In multi-line mode, you can click and drag the status bar above
    the prompt to resize the prompt.

  • Pressing CTRL+O in the prompt will transfer the prompt to
    contents to Visual Studio Code or the default text editor on
    macOS.
    You can then edit the file and run it from the | prompt with:

    |saved-prompt
    

  • When e

lnav v0.13.1

Features:

• Initial support for Windows. Configuration should be stored
  in %APPDATA%. The binary is built using msys2. So, it
  depends on msys-2.0.dll being in the same directory. No other
  dependencies should be needed.
• Removed dependency on ncurses during the build. The terminfo
  files are still used during runtime, but fallback terminfo
  files for common terminals are included in the binary.
• Added the postgres_log format.

Interface changes:

• If all the log messages in the LOG view are hidden, a notice
  will be displayed that describes the filters that are in
  effect.

Bug Fixes:

• Fix a crash on startup for

lnav v0.13.0

Interface changes:

• The prompt is now a custom implementation instead of readline.
  Some highlights:

  • In the DB prompt: pressing CTRL+L will reformat the query and
    switch the prompt to multi-line mode; error locations will be
    highlighted.

  • In multi-line mode, you can click and drag the status bar above
    the prompt to resize the prompt.

  • Pressing CTRL+O in the prompt will transfer the prompt to
    contents to Visual Studio Code or the default text editor on
    macOS.
    You can then edit the file and run it from the | prompt with:

    |saved-prompt
    

  • When e

lnav v0.13.0

Interface changes:

• The prompt is now a custom implementation instead of readline.
  Some highlights:

  • In the DB prompt: pressing CTRL+L will reformat the query and
    switch the prompt to multi-line mode; error locations will be
    highlighted.

  • In multi-line mode, you can click and drag the status bar above
    the prompt to resize the prompt.

  • Pressing CTRL+O in the prompt will transfer the prompt to
    contents to Visual Studio Code or the default text editor on
    macOS.
    You can then edit the file and run it from the | prompt with:

    |saved-prompt
    

  • When e

lnav v0.13.0

Interface changes:

• The prompt is now a custom implementation instead of readline.
  Some highlights:

  • In the DB prompt: pressing CTRL+L will reformat the query and
    switch the prompt to multi-line mode; error locations will be
    highlighted.

  • In multi-line mode, you can click and drag the status bar above
    the prompt to resize the prompt.

  • Pressing CTRL+O in the prompt will transfer the prompt to
    contents to Visual Studio Code or the default text editor on
    macOS.
    You can then edit the file and run it from the | prompt with:

    |saved-prompt
    

  • When editing a regular expression, like the search prompt or
    for a filter, if the current pattern matches a line in the<