From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id E95571F453 for ; Tue, 5 Feb 2019 11:10:53 +0000 (UTC) From: Eric Wong To: meta@public-inbox.org Subject: [PATCH 0/6] highlighting cleanups + help update Date: Tue, 5 Feb 2019 11:10:47 +0000 Message-Id: <20190205111053.7155-1-e@80x24.org> List-Id: Experimenting with using Markdown-style "```$LANG" blocks support for our user documentation. It makes the CSS example easier-to-follow when the CSS source is in front of the user. Markdown-style blocks definitely won't be enabled by default for emails. I don't want to encourage people to use Markdown in emails (as that inevitably ends with "which flavor?") and the same mess with privacy/compatibility problems have with HTML mail. But preserving the WYSIWYG nature of plain-text while allowing a tiny subset of Markdown (we already respect it for linkification) might be useful for mailing lists which forward messages from Markdown-supported forums/trackers (e.g. Redmine and ruby-core mailing list). Eric Wong (6): viewvcs: cleanup utf8 handling hlmod: hoist out do_hl_lang sub hlmod: make into a singleton hlmod: do_hl* performs src_escape immediately hlmod: support "```$LANG" blocks in text wwwtext: inline sample CSS and use highlight contrib/css/216dark.css | 30 ++++++++++-------- lib/PublicInbox/HlMod.pm | 70 ++++++++++++++++++++++++++++-------------- lib/PublicInbox/UserContent.pm | 16 +++++----- lib/PublicInbox/ViewVCS.pm | 14 ++------- lib/PublicInbox/WwwText.pm | 35 ++++++++++----------- t/hl_mod.t | 34 ++++++++++++-------- 6 files changed, 114 insertions(+), 85 deletions(-) -- EW