unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 34873@debbugs.gnu.org, lg.zevlg@gmail.com
Subject: bug#34873: 27.0.50; Creating unibyte string in emacs modules
Date: Tue, 07 May 2019 21:33:40 +0300	[thread overview]
Message-ID: <83tve6i06z.fsf@gnu.org> (raw)
In-Reply-To: <87o94e2ogz.fsf@tcd.ie> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Cc: <lg.zevlg@gmail.com>,  <34873@debbugs.gnu.org>
> Date: Tue, 07 May 2019 17:55:56 +0100
> 
> Sorry if this is a dumb question, but would the functions
> unibyte-string, string-to-unibyte, string-as-unibyte et al. be of any
> use here?

I'm not sure I follow: how can these functions help writing code in a
module?  A module cannot be written in Lisp, and you cannot call these
functions on a C string, only on a Lisp string.

What am I missing?





  reply	other threads:[~2019-05-07 18:33 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 [this message]
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=83tve6i06z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34873@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --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).