From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29872@debbugs.gnu.org
Subject: bug#29872: 26.0.90; `man' output encoding, hyphen chars
Date: Sun, 31 Dec 2017 09:34:42 -0800 (PST) [thread overview]
Message-ID: <f0c022ca-3055-4cce-b464-eac69dcc8f61@default> (raw)
In-Reply-To: <83bmieeuhm.fsf@gnu.org>
> > > What about the below, does that work?
> > > (let ((locale-coding-system 'utf-8))
> > > (man "find"))
> >
> > Yes! With `emacs -Q', loading the two files mentioned,
> > and then evaluating that sexp, the `man' output is correct:
> > hyphens appear as they should - that is:
> >
> > name: HYPHEN
> > general-category: Pd (Punctuation, Dash)
> > decomposition: (8208) ('‐')
> >
> > What should I then change in, say, `setup-cygwin.el',
> > to make that happen? (Or does something need to be
> > changed in Emacs itself?)
>
> For Emacs 26, I've just committed a change that introduces a new
> defcustom, Man-coding-system, which you can customize to utf-8 to get
> the correct behavior in your case. For older versions of Emacs, you
> will need to use a separate command that invokes 'man' as shown above,
> because man.el unconditionally uses locale-coding-system for that, and
> locale-coding-system on MS-Windows can never be UTF-8.
Thank you. I assume that you'll mention this in NEWS.
I wonder whether it is something that I should set in
`setup-cygwin.el' or just tell users there, in a comment,
that they will need to customize it.
Leavning aside, for the moments, arguments about whether
code should mess with user options, can you say when it
is appropriate, typically, for a Windows user to customize
that option? Does it have to do with whether Cygwin is
used, for instance (with a non-Cygwin Emacs)? Or does
the option default value depend on the platform perhaps?
next prev parent reply other threads:[~2017-12-31 17:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` bug#29872: 26.0.90; `man' output encoding, hyphen chars 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 [this message]
2017-12-31 18:53 ` Eli Zaretskii
2017-12-28 1:59 Drew Adams
2017-12-28 3:34 ` Eli Zaretskii
2017-12-28 23:52 ` Drew Adams
2017-12-29 9:48 ` Eli Zaretskii
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f0c022ca-3055-4cce-b464-eac69dcc8f61@default \
--to=drew.adams@oracle.com \
--cc=29872@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).