From 4e2ea0ed7f5c48867964f42621540fb1b0effb5c Mon Sep 17 00:00:00 2001 From: Roman Scherer Date: Wed, 30 Oct 2024 21:27:13 +0100 Subject: [PATCH] Update docs --- doc/modules/ROOT/pages/debugging/logging.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/modules/ROOT/pages/debugging/logging.adoc b/doc/modules/ROOT/pages/debugging/logging.adoc index e3dddd084..9aafa335a 100644 --- a/doc/modules/ROOT/pages/debugging/logging.adoc +++ b/doc/modules/ROOT/pages/debugging/logging.adoc @@ -49,7 +49,7 @@ Its usage is mostly self-describing, since each command has its keybinding attac To use CIDER Log Mode, there two main ways to get started: -* `M-x cider-log-frameworks`, to see the available logging frameworks. If your logging framework is supported but not shown, see the troubleshooting section. +* `M-x cider-log-show-frameworks`, to see the available logging frameworks. If your logging framework is supported but not shown, see the troubleshooting section. * `M-x cider-log-event`, which uses transient-mode and will not immediately show the logs (you should use transient-mode to show the `+*cider-log*+` buffer) * `M-x cider-log-show` is a newer function that intends to be an "all-in-one" command, intended for a streamlined experience, which can be useful to get started, or for casual usage. ** It doesn't use transient-mode - it aims to do everything in one step @@ -179,7 +179,7 @@ or Clojure CLI aliases. |=== | Command | Keyboard shortcut | Description -| `cider-log-frameworks` +| `cider-log-show-frameworks` | kbd:[C-c M-l f a] | Show all available log frameworks in a buffer.