From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: larsi@gnus.org, 12925@debbugs.gnu.org, ethan.glasser.camp@gmail.com
Subject: bug#12925: 24.1; string-make-unibyte instead of string-as-unibyte
Date: Tue, 01 Jun 2021 18:26:33 +0300 [thread overview]
Message-ID: <83v96xzjva.fsf@gnu.org> (raw)
In-Reply-To: <jwvpmx5ll8a.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 01 Jun 2021 10:25:17 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: larsi@gnus.org, 12925@debbugs.gnu.org, ethan.glasser.camp@gmail.com
> Date: Tue, 01 Jun 2021 10:25:17 -0400
>
> > What I mean is: if we think the current behavior is broken, then what
> > I suggest is at least less broken (and sometimes might just be TRT).
>
> I doubt it's less broken: sometimes it will be TRT, other times it will
> be worse than what we have.
>
> > At the very least what I suggest is reversible, whereas neither the
> > current behavior nor what you suggest is.
>
> My point is that we shouldn't even get into the position of having to
> make such arbitrary choices: we should signal an error before we
> get there.
Well, then we still disagree.
next prev parent reply other threads:[~2021-06-01 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 17:45 bug#12925: 24.1; string-make-unibyte instead of string-as-unibyte Ethan Glasser-Camp
2012-11-19 2:27 ` Stefan Monnier
2021-06-01 7:02 ` Lars Ingebrigtsen
2021-06-01 11:56 ` Eli Zaretskii
2021-06-01 13:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-01 14:03 ` Eli Zaretskii
2021-06-01 14:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-01 15:26 ` Eli Zaretskii [this message]
2021-06-02 5:07 ` Lars Ingebrigtsen
2021-06-02 12:07 ` Eli Zaretskii
2021-06-02 13:09 ` Lars Ingebrigtsen
2021-06-02 13:36 ` 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=83v96xzjva.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12925@debbugs.gnu.org \
--cc=ethan.glasser.camp@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.