unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: lg.zevlg@gmail.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34873@debbugs.gnu.org
Subject: bug#34873: 27.0.50; Creating unibyte string in emacs modules
Date: Sat, 16 Mar 2019 11:32:47 +0100	[thread overview]
Message-ID: <88B2D883-45AD-4432-9FE1-D4E24709E294@gmail.com> (raw)
In-Reply-To: <83ef77z371.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

16 марта 2019 г., в 8:30, Eli Zaretskii <eliz@gnu.org> написал(а):

>> From: Evgeny Zajcev <lg.zevlg@gmail.com>
>> Date: Fri, 15 Mar 2019 23:52:17 +0300
>> 
>> There is no possibility to create unibyte strings from emacs modules in order to create some binary data
>> representation
>> 
>> The only solution for now is to call `make_string` method and then apply `encode-coding-string' with utf-8
>> encoding to the result.  But on large data this became very slow
>> 
>> I used this patch to bypass the conversion steps and it works pretty nice
>> 
>> Ideally I would like to use user-ptr objects as `:data' in image specification, but solution with `make_data'
>> module method will be suitable enough
> 
> Please explain why you need to create a unibyte string for that.  I
> guess what's missing is more details regarding what you are trying to
> do (the single sentence above about :data wasn't enough for me), and
> how is your module involved in that, in particular why do you need a
> module to display an image in Emacs.

See this thread https://lists.gnu.org/archive/html/emacs-devel/2019-03/msg00465.html

I need this module, because all existing packages to manipulate images are not capable enough for me

—
lg


[-- Attachment #2: Type: text/html, Size: 2895 bytes --]

  reply	other threads:[~2019-03-16 10:32 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 [this message]
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
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=88B2D883-45AD-4432-9FE1-D4E24709E294@gmail.com \
    --to=lg.zevlg@gmail.com \
    --cc=34873@debbugs.gnu.org \
    --cc=eliz@gnu.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 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).