@@ -54,7 +54,7 @@ To use CIDER Log Mode, there two main ways to get started:
54
54
** It doesn't use transient-mode - it aims to do everything in one step
55
55
** It immediately shows the `+*cider-log*+` buffer
56
56
57
- NOTE: any of these commands will only succeed in
57
+ NOTE: Any of these commands will only succeed in
58
58
a buffer that has a CIDER repl (https://github.com/vspinu/sesman[Sesman]
59
59
session) attached to it.
60
60
@@ -70,7 +70,7 @@ By using `M-x cider-log-show`, all setup and rendering will be performed for you
70
70
71
71
All these steps are idempotent, so it's safe to run `M-x cider-log-show` more than once.
72
72
73
- You can refine the setup afterwards (e.g. configuring filtering) by running `M-x cider-log`.
73
+ You can refine the setup afterwards (e.g. configuring filtering) by running `M-x cider-log`, `M-x cider-log-consumer`, etc .
74
74
75
75
=== Via `cider-log-event`
76
76
@@ -168,7 +168,7 @@ Timbre support is WIP as well.
168
168
TIP: If your logging framework of choice is not currently supported by CIDER Log Mode,
169
169
you can opt to use Clojure's official `tools.logging` façade in your project, such that you can locally,
170
170
unobstrusively tell it to use a supported framework (like Logback) instead of your project's default one.
171
- Note that `tools.logging`'s choice of logging backend implementation can be controlled with the
171
+ Note that its choice of logging backend implementation can be controlled with the
172
172
`-Dclojure.tools.logging.factory` Java system property, which can be cleanly customized locally via Lein profiles,
173
173
or Clojure CLI aliases.
174
174
0 commit comments