[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[nongnu] elpa/cider 5d68d88372 2/3: Tweak `docs/cider/debugging/logging.
From: |
ELPA Syncer |
Subject: |
[nongnu] elpa/cider 5d68d88372 2/3: Tweak `docs/cider/debugging/logging.html` |
Date: |
Tue, 2 Jan 2024 15:59:19 -0500 (EST) |
branch: elpa/cider
commit 5d68d88372be51ca31bdf1b662184a137bed7dbe
Author: vemv <vemv@users.noreply.github.com>
Commit: vemv <vemv@users.noreply.github.com>
Tweak `docs/cider/debugging/logging.html`
---
doc/modules/ROOT/pages/debugging/logging.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/modules/ROOT/pages/debugging/logging.adoc
b/doc/modules/ROOT/pages/debugging/logging.adoc
index 3ee4436088..e061b3e78b 100644
--- a/doc/modules/ROOT/pages/debugging/logging.adoc
+++ b/doc/modules/ROOT/pages/debugging/logging.adoc
@@ -54,7 +54,7 @@ To use CIDER Log Mode, there two main ways to get started:
** It doesn't use transient-mode - it aims to do everything in one step
** It immediately shows the `+*cider-log*+` buffer
-NOTE: any of these commands will only succeed in
+NOTE: Any of these commands will only succeed in
a buffer that has a CIDER repl (https://github.com/vspinu/sesman[Sesman]
session) attached to it.
@@ -70,7 +70,7 @@ By using `M-x cider-log-show`, all setup and rendering will
be performed for you
All these steps are idempotent, so it's safe to run `M-x cider-log-show` more
than once.
-You can refine the setup afterwards (e.g. configuring filtering) by running
`M-x cider-log`.
+You can refine the setup afterwards (e.g. configuring filtering) by running
`M-x cider-log`, `M-x cider-log-consumer`, etc.
=== Via `cider-log-event`
@@ -168,7 +168,7 @@ Timbre support is WIP as well.
TIP: If your logging framework of choice is not currently supported by CIDER
Log Mode,
you can opt to use Clojure's official `tools.logging` façade in your project,
such that you can locally,
unobstrusively tell it to use a supported framework (like Logback) instead of
your project's default one.
-Note that `tools.logging`'s choice of logging backend implementation can be
controlled with the
+Note that its choice of logging backend implementation can be controlled with
the
`-Dclojure.tools.logging.factory` Java system property, which can be cleanly
customized locally via Lein profiles,
or Clojure CLI aliases.