Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Time zone mailing list <tz@iana.org>, Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man <linux-man@vger.kernel.org>, groff <groff@gnu.org>
Subject: Doubts about a typo fix
Date: Wed, 23 Nov 2022 20:31:22 +0100	[thread overview]
Message-ID: <842adff8-8d8c-b189-8e6c-34be111b8b19@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2375 bytes --]

Hi Paul,

I don't undertstand the commit shown below.  It breaks the '-' symbol, which now 
is a hyphen.  See the table mentioned yesterday:

          ┌──────────────────────────────────────────────────────────────────┐
          │Keycap   Appearance and meaning   Special character and meaning   │
          ├──────────────────────────────────────────────────────────────────┤
          │"        " neutral double quote   \[dq] neutral double quote      │
          │'        ’ closing single quote   \[aq] neutral apostrophe        │
          │-        ‐ hyphen                 \- or \[-] minus sign/Unix dash │
          │\        (escape character)       \e or \[rs] reverse solidus     │
          │^        ˆ modifier circumflex    \(ha circumflex/caret/“hat”     │
          │`        ‘ opening single quote   \(ga grave accent               │
          │~        ˜ modifier tilde         \(ti tilde                      │
          └──────────────────────────────────────────────────────────────────┘


So, at least, it should be (but I believe the initial code was correct):

.q "zic \*\-r @$(date +%s)"

However, I wonder what that \* is intending to do there (I can see no difference 
in my screen with or without it).

Cheers,

Alex

---

commit 918e10e8963b3c0d38d3b5fb8ec9cf08ecd03757
Author: Paul Eggert <eggert@cs.ucla.edu>
Date:   Tue Jul 12 06:26:53 2022 -0700

     * zic.8: fix minus typo

diff --git a/zic.8 b/zic.8
index 0cd0781e..e8816e5b 100644
--- a/zic.8
+++ b/zic.8
@@ -145,7 +145,7 @@ .SH OPTIONS
  31-bit signed integers.
  On platforms with GNU
  .BR date ,
-.q "zic \-r @$(date +%s)"
+.q "zic \*-r @$(date +%s)"
  omits data intended for past timestamps.
  Although this option typically reduces the output file's size,
  the size can increase due to the need to represent the timestamp range



-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2022-11-23 19:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 19:31 Alejandro Colomar [this message]
2022-11-23 21:40 ` Doubts about a typo fix G. Branden Robinson
2022-11-26  2:18   ` Paul Eggert
2022-11-26  3:20     ` [tz] " Russ Allbery
2022-11-26  3:50       ` Paul Eggert
2022-11-26 20:44         ` G. Branden Robinson
2022-11-26  3:52     ` G. Branden Robinson
2022-11-26 12:33       ` Deri
2022-11-26 21:01       ` Paul Eggert
2022-11-26 21:56         ` G. Branden Robinson
2022-11-27  1:58           ` Deri
2022-11-27  2:32           ` Paul Eggert
2022-12-13 19:24             ` G. Branden Robinson
2022-12-25 22:07               ` Lennart Jablonka
2022-12-25 23:21                 ` G. Branden Robinson
2022-11-26 21:20       ` Steffen Nurpmeso
2022-11-26 22:07         ` G. Branden Robinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=842adff8-8d8c-b189-8e6c-34be111b8b19@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=tz@iana.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox