From: Noam Postavsky <npostavs@gmail.com>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: 31376@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#31376: 26.0.50; print-charset-text-property not honored
Date: Mon, 07 May 2018 08:57:13 -0400 [thread overview]
Message-ID: <87603zmxna.fsf@gmail.com> (raw)
In-Reply-To: <m27eofq2ra.fsf@gmail.com> (Helmut Eller's message of "Mon, 07 May 2018 10:38:33 +0200")
Helmut Eller <eller.helmut@gmail.com> writes:
> On Mon, May 07 2018, Andreas Schwab wrote:
>
>>> In GNU Emacs 26.0.50 (build 10, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
>>> of 2017-08-15 built on caladan
>>
>> Worksforme. Have you tried a current version?
>
> Same (wrong) result with the current version. Maybe it's an issue with
> environment settings?
I can reproduce this. I see something about
PRINT_STRING_UNSAFE_CHARSET_FOUND in print.c, so I guess iso-8859-1 is
considered "unsafe"?
next prev parent reply other threads:[~2018-05-07 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 6:48 bug#31376: 26.0.50; print-charset-text-property not honored Helmut Eller
2018-05-07 7:58 ` Andreas Schwab
2018-05-07 8:38 ` Helmut Eller
2018-05-07 12:57 ` Noam Postavsky [this message]
2018-05-07 18:08 ` Helmut Eller
2018-05-11 13:31 ` Eli Zaretskii
2018-05-11 17:44 ` Noam Postavsky
2018-05-11 18:45 ` Eli Zaretskii
2018-05-12 20:02 ` Noam Postavsky
2018-05-13 15:29 ` Eli Zaretskii
2018-05-13 18:29 ` Noam Postavsky
2018-05-13 18:51 ` Eli Zaretskii
2018-05-13 19:42 ` Noam Postavsky
2018-05-14 16:34 ` Eli Zaretskii
2018-05-14 23:15 ` Noam Postavsky
2018-05-15 17:19 ` Eli Zaretskii
2018-05-15 23:37 ` Noam Postavsky
2018-05-23 23:12 ` Noam Postavsky
[not found] ` <<837eoani9b.fsf@gnu.org>
2018-05-11 19:58 ` Drew Adams
2018-05-12 6:10 ` Eli Zaretskii
[not found] <<m2zi1c6jvo.fsf@caladan>
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=87603zmxna.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31376@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=schwab@linux-m68k.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).