unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
	lg.zevlg@gmail.com, 34873@debbugs.gnu.org
Subject: bug#34873: 27.0.50; Creating unibyte string in emacs modules
Date: Thu, 27 Aug 2020 13:13:36 -0400	[thread overview]
Message-ID: <CAM-tV-98ja5Vn+Hxqqn-+wQHERPePqJoLEiUWF57HkJCcZtjpQ@mail.gmail.com> (raw)
In-Reply-To: <83r1rs10yd.fsf@gnu.org>

On Thu, 27 Aug 2020 at 12:57, Eli Zaretskii <eliz@gnu.org> wrote:

> > Does that mean that you think binary data should be stored only in vectors?
>
> Why would it mean that, I wonder?

You said binary data is not the use case for unibyte strings and
pointed to bindat.el instead. bindat.el uses unibyte strings or
vectors for binary data.

(NOT unibyte strings) AND (unibyte strings OR vectors) => vectors





  reply	other threads:[~2020-08-27 17:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 20:52 bug#34873: 27.0.50; Creating unibyte string in emacs modules Evgeny Zajcev
2019-03-16  7:30 ` Eli Zaretskii
2019-03-16 10:32   ` lg.zevlg
2019-03-16 12:20     ` Eli Zaretskii
2019-03-16 15:28       ` lg.zevlg
2019-03-16 16:17         ` Eli Zaretskii
2019-05-07 16:55           ` Basil L. Contovounesios
2019-05-07 18:33             ` Eli Zaretskii
2019-05-07 19:24               ` Basil L. Contovounesios
2019-05-07 19:48                 ` Eli Zaretskii
2020-08-26 10:43           ` Lars Ingebrigtsen
2020-08-26 10:52             ` Eli Zaretskii
2020-08-27 13:04               ` Lars Ingebrigtsen
2020-08-27 13:40                 ` Eli Zaretskii
2020-08-27 14:33                   ` Noam Postavsky
2020-08-27 16:57                     ` Eli Zaretskii
2020-08-27 17:13                       ` Noam Postavsky [this message]
2020-08-27 17:18                         ` Eli Zaretskii
2020-10-13  4:52 ` Lars Ingebrigtsen
2020-10-13 14:31   ` Philipp Stephani
2020-10-14  3:59     ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM-tV-98ja5Vn+Hxqqn-+wQHERPePqJoLEiUWF57HkJCcZtjpQ@mail.gmail.com \
    --to=npostavs@gmail.com \
    --cc=34873@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=lg.zevlg@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).