unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 31 Dec 2017 20:53:13 +0200	[thread overview]
Message-ID: <83zi5yd90m.fsf@gnu.org> (raw)
In-Reply-To: <f0c022ca-3055-4cce-b464-eac69dcc8f61@default> (message from Drew Adams on Sun, 31 Dec 2017 09:34:42 -0800 (PST))

> Date: Sun, 31 Dec 2017 09:34:42 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 29872@debbugs.gnu.org
> 
> > 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'm not sure it's NEWS worthy.  The situations in which this variable
is useful are quite obscure (see below) and since the code in its
present form exists for a long time without anyone complaining, we can
assume they are rare.  And mentioning this variable won't enhance its
discoverability, since no one will know to look it up when/if they
bump into this problem.

> 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.

Probably the latter.

> 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?

On Windows, probably only when using a Cygwin 'man' from a native
Windows Emacs.  On some other system, only if the man pages were
pre-formatted on another system with an incompatible locale setting,
or if Groff was forced to produce UTF-8 encoded man pages when those
man pages were formatted.

> 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?

On almost any platform with correct setup, the default of using
locale-coding-system for decoding the man pages should work correctly,
so the default should not depend on the platform.  This new variable
is a fire escape for those rare cases where the default doesn't work.





  reply	other threads:[~2017-12-31 18:53 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
2017-12-31 18:53                         ` Eli Zaretskii [this message]
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=83zi5yd90m.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 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).