On Mon, 29 Oct 2018 at 14:25 Evan Laforge wrote:

Also, when I copy paste the links in the "At the time of writing" section, the backslashes in the search query mess it up. Maybe a markdown rendering step would remove those?

I'm not sure It makes much sense to use {{{...}}} to format the document in the first place. Maybe use normal wiki-text? I can decorate links if this is approved. -- Best, Artem

On Sun, Oct 28, 2018 at 6:24 PM Ben Gamari wrote:

...

Hello everyone,

The Haskell Community Activities Report is coming up and I have prepared the skeleton for GHC's contribution [1]. If you have a project cooking or have recently had a patch land do have a look to make sure it's recognized in the submission.

Cheers,

- Ben

https://ghc.haskell.org/trac/ghc/wiki/Status/Oct18 _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Hi Ben, I see. Have you considered using online converting tools like try-pandoc[1]? Is it still painful? [1]: https://pandoc.org/try/ On Mon, 29 Oct 2018 at 15:32 Ben Gamari wrote:

Artem Pelenitsyn writes:

...

On Mon, 29 Oct 2018 at 14:25 Evan Laforge wrote:

...

Also, when I copy paste the links in the "At the time of writing" section, the backslashes in the search query mess it up. Maybe a markdown rendering step would remove those?

I'm not sure It makes much sense to use {{{...}}} to format the document in the first place. Maybe use normal wiki-text? I can decorate links if this is approved.

This is what I have done in the past. However, it is unfortunately quite labor intensive since I need to convert the document to Wiki markup, then back to TeX for submission.

Instead with this iteration I have decided to try just writing the thing in Markdown and convert to TeX at the end. I was hoping to install a Trac processor for Markdown rendering but sadly Trac put up resistance.

Cheers,

- Ben

Ben, I assume, writing a Pandoc writer for TracWiki shouldn't be that hard. Would that be of any help? -- Best, Artem On Mon, 29 Oct 2018 at 16:39 Ben Gamari wrote:

Artem Pelenitsyn writes:

...

Hi Ben,

I see. Have you considered using online converting tools like try-pandoc[1]? Is it still painful?

I do use Pandoc to convert from Markdown to Latex. However, Pandoc does not support Trac's wiki syntax.

Cheers,

- Ben

On November 12, 2018 5:14:22 AM EST, Simon Peyton Jones via ghc-devs wrote:

Ben

What's the deadline for this?

I have sent the division but I suspect it's not too late to amend it if necessary. Cheers, - Ben

* Under GHC proposals, can you list proposals that are - Accepted but not yet implemented - Accepted and implemented in 8.8, but not in 8.6

Thanks

Simon

| -----Original Message----- | From: ghc-devs On Behalf Of Ben Gamari | Sent: 29 October 2018 01:24 | To: GHC developers | Subject: GHC's Fall 2018 HCAR submission | | Hello everyone, | | The Haskell Community Activities Report is coming up and I have prepared | the skeleton for GHC's contribution [1]. If you have a project cooking or | have recently had a patch land do have a look to make sure it's recognized | in the submission. | | Cheers, | | - Ben | | | https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fghc.haskel | l.org%2Ftrac%2Fghc%2Fwiki%2FStatus%2FOct18&data=02%7C01%7Csimonpj%40mic | rosoft.com%7C1273ad22650740f389de08d63d3d4800%7C72f988bf86f141af91ab2d7cd01 | 1db47%7C1%7C0%7C636763730743640484&sdata=PeAMJVxYq8%2FfTg5QEDjrF2N98ui3 | lJPnQOA6nrufBtg%3D&reserved=0 _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs