lnav

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 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.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.

  • 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

lnav v0.12.4

Features:

• Log message timestamps are now represented with microsecond
  precision internally instead of just millisecond.
• The log_time and log_level fields can now be hidden.
• The "Op ID:" overlay that is added when the log_opid field is
  manually set on a message can now be hidden by hiding the
  log_opid field.
• Pasting a command snippet when the input focus is on the main
  view will now execute it.
  For this to work: the terminal must support "bracketed-paste"
  mode, which most do;
  and, the pasted content must also start with one of the sigils
  for the desired operation (i.e. : for lnav commands, ; for SQL
  queries, / for searches, and | for scripts).
• Ad

lnav v0.12.4

Features:

• Log message timestamps are now represented with microsecond
  precision internally instead of just millisecond.
• The log_time and log_level fields can now be hidden.
• The "Op ID:" overlay that is added when the log_opid field is
  manually set on a message can now be hidden by hiding the
  log_opid field.
• Pasting a command snippet when the input focus is on the main
  view will now execute it.
  For this to work: the terminal must support "bracketed-paste"
  mode, which most do;
  and, the pasted content must also start with one of the sigils
  for the desired operation (i.e. : for lnav com

lnav v0.12.4

Features:

• Log message timestamps are now represented with microsecond
  precision internally instead of just millisecond.
• The log_time and log_level fields can now be hidden.
• Added a report-access-log script that generates a report that
  is similar to the output of the goaccess
  utility.
• Added a find-msg script that can be used to find the
  next/previous message with a field that matches the value of the
  field in the focused message.
• Added a find-chained-msg script that can be used to find the
  next/previous message where a target field matches the value of
  the source

lnav v0.12.3

Features:

• Files that contain a mixture of log messages from separate
  services (e.g. docker logs) can now be automatically
  de-multiplexed into separate files that lnav can digest.
• The log_opid column on log vtables can now be UPDATEd
  so that you can manually set an opid on log messages that
  don't have one. Setting an opid allows messages to show
  up in the timeline view.
• The Files panel now has a details view on the right side
  that shows extra information about the selec