From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) by krisdoz.my.domain (8.14.5/8.14.5) with ESMTP id sAGNDCEW015586 for ; Sun, 16 Nov 2014 18:13:13 -0500 (EST) Received: by mail-ie0-f179.google.com with SMTP id rp18so790527iec.24 for ; Sun, 16 Nov 2014 15:13:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:mime-version:content-type :content-id:date:message-id; bh=8OrPeC2k5PgPRpSmAP2H0ZWdyD5pq6H83ucNBBge/r8=; b=j6t0eVkdFTYdyh8Ig9/M5A/QzKvDuaJRhoYqGenN7bzLNLgJpLZdD2EIuldUxlZ4jS gkCGENZ4OsTHau847hHeS6q71NLnHHimUUFXq2GRQ8RKlNJIxi2tAI4J73nUrvuoSp6I VyNqp2A6Q/JtKk9AIbeCN2gVJ8TbPDqzf9/QTeQHmWYxwtuEX3dRWq8Q0MC9g+sWJ5vW 7O5Mu6u+EEQQlK1CB3MG6uJfkzUNVtmsdX42sf1O3RSIm9mSx1XhzXc9NTTZoMJB50SY +Cpmu1wj2rCwyVCPC6Cl4Z5qVDhngd60fxkmMB21zKdBYYdoIAGGJxYXzsZTJw4v5FDy vzDg== X-Gm-Message-State: ALoCoQl54JSFSvBTxVjAcLgMLszXf0lB7cSi138kvkPAUq+8Y5v41svlR62t4rPv7Xb/uUR1B9/Q X-Received: by 10.43.26.142 with SMTP id rm14mr24616167icb.22.1416179585996; Sun, 16 Nov 2014 15:13:05 -0800 (PST) Received: from cathet.us. (75-161-0-121.albq.qwest.net. [75.161.0.121]) by mx.google.com with ESMTPSA id d2sm18025061ioj.30.2014.11.16.15.13.04 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Nov 2014 15:13:05 -0800 (PST) Received: from cathet.us (localhost [127.0.0.1]); by cathet.us. (OpenSMTPD) with ESMTP id 3b53a5cb; for ; Sun, 16 Nov 2014 16:13:03 -0700 (MST) From: "Anthony J. Bentley" To: discuss@mdocml.bsd.lv Subject: Lint feature: macro arguments to No X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10672.1416179582.1@cathet.us> Date: Sun, 16 Nov 2014 16:13:02 -0700 Message-ID: <8174.1416179582@cathet.us> Hi, When working on a manual today, I accidentally wrote: .Ar foo No Ns bar instead of .Ar foo Ns No bar mandoc -Tlint didn't warn me at all, but groff did: mdoc warning: Using a macro as first argument cancels effect of .No This seems like an easy-to-miss mistake that would be useful to catch with mandoc -Tlint. -- Anthony J. Bentley -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv