[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24206: 25.1; Curly quotes generate invalid strings, leading to a seg
From: |
Eli Zaretskii |
Subject: |
bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault |
Date: |
Mon, 15 Aug 2016 22:04:18 +0300 |
> Cc: p.stephani2@gmail.com, johnw@gnu.org, nicolas@petton.fr,
> 24206@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 15 Aug 2016 11:43:16 -0700
>
> Yes. This is in the Elisp manual, which says "We recommend that
> you never use unibyte buffers and strings except for manipulating
> encoded text or binary non-text data."
That advice is for Lisp programmers, so it's only tangentially
relevant in this case.
> Eli Zaretskii wrote:
> > as the original string is
> > unibyte, the output of "\200≠", which is multibyte, might not be what
> > the users expect. They might expect "\200\342\211\240" instead.
>
> No, as per Andreas's comment and the Elisp reference manual, users should not
> expect substitute-command-keys to do that.
We still want them to be as little surprised as possible, do we?
> As long as it doesn't crash on non-ASCII unibyte data we needn't
> sweat the details about whether it returns unibyte or multibyte
> strings for such data.
I explained why this cannot be 100% true. So I'd like to avoid
converting unibyte strings to multibyte as much as reasonably
possible.
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, (continued)
bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Paul Eggert, 2016/08/14
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Eli Zaretskii, 2016/08/14
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Paul Eggert, 2016/08/14
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Eli Zaretskii, 2016/08/14
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Paul Eggert, 2016/08/14
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Eli Zaretskii, 2016/08/15
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Andreas Schwab, 2016/08/15
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Paul Eggert, 2016/08/15
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault,
Eli Zaretskii <=
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Eli Zaretskii, 2016/08/15
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, John Wiegley, 2016/08/15
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Paul Eggert, 2016/08/15
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Eli Zaretskii, 2016/08/16
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, John Wiegley, 2016/08/16
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Nicolas Petton, 2016/08/16
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Nicolas Petton, 2016/08/18
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, John Wiegley, 2016/08/18
- bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Eli Zaretskii, 2016/08/18
bug#24206: 25.1; Curly quotes generate invalid strings, leading to a segfault, Paul Eggert, 2016/08/16