From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 29872@debbugs.gnu.org
Subject: bug#29872: 26.0.90; `man' output encoding, hyphen chars
Date: Fri, 29 Dec 2017 11:48:55 +0200 [thread overview]
Message-ID: <83shbtg8zc.fsf@gnu.org> (raw)
In-Reply-To: <5a25751a-3a68-4e44-862f-44fa47871c04@default> (message from Drew Adams on Thu, 28 Dec 2017 15:52:30 -0800 (PST))
> Date: Thu, 28 Dec 2017 15:52:30 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 29872@debbugs.gnu.org
>
> In Emacs 25.3.1 and prior I see a hyphen character
> instead. I thought that was clear.
It wasn't clear because you never said that explicitly, and because
"hyphen" is ambiguous in this context: it could refer to ASCII '-'
character or to non-ASCII '' or to non-ASCII '‐'. They are all
different characters, and potentially hint on different problems.
> This manual page documents the GNU version of find. GNU find searches
> the directory tree rooted at each given file name by evaluating the
> given expression from left to right, according to the rules of prece-
> dence (see section OPERATORS), until the outcome is known (the left
>
> `C-u C-x =' before that hyphen says this:
>
> name: HYPHEN-MINUS
> general-category: Pd (Punctuation, Dash)
> decomposition: (45) ('-')
>
> (BTW, I showed only that one hyphen occurrence, but all of
> the "hyphens" show the same problem in Emacs 26 and later.)
OK. If you manually load man.el from Emacs 25, does the problem go
away?
Also, if you invoke the 'man' command from the Bash shell and redirect
its output to a file, what characters/bytes do you see in place of
those hyphens in the file created by that command?
next prev parent reply other threads:[~2017-12-29 9:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 1:59 bug#29872: 26.0.90; `man' output encoding, hyphen chars Drew Adams
2017-12-28 3:34 ` Eli Zaretskii
2017-12-28 23:52 ` Drew Adams
2017-12-29 9:48 ` Eli Zaretskii [this message]
2017-12-29 17:21 ` Drew Adams
2017-12-29 18:54 ` Eli Zaretskii
2017-12-30 0:35 ` Drew Adams
2017-12-30 0:39 ` Drew Adams
2017-12-30 8:15 ` Eli Zaretskii
2017-12-30 17:03 ` Drew Adams
2017-12-30 18:22 ` Eli Zaretskii
2017-12-30 8:13 ` Eli Zaretskii
2019-09-28 23:26 ` Stefan Kangas
[not found] <<2dfed463-2ddb-4591-a476-c78e0b8d445b@default>
[not found] ` <<838tdnh6ej.fsf@gnu.org>
[not found] ` <<5a25751a-3a68-4e44-862f-44fa47871c04@default>
[not found] ` <<83shbtg8zc.fsf@gnu.org>
[not found] ` <<b25fb680-3f64-49ec-a894-899cf3213b07@default>
[not found] ` <<83mv21fjpb.fsf@gnu.org>
[not found] ` <<e0f4da49-27e1-4f58-99d6-377d6c1882e6@default>
[not found] ` <<83d12wfxb5.fsf@gnu.org>
2017-12-30 17:03 ` Drew Adams
2017-12-30 18:20 ` Eli Zaretskii
2017-12-30 18:28 ` Eli Zaretskii
2017-12-30 23:11 ` Drew Adams
2017-12-31 16:24 ` Eli Zaretskii
2017-12-31 17:34 ` Drew Adams
2017-12-31 18:53 ` Eli Zaretskii
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=83shbtg8zc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29872@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.