From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.2 Received: (qmail 17162 invoked from network); 26 Apr 2020 22:59:10 -0000 Received: from bsd.lv (HELO mandoc.bsd.lv) (66.111.2.12) by inbox.vuxu.org with UTF8ESMTPZ; 26 Apr 2020 22:59:10 -0000 Received: from fantadrom.bsd.lv (localhost [127.0.0.1]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 9acba267 for ; Sun, 26 Apr 2020 17:59:06 -0500 (EST) Received: from mail-il1-f179.google.com (mail-il1-f179.google.com [209.85.166.179]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id e6f55313 for ; Sun, 26 Apr 2020 17:59:05 -0500 (EST) Received: by mail-il1-f179.google.com with SMTP id x2so14999696ilp.13 for ; Sun, 26 Apr 2020 15:59:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anjbe-name.20150623.gappssmtp.com; s=20150623; h=from:to:subject:in-reply-to:references:comments:mime-version :content-id:date:message-id; bh=3VhzG47SYZPkTOi/a1ecVR/IMPwsFlTMiFYIGA8eEY0=; b=sAWXMH8MXv/14PZQ945pQ9K6UbG+TaFNbZ9sNmkstPVPfaWvgFVXaJhUM2B/e8Ma5L p+e394N8pWNHIX4h/8b2dJWVJ+D5aI8bAvwAaA7A1EEtyVoadXfOKliSh90i3BBp5S1W GUfObQb8eECZbMYQmFO7Q87I+tmZECqPDp7fx+Tw9O47nsv134F2yGLZ9SAnrg/xej+O AYz2Qwh/whT0IkTT2RxxlSOCk+m1T5btz9yIL5AkjAFYPqLUeOTIUavX4A3sHEoFcHiA sWuCFMdW1WXdfrm1L11dq/MRRAz3rnKBK8HuQptGDbdWsOUK1Lrxng8P6aRliHVk71hO JDzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:comments :mime-version:content-id:date:message-id; bh=3VhzG47SYZPkTOi/a1ecVR/IMPwsFlTMiFYIGA8eEY0=; b=VVPDF3UGP8ZjDBm6SgkzFEDSWsso5Fp+EWIAtK/HdDtPhw+YOFQIMZALossylHNdj2 /G+6DIVUcQKE+wum9EDRtudgWygMgMT5p61yGwWZybxJ2MC6uSqnDaa8ZN0PYlUJszKr ZLMLLy60jHK9i7PAJOgogLJKW70GzPX8SoOgU7x7J79LeT8bjs01zfUqkqFOSefYT2S8 mD1Byyakk0jK5wdpaQWNqeda6JTcZKQW2hOZW4YbiVN9ReX8qmDu+ZdgrajP6L58sbDx lmn1EtKvDtbfreLPCk3BOhBfH5ykOdNqLw0xw/wLBo1N68rM2tJlf4jc9ppStKEm9Cqo g33A== X-Gm-Message-State: AGi0PuZpm/0gaXTtzGdtJ27895j8zHk/srNQY1x/KRKQ0atIBvi1ag6h I6SceTa41Jv1dsVIRQvv4aVzPgyqi3o= X-Google-Smtp-Source: APiQypI5h4cMXhoHTFGaHwMiYprwKswo650IrRqiOQmGrz4EkdgADtlh+j6i3fujHaFcu8dI2QS/rg== X-Received: by 2002:a92:5b50:: with SMTP id p77mr17444103ilb.155.1587941944937; Sun, 26 Apr 2020 15:59:04 -0700 (PDT) Received: from desktop.ajb.soy (c-174-56-122-129.hsd1.nm.comcast.net. [174.56.122.129]) by smtp.gmail.com with ESMTPSA id t74sm787811iof.53.2020.04.26.15.59.04 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 26 Apr 2020 15:59:04 -0700 (PDT) Received: from desktop.ajb.soy (localhost [127.0.0.1]) by desktop.ajb.soy (OpenSMTPD) with ESMTP id 757e487f for ; Sun, 26 Apr 2020 16:59:03 -0600 (MDT) From: "Anthony J. Bentley" To: discuss@mandoc.bsd.lv Subject: Fl Fl for long options In-reply-to: <8a57c2f3270c2455@mandoc.bsd.lv> References: <8a57c2f3270c2455@mandoc.bsd.lv> Comments: In-reply-to schwarze@mandoc.bsd.lv message dated "Sun, 26 Apr 2020 16:41:09 -0500." X-Mailinglist: mandoc-discuss Reply-To: discuss@mandoc.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5228.1587941943.1@desktop.ajb.soy> Date: Sun, 26 Apr 2020 16:59:03 -0600 Message-ID: <14105-1587941943.721637@wO-a.W87w.5Fm4> Hi Ingo, schwarze@mandoc.bsd.lv writes: > Log Message: > ----------- > While we do not recommend the idiom ".Fl Fl long" for long options > because it is an abuse of semantic macros for device-specific > presentational effects Since we've had this discussion before, I feel like I must reiterate my disagreement here. "Fl Fl" is a perfectly natural way to represent long options and it's how I've always done it. And again, I still find it incredibly unintuitive that in OpenBSD's grep(1) manual jumping to the --label tag unintuitively requires searching for "-label" rather than "label". Interpreting "Fl Fl foo" as "empty flag followed by flag foo" simply doesn't make sense to me. I'm aware there are cases like lprm(1) and tset(1) that have an empty flag. Even if those were typical examples-- and they are decidedly not--where in those pages would it ever make sense to use that empty flag adjacent to another? Is there a single manpage anywhere that ever uses "Fl Fl" to mean something *other* than long options? Maybe I just don't understand how this works. But considering the prevalence of Fl Fl as long option, clearly I'm not alone. -- Anthony J. Bentley -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv