[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23750: 25.0.95; bug in url-retrieve or json.el
From: |
Eli Zaretskii |
Subject: |
bug#23750: 25.0.95; bug in url-retrieve or json.el |
Date: |
Tue, 21 Jun 2016 05:30:04 +0300 |
> Cc: 23750@debbugs.gnu.org, monnier@IRO.UMontreal.CA, sdl.web@gmail.com
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 20 Jun 2016 23:27:01 +0300
>
> On 06/20/2016 11:17 PM, Eli Zaretskii wrote:
>
> > We can replace the call to multibyte-string-p with a comparison of
> > what 'length' and 'string-bytes' return. That should overcome this
> > issue.
>
> Why not just call string-to-unibyte?
Because (a) I don't want to see that function in our sources, ever,
and (b) you don't have any control on the error message it produces,
which is not appropriate for application-level checks.
- bug#23750: 25.0.95; bug in url-retrieve or json.el, (continued)
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Eli Zaretskii, 2016/06/19
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Dmitry Gutov, 2016/06/19
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Eli Zaretskii, 2016/06/20
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Dmitry Gutov, 2016/06/20
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Eli Zaretskii, 2016/06/20
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Dmitry Gutov, 2016/06/20
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Eli Zaretskii, 2016/06/20
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Dmitry Gutov, 2016/06/20
- bug#23750: 25.0.95; bug in url-retrieve or json.el,
Eli Zaretskii <=
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Dmitry Gutov, 2016/06/21
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Eli Zaretskii, 2016/06/21
- bug#23750: 25.0.95; bug in url-retrieve or json.el, John Wiegley, 2016/06/21
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Eli Zaretskii, 2016/06/21
- bug#23750: 25.0.95; bug in url-retrieve or json.el, Dmitry Gutov, 2016/06/22