From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Kraai Subject: Re: [PATCH] Documentation: remove unnecessary backslashes Date: Wed, 20 Jan 2016 13:35:12 -0800 Message-ID: <20160120213512.GA10192@ftbfs.org> References: <1453310497-7971-1-git-send-email-kraai@ftbfs.org> <20160120182421.GA27562@sigill.intra.peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org, Philip Oakley , Matthew Kraai To: Jeff King X-From: git-owner@vger.kernel.org Wed Jan 20 22:35:25 2016 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aM0PU-00010Z-A1 for gcvg-git-2@plane.gmane.org; Wed, 20 Jan 2016 22:35:24 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752869AbcATVfT (ORCPT ); Wed, 20 Jan 2016 16:35:19 -0500 Received: from 46-22-115-26.ip.axbyte.se ([46.22.115.26]:39006 "EHLO kvm.ftbfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757964AbcATVfS (ORCPT ); Wed, 20 Jan 2016 16:35:18 -0500 Received: from kraai by kvm.ftbfs.org with local (Exim 4.84) (envelope-from ) id 1aM0PI-0002gp-9T; Wed, 20 Jan 2016 13:35:12 -0800 Content-Disposition: inline In-Reply-To: <20160120182421.GA27562@sigill.intra.peff.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Hi, On Wed, Jan 20, 2016 at 01:24:21PM -0500, Jeff King wrote: > On Wed, Jan 20, 2016 at 09:21:37AM -0800, Matt Kraai wrote: > > -'@\{\}', e.g. 'master@\{yesterday\}', 'HEAD@\{5 minutes ago\}':: > > +'@{}', e.g. 'master@\{yesterday\}', 'HEAD@{5 minutes ago}':: > > I see you didn't tweak the middle one here, because it _does_ look like > an attribute. Does asciidoctor actually remove the backslashes there? Yes, asciidoctor appears to remove the backslashes in some cases but not others. I removed the backslashes from the source if it did not remove them. I verified that the asciidoc output isn't affected. > > -'@\{\}', e.g. 'master@\{1\}':: > > +'@{}', e.g. 'master@\{1\}':: > > Ditto here for "1". IMHO asciidoctor's behavior is somewhat crazy, as it > means you have to know arcane quoting rules to get correct output (you > cannot just err on the side of quoting). But it's probably still worth > working around. I couldn't find any documentation of asciidoctor's behavior. I didn't try figuring the behavior out from asciidoctor's source code. -- Matt https://ftbfs.org/~kraai/