[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#26796: 26.0.50; (2 characters) is usually wrong
From: |
Eli Zaretskii |
Subject: |
bug#26796: 26.0.50; (2 characters) is usually wrong |
Date: |
Sat, 06 May 2017 14:06:37 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 26796@debbugs.gnu.org
> Date: Sat, 06 May 2017 12:45:45 +0200
>
> But this is questionable, at least:
>
> (with-temp-buffer (set-buffer-multibyte nil) (insert-file-contents
> "~/rms.jpg") (write-region (point-min) (point-max) "/tmp/a.jpg"))
> Wrote ‘/tmp/a.jpg’ (889 characters)
>
> There are no characters in a JPEG file; it's all bytes.
Each byte is a character in this case, right?
Anyway, since you don't like this feature, it's clear that you can
come up with many examples where you don't like the result. People
who do like it will most probably disagree.
- bug#26796: 26.0.50; (2 characters) is usually wrong, Lars Ingebrigtsen, 2017/05/06
- bug#26796: 26.0.50; (2 characters) is usually wrong, Eli Zaretskii, 2017/05/06
- bug#26796: 26.0.50; (2 characters) is usually wrong, npostavs, 2017/05/06
- bug#26796: 26.0.50; (2 characters) is usually wrong, Eli Zaretskii, 2017/05/06
- bug#26796: 26.0.50; (2 characters) is usually wrong, npostavs, 2017/05/06
- bug#26796: 26.0.50; (2 characters) is usually wrong, Mark Oteiza, 2017/05/08
- bug#26796: 26.0.50; (2 characters) is usually wrong, Eli Zaretskii, 2017/05/08
- bug#26796: 26.0.50; (2 characters) is usually wrong, Glenn Morris, 2017/05/08
- bug#26796: 26.0.50; (2 characters) is usually wrong, Eli Zaretskii, 2017/05/08
- bug#26796: 26.0.50; (2 characters) is usually wrong, Mark Oteiza, 2017/05/08
- bug#26796: 26.0.50; (2 characters) is usually wrong, npostavs, 2017/05/09
bug#26796: 26.0.50; (2 characters) is usually wrong, Paul Eggert, 2017/05/06