all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 29 Dec 2017 16:35:50 -0800 (PST)	[thread overview]
Message-ID: <e0f4da49-27e1-4f58-99d6-377d6c1882e6@default> (raw)
In-Reply-To: <83mv21fjpb.fsf@gnu.org>

> > I do `M-x shell' and see this in buffer `*shell*':
> >
> >  bash: cannot set terminal process group (-1): Inappropriate ioctl for
> >  device bash: no job control in this shell
> >
> > (Perhaps you have an idea about that?  If not, OK.)
> >
> > But doing what you said anyway (`man find > foo'), the output
> > is correct; the "hyphens" are actually hyphens:
> >
> >   name: HYPHEN
> >   general-category: Pd (Punctuation, Dash)
> >   decomposition: (8208) ('‐')
> 
> Then I think you will have to set up process-coding-system-alist such
> that it reads output from 'man' with utf-8 decoding.  I don't know
> what changed since Emacs 25, but if 'man' produces UTF-8 encoded
> hyphens by default, Emacs needs to be told about that.

I have no idea in what way to change
`process-coding-system-alist'.  The doc string and
(elisp) `Default Coding System' give me no hint that
I can recognize.

I don't even know whether it is the VAL (which is
`(raw-text-dos . raw-text-unix)') that is incorrect
or it is the PATTERN (which is "bash") that is
incorrect, or both.

And it is not even a user option.

_Someone_ should be able to tell "what changed
since Emacs 25", hopefully.  This is a (presumaby
incompatible) change in Emacs, not something a user
has provoked, AFAICS.

Suddenly something that (still) works in all prior
Emacs releases (as far back as Emacs 20, at least)
no longer works.





  reply	other threads:[~2017-12-30  0:35 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
2017-12-29 17:21       ` Drew Adams
2017-12-29 18:54         ` Eli Zaretskii
2017-12-30  0:35           ` Drew Adams [this message]
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=e0f4da49-27e1-4f58-99d6-377d6c1882e6@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 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.