branch: elpa/cider
commit 8a186ff8789aa8b2cadc85ba4f06fec0956596a3
Author: vemv <v...@users.noreply.github.com>
Commit: Bozhidar Batsov <bozhi...@batsov.dev>
Docs: fix some unordered lists
---
doc/modules/ROOT/pages/indent_spec.adoc | 20 ++++++++++----------
doc/modules/ROOT/pages/troubleshooting.adoc | 12 ++++++------
2 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/doc/modules/ROOT/pages/indent_spec.adoc
b/doc/modules/ROOT/pages/indent_spec.adoc
index 145779c479..9915eeb94b 100644
--- a/doc/modules/ROOT/pages/indent_spec.adoc
+++ b/doc/modules/ROOT/pages/indent_spec.adoc
@@ -165,18 +165,18 @@ so you wouldn't have to specify it.
For that to happen, it's most recommended that you write idiomatic Clojure
macros:
* If your macro is analog to a clojure.core one, name it identically
- * e.g. name your macro `defprotocol`, not `my-defprotocol`
- * (this is intentful usage of Clojure's namespace system)
+ ** e.g. name your macro `defprotocol`, not `my-defprotocol`
+ *** (this is intentful usage of Clojure's namespace system)
* If your macro is analog to a clojure.core one, mirror all its arglists
- * The exact names that you choose for your args do not matter
- * It's the structure of the arglists that have to match.
- * It doesn't matter if you express a given arg as a name, or as a
destructured map/vector.
+ ** The exact names that you choose for your args do not matter
+ ** It's the structure of the arglists that have to match.
+ ** It doesn't matter if you express a given arg as a name, or as a
destructured map/vector.
* Name 'body' args like using clojure.core customs
- * good: `[opts body]`
- * bad: `[opts etc]`
- * good: `[& body]`
- * bad: `[& etc]`
- * Other commonly accepted names include `forms`, `clauses`, etc.
+ ** good: `[opts body]`
+ ** bad: `[opts etc]`
+ ** good: `[& body]`
+ ** bad: `[& etc]`
+ ** Other commonly accepted names include `forms`, `clauses`, etc.
You certainly don't _have_ to follow these suggestions - it's only for your
convenience,
as the indentation produced by CIDER will be better.
diff --git a/doc/modules/ROOT/pages/troubleshooting.adoc
b/doc/modules/ROOT/pages/troubleshooting.adoc
index 282ed61304..803a24bb3d 100644
--- a/doc/modules/ROOT/pages/troubleshooting.adoc
+++ b/doc/modules/ROOT/pages/troubleshooting.adoc
@@ -359,10 +359,10 @@ If any interactive feature is being shortcircuited for
you with the message `No
that's due to one of the following reasons:
* You're evaluating code in a buffer from a project that hasn't started a repl
- * You can fix this by switching instead to a project that has.
- * You can also, simply, start a repl in the current project.
+ ** You can fix this by switching instead to a project that has.
+ ** You can also, simply, start a repl in the current project.
* There's a bug in the CIDER/Sesman integration
- * Session linking generally works by determining whether the current buffer
is related to the classpath of some REPL.
- * You can obtain debug info echoed to the `*messages*` buffer by running
`M-x cider-debug-sesman-friendly-session-p` on the problematic buffer.
- * By reading it, you might be able to determine why CIDER failed to see
the relationship between `(buffer-filename)` and the classpath.
- * Feel free to created a detailed GitHub issue including this information.
+ ** Session linking generally works by determining whether the current buffer
is related to the classpath of some REPL.
+ ** You can obtain debug info echoed to the `*messages*` buffer by running
`M-x cider-debug-sesman-friendly-session-p` on the problematic buffer.
+ *** By reading it, you might be able to determine why CIDER failed to see
the relationship between `(buffer-filename)` and the classpath.
+ *** Feel free to created a detailed GitHub issue including this information.
