Max Rothman
Max Rothman
The colored log output is nice when you're working in the terminal, but when working with a non-terminal logging system, you end up with log files that look like this:...
## Description The "comment" keyboard shortcut (cmd+/ on Mac) toggles the presence of a "#" comment character at the beginning of a line. When this keyboard shortcut is used on...
core.matrix has pretty good coverage of the APL primitives, but one notable exception is the [reverse function (monadic ⌽ and ⊖)](https://aplwiki.com/wiki/Reverse). For 2d matrices with native Clojure sequences, one can...
Currently, `eq` only works on numerical matrices because [the protocol implementation uses `==`](https://github.com/mikera/core.matrix/blob/develop/src/main/clojure/clojure/core/matrix/impl/defaults.cljc#L1068-L1070). (Note that this appears to not always have been true, https://github.com/mikera/core.matrix/commit/eb71bb43d401b8bab7701a4e187411e3a6252889 changed the uses of `=` to...
With Clojuredocs examples on, you have to scroll to the bottom of the hover to see problem reports
Slack thread: https://clojurians.slack.com/archives/CBE668G4R/p1670838574590269 In https://github.com/BetterThanTomorrow/calva/issues/1998, I found that no API exists to move the problems report above the hover provider-provided text in the hover pane. However, having to scroll to...
Currently this extension is not capable of recognizing multiline quote-delimited strings. For example: ```bash foo='asdf asdf asdf' echo "$foo" ``` This is a valid bash script. If you place your...
Thanks for building Joinery! I've had a lot of fun playing around with it a little recently, it definitely opens up interesting possibilities. I ran into a couple of small...
### Error Code None ### Describe the bug When I try to open a file from a github repository, nothing happens. Afterwards, the UI is left in an intermediate state...
Resolves #1517 I took a first pass at writing documentation for `@beam`, which was mentioned in the guidelines as if explained elsewhere, but was not actually explained anywhere. This is...
In [this bit of the guidelines](https://github.com/music-encoding/music-encoding/blob/ac400fe7820241bd69ccd20f16c71932d1859a14/source/docs/04-cmn.xml#L577), this passage appears (emphasis mine): > In addition to the explicit encoding of beams accommodated by the [\](https://music-encoding.org/guidelines/v5/elements/beam.html) and [\](https://music-encoding.org/guidelines/v5/elements/beamSpan.html) elements ***and the @beam...