For new checks and feature suggestions

• shellcheck.net (i.e. the latest commit) currently gives no useful warnings about this
• I searched through https://github.com/koalaman/shellcheck/issues and didn't find anything related

I can't check shellcheck.net because it requires JavaScript.

Here's a snippet or screenshot that shows the problem:

#!/bin/sh
set +x

Hi,

I'm using pandoc (version 2.9.2.1) to convert documents to dokuwiki format.
I ran into a problem using this command:

pandoc input.html -f html -t dokuwiki -o output_dokuwiki.txt --preserve-tabs

Input:

<strong>bold</strong>
<em>italic</em>
<u>underline</u>

Output:

**bold** //italic// underline

Expected output:

**bol

Environment

• PostgreSQL version: All
• PostgREST+ version: 6.0.2 (713b214)

Current state

Currently, Comment on Table

COMMENT ON SCHEMA todos IS
  'Todos object description';

generate a summary for all operations on this resource

 /todos:
    get:
      tags:
        - todos
      summary: Todos object description
      parameters:

But sum

The images are quite nice but sometimes they feel kinda cheap. It would be nice if they could be redrawn with TikZ.
This would give a touch of class to a book that is already beautiful.

Example:

Simple solution:
![TikZ-diagram-simple](https://user-images.githubusercontent.com/22

Well, we need to check all the projects and remove outdated ones.

We declare this in the readme:

However, keep in mind that we don't accept mammoth's shit. Only active and interesting projects with good documentation are added. Dead and abandoned projects will be removed.

But, sadly at this moment, this project looks like a mammoth shit itself.

We really need to fix it. I think

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
I'd like the source code to be automatically clang-formatted according to my settings anytime the code is compiled. That is, don't require me to use the contextual menu or keyboard shortcut to format the code. Just auto-format it; just like the code is auto-compiled too.

Well, ther

Description

Observed in nwolverson/vscode-ide-purescript#142:

When a fast rebuild is triggered and the rebuildCache^[1] is populated the documentation isn't preserved properly in that process.

To Reproduce

With a module like:

module A where

-- | MyType's documentation
type MyType = Int

• This is a bug report
• I searched existing issues before opening this one

Expected behavior

No warning.

Actual behavior

• Double quote to prevent globbing and word splitting.
• d is referenced but not assigned.

None of these are relevant. ShellCheck is never relevant, because it's all about how you run shell commands, while the json-array format doesn't run any s

As we see:

• https://github.com/input-output-hk/cardano-sl/blob/199774af177f05a4ca8741db25dc67ab79d02bcf/docs/how-to/build-cardano-sl-and-daedalus-from-source-code.md

cardano-sl repo contains how-to doc, how to build daedalus - why isn't this doc in daedalus repo?

It not only makes it harder to find for one looking for how to build daedalus, but also :

• confuses where to post issues r

Currently, when doing a push, UCM creates messages like 'Sync branch ' which is not super informative. It is useful to know the namespace hash but it would be nice to know the diff from the previous version as well.

The message comes from here:

https://github.com/unisonweb/unison/blob/master/parser-typechecker/src/Unison/Codebase/Editor/Git.hs#L146-L151

But actually, rig

Description

When I type this into the REPL:

:set prompt "\ESC[34mλ> \ESC[m"

I get a nice purple lambda prompt.

For ghci, you put that command in ~/.ghci and the REPL will run the commands in that file on

There are a number of functions that create https servers for integration tests:

• https://github.com/wireapp/wire-server/blob/b266f9aae3ee8bf31ac83413b7e7f37feb8aa488/services/brig/test/integration/API/Provider.hs#L1519-L1531
• https://github.com/wireapp/wire-server/blob/b266f9aae3ee8bf31ac83413b7e7f37feb8aa488/services/galley/test/integration/API/Teams/LegalHold.hs#L805-L825
• ...? (`git g

This issue is to announce that I'm working on implementing a Miso submission for Realworld. This is aiming to be the most comprehensive Miso example with pages, routing, auth, css, etc.

The only thing it's not gonna cover, at least initially, is full-stack development with shared types. I'll think about adding that (maybe in a separate example?) when

Auto posting rules affect the whole current file and any parent or child file, but not sibling files (with multiple -f options). The docs at https://hledger.org/journal.html#auto-postings-transaction-modifiers are not clear on this. Also auto posting rules' and periodic transaction rules' scope should be mentioned in the https://hledger.org/journal.html#directives reference table, probably.

Wo

Looks like some changes made from String to JSStr broke at least this example.

I was just exploring haste / client side javascript generation from Haskell, and encountered this. I've created a patch for the one example I was working on.

I am not sure if this is the correct fix, but compiles and runs. Chrome run-time error "Tainted canvases may not be exported" occurred, but did not seem t

At the moment the random initialisation is baked into the UpdateLayer class.

We could replace this with either Variates from System.Random.MWC or Random.

Following #338, we should be able to avoid running parcel at link-time and instead ship a pre-bundled rts.js. Some minor adjustments in the js codegen, and the browser backend can take advantage of rts.js and use it to initialize multiple instances at once.

Besides improving linking speed, this also means we can drop npm-utils, which uses a custom Setup.hs to do npm install...whic

Describe the bug

As mentioned on #641, n and note have no clear description in the docs regarding their difference. This can be confusing to newcomers, and their behavior should be documented.

Describe the bug

I expected to see the documentation for default-language and other-languages fields in the build information section of the docs. However, it is not present there. Searching the documentation doesn't help as well.

I found the syntax documentation in "Field Synta

This is something I reach for, perhaps because I'm used to it more than anything. But it might be nice to have Hoogle integrated into the documentation.

Repro: go .cabal file, type quick somewhere in build-depends stanza, a suggestion list appears
Expected: the QuickCheck package is present in the suggestions' list
Instead: the QuickCheck package is absent in the suggestions' list