all messages for Emacs-related lists mirrored at yhetil.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: Sat, 30 Dec 2017 10:15:13 +0200	[thread overview]
Message-ID: <83bmigfx7y.fsf@gnu.org> (raw)
In-Reply-To: <8e3728bd-a5d4-448d-b1f0-861fd7450f71@default> (message from Drew Adams on Fri, 29 Dec 2017 16:39:51 -0800 (PST))

> Date: Fri, 29 Dec 2017 16:39:51 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 29872@debbugs.gnu.org
> 
> > Suddenly something that (still) works in all prior
> > Emacs releases (as far back as Emacs 20, at least)
> > no longer works.
> 
> Sorry, my bad.  At least as far back as Emacs 22.
> Emacs 20 shows the same problem.  There the output
> shows this, where the end of the line is displayed
> as `\342\200\220'.
> 
>  given  expression  from left to right, according to the rules of prece‐

Thanks, this is good to know, but then how did you obtain the text
with an ASCII hyphen that you said earlier you saw in older versions
of Emacs?

In any case, the above means the decoding of the stuff produced by
the Cygwin 'man' you have installed was incorrect since long ago.





  reply	other threads:[~2017-12-30  8:15 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
2017-12-30  0:39             ` Drew Adams
2017-12-30  8:15               ` Eli Zaretskii [this message]
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=83bmigfx7y.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.