[track-state] Tune recognized meta keys

Author: alexander-yakushev

cider-mode.el

@@ -806,17 +806,13 @@ with the given LIMIT."
                          (`"\"light-form\""
                           (push sym enlightened)))
                        ;; FIXME: This matches values too, not just keys.
-                       (when (seq-find (lambda (k)
-                                         (and (stringp k)
-                                              (or (string= "orchard.trace/traced" k)
-                                                  (string= "orchard.profile/profiled" k))))
-                                       meta)
+                       (when (or (nrepl-dict-get meta "orchard.trace/traced")
+                                 (nrepl-dict-get meta "orchard.profile/profiled"))
                          (push sym traced))
                        (when (and do-deprecated (nrepl-dict-get meta "deprecated"))
                          (push sym deprecated))
                        (let ((is-macro (nrepl-dict-get meta "macro"))
-                             (is-function (or (nrepl-dict-get meta "fn")
-                                              (nrepl-dict-get meta "arglists"))))
+                             (is-function (nrepl-dict-get meta "fn")))
                          (cond ((and do-macro is-macro)
                                 (push sym macros))
                                ((and do-function is-function)

doc/modules/ROOT/pages/debugging/profiling.adoc

@@ -2,8 +2,7 @@
 
 CIDER has a simple built-in profiler that can you to quickly measure the running
 time of individual functions. It is similar to wrapping your functions with
-`time` macro, except it records every timing and displays a the summarized
-result.
+`time` macro, except it records every timing and displays a summarized result.
 
 NOTE: Profiling is different from benchmarking. Benchmarking more accurately
 tells you how long the code executes. If you need accurate timing results, use a