From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/10651 Path: news.gmane.org!not-for-mail From: John MacFarlane Newsgroups: gmane.text.pandoc Subject: Re: Use of RCS with pandoc YAML blocks - SOLVED Date: Wed, 20 Aug 2014 09:32:35 -0700 Message-ID: <20140820163235.GA18332@localhost.hsd1.ca.comcast.net> References: <19f1dbef-ad4e-401e-b549-dd2154c9c531@googlegroups.com> <20140818194437.GB35861@dhcp-128-32-252-28.lips.berkeley.edu> <20140819164539.GF17247@localhost.hsd1.ca.comcast.net> <9326fed8-88cc-44ee-a3bf-574311e40da9@googlegroups.com> <9caf551f-a3ff-4d61-bf91-389f7260db03@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Trace: ger.gmane.org 1408552381 5040 80.91.229.3 (20 Aug 2014 16:33:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 20 Aug 2014 16:33:01 +0000 (UTC) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-X-From: pandoc-discuss+bncBCJZJHG45QDBBNM32OPQKGQEFQS4C2Y-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Wed Aug 20 18:32:55 2014 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-ie0-f192.google.com ([209.85.223.192]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XK8og-0003dx-G8 for gtp-pandoc-discuss@m.gmane.org; Wed, 20 Aug 2014 18:32:54 +0200 Original-Received: by mail-ie0-f192.google.com with SMTP id rl12sf530426iec.19 for ; Wed, 20 Aug 2014 09:32:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=from:date:to:subject:message-id:references:mime-version:in-reply-to :user-agent:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe:content-type :content-disposition; bh=XrSVq8uwPZC+vCj5ahDGoVsgVisNIqEAYQXpke7H/Ks=; b=y67rHwXMefsiiDNgcZD294jy+uSPIhSD5rLzZsXo8KsRwg6n8llYyEKWFul5p/65Fj HsJZ0XbC3c7gRedE1hQXkPTp2iYgADgJzABDbcz98Hl9q5Lej4BdQJ+HFD2ToPH1z4pT dHTp8L8BKGpv7XEVfGyXb0yXFhFM3wKyFsI9f17tdw5Pf7iGkvjJNkDnjKDYYNYS5KQj sA4Ki1sov+Zc+d2zYXEMAZFQo1n5gMM69+uS+Ke1K0LnaaudvhM9RujWJxGsBkWuzcnY kKw+ecnJaV8JHst0vyZxuhCddBGSzeOxjgoASzLKWs3Fsh2JYrliDUz1VmwZOUmvvKll jsdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:subject:message-id:references :mime-version:in-reply-to:user-agent:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type:content-disposition; bh=XrSVq8uwPZC+vCj5ahDGoVsgVisNIqEAYQXpke7H/Ks=; b=ZIwfpMvTgn/aV2Owt7uj+v6w+VVRgV1R+GzwpTvh15bL/rGW5Lif3BksWR77fIytMe wdieLQ3kJZCfPbmFIfRawOSO0HnvKrYr/+jzZAD43nkHrEGbSCQ2Qjp0GvzTe/zRUZTE MPUhsub9v4YCGMx3gC05y74HIriMm2EW0zG2Uqv4Gq0JdfpP6F7Nj0eSK9FUgiInqeq5 u4YEvZNCkN5eb8S7yBfCdQHcvB0aQVjEc1N9bOyZtpLHapym/IkdWjxaVYLsnZQlmuni El14RNDGjmu2sh0HLy9vhow9AiqXq4nBoGSifrirxJAHO8Pk/44xqF5/LNUmqE/twnud nL X-Received: by 10.50.138.69 with SMTP id qo5mr353088igb.7.1408552373619; Wed, 20 Aug 2014 09:32:53 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 10.50.80.109 with SMTP id q13ls3286195igx.20.canary; Wed, 20 Aug 2014 09:32:52 -0700 (PDT) X-Received: by 10.66.249.73 with SMTP id ys9mr26681663pac.9.1408552372830; Wed, 20 Aug 2014 09:32:52 -0700 (PDT) Original-Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by gmr-mx.google.com with ESMTPS id mk1si1542708pdb.1.2014.08.20.09.32.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Aug 2014 09:32:51 -0700 (PDT) Received-SPF: pass (google.com: domain of jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org designates 209.85.220.53 as permitted sender) client-ip=209.85.220.53; Original-Received: by mail-pa0-f53.google.com with SMTP id rd3so12643798pab.40 for ; Wed, 20 Aug 2014 09:32:51 -0700 (PDT) X-Gm-Message-State: ALoCoQnEHSVcdsgV7Ny1hSA08JjIQoYrWkGiIOISHIANeB1ptVXpj9PJSwXO3u57dKzzJt+G7hOo X-Received: by 10.68.88.161 with SMTP id bh1mr54787308pbb.6.1408552371703; Wed, 20 Aug 2014 09:32:51 -0700 (PDT) Original-Received: from johnmacfarlane.net (li55-134.members.linode.com. [74.82.3.134]) by mx.google.com with ESMTPSA id z4sm9064493pdp.69.2014.08.20.09.32.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Aug 2014 09:32:51 -0700 (PDT) Original-Received: by johnmacfarlane.net (Postfix, from userid 1000) id DF226A15C; Wed, 20 Aug 2014 12:35:46 -0400 (EDT) In-Reply-To: <9caf551f-a3ff-4d61-bf91-389f7260db03-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> X-PGP-Key: http://johnmacfarlane.net/jgm.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-Original-Sender: jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org designates 209.85.220.53 as permitted sender) smtp.mail=jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Content-Disposition: inline Xref: news.gmane.org gmane.text.pandoc:10651 Archived-At: +++ Pete Phillips [Aug 20 14 08:42 ]: > Hmm. OK. > I'll junk that idea then. So the code I used above really did work on > the previous version of pandoc. Not the end of the world if I can't > reproduce it now. > Something happened in between 1.12 and 1.13 which dealt with the > quoting of the dollar sign (perhaps only in the YAML header ?). The difference is explained by the following item in the changelog: + Inline math must have nonspace before final `$` (#1313). In 1.12.4, your RCS string was being erroneously parsed as LaTeX math. This had the good consequence (for you) that it was rendered verbatim, without escaping the $'s. But this was a bug in the markdown reader, which has now been fixed. > If it was possible to revert to that behaviour for the YAML block I > would be a happy bunny. Is that possible ? Sorry, no. I did think of a workaround which is a bit kludgy, but might work. Suppose you defined a do-nothing macro \noop{..}, then enclosed your RCS in that: \noop{\RCS $blah blah $} This will be parsed as raw latex, and the whole thing will go through the writer without escaping. (You'll need to make sure you're using --parse-raw with the reader, as you probably already are.) Maybe it's even possible to define a macro in your preamble: \def\rcs{#1}{\RCS #1} and then just do \rcs{$blah blah $} I haven't tested this, though.