all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: master b8062be 3/5: Remove some compat code from eudc-bob.el
Date: Tue, 18 Aug 2020 13:02:47 -0400	[thread overview]
Message-ID: <jwvh7sz6gg0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ft8kj93z.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 18 Aug 2020 16:56:32 +0200")

> Right...  but these days, we don't use Unibyte buffers for text at all?

That's right.

> So is this still baggage that we have to carry around?

I'm pretty sure it's not necessary.
But I don't have a clear idea of how much breakage it would involve:
someone should try it out and see what breaks in the packages they use to
get a feel for how serious it is.

> Hm...  I guess if we have a unibyte ASCII buffer, somebody might still
> want to do EOL conversions...

I get the impression that the more problematic case will be process
filters: I think it is fairly rare to have ASCII text (really meant as
*text* where we want EOL conversion) in a unibyte buffer, but I think
it's pretty frequent to have ASCII *text* inside unibyte strings.
The difference is that the unibyteness of strings is determined
semi-automatically.

So we could end up with a half-way rule where coding-systems (i.e. EOL
conversion) doesn't apply to text coming from or going to a unibyte
buffer, but does apply to unibyte strings :-(


        Stefan




  parent reply	other threads:[~2020-08-18 17:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200812175454.4839.92908@vcs0.savannah.gnu.org>
     [not found] ` <20200812175456.C5D122172E@vcs0.savannah.gnu.org>
2020-08-12 17:56   ` master b8062be 3/5: Remove some compat code from eudc-bob.el Lars Ingebrigtsen
2020-08-12 18:15     ` Stefan Monnier
2020-08-13  8:08       ` Lars Ingebrigtsen
2020-08-13 13:14         ` Eli Zaretskii
2020-08-13 13:58           ` Stefan Monnier
2020-08-13 14:14             ` Eli Zaretskii
2020-08-13 14:23               ` Stefan Monnier
2020-08-13 16:43                 ` Eli Zaretskii
2020-08-13 17:43                   ` Stefan Monnier
2020-08-13 18:25                     ` Eli Zaretskii
2020-08-13 19:02                       ` Stefan Monnier
2020-08-13 19:06                         ` Eli Zaretskii
2020-08-13 19:54                           ` Stefan Monnier
2020-08-14  6:05                             ` Eli Zaretskii
2020-08-14  9:54                               ` Lars Ingebrigtsen
2020-08-14 10:35                                 ` Eli Zaretskii
2020-08-14 11:03                                   ` Eli Zaretskii
2020-08-15  9:53                                     ` Lars Ingebrigtsen
2020-08-15 12:56                                       ` Stefan Monnier
2020-08-15 15:10                                       ` Eli Zaretskii
2020-08-16 11:17                                         ` Lars Ingebrigtsen
2020-08-16 14:41                                           ` Eli Zaretskii
2020-08-17  8:32                                             ` Lars Ingebrigtsen
2020-08-17 13:15                                               ` Stefan Monnier
2020-08-18 14:56                                                 ` Lars Ingebrigtsen
2020-08-18 15:08                                                   ` Eli Zaretskii
2020-08-18 17:02                                                   ` Stefan Monnier [this message]
2020-08-19 10:20                                                     ` Lars Ingebrigtsen
2020-08-17 14:17                                               ` Eli Zaretskii
2020-08-13 13:33         ` Stefan Monnier
2020-08-15 21:19         ` Stefan Monnier
2020-08-15 21:27           ` Stefan Monnier

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=jwvh7sz6gg0.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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 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.