GNU bug report logs - #75345
29.4; 'insert' doc string still mentions 'string-as-multibyte'

Previous Next

Full log

Message #10 received at 75345-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ulrich Müller <ulm <at> gentoo.org>
Cc: 75345-done <at> debbugs.gnu.org
Subject: Re: bug#75345: 29.4;
 'insert' doc string still mentions 'string-as-multibyte'
Date: Sat, 04 Jan 2025 15:32:59 +0200

> From: Ulrich Müller <ulm <at> gentoo.org>
> Date: Sat, 04 Jan 2025 10:50:04 +0100
> 
> C-h f insert RET
> 
>    insert is a built-in function in ‘src/editfns.c’.
> 
>    [...]
> 
>    When operating on binary data, it may be necessary to preserve the
>    original bytes of a unibyte string when inserting it into a multibyte
>    buffer; to accomplish this, apply ‘string-as-multibyte’ to the string
>    and insert the result.
> 
> C-h f string-as-multibyte RET
> 
>    string-as-multibyte is a built-in function in ‘src/fns.c’.
> 
>    This function is obsolete since 26.1; use `decode-coding-string'.
> 
>    [...]
> 
> This looks inconsistent, presumably 'insert' shouldn't mention
> 'string-as-multibyte'. Attached patch updates the doc string.

Thanks, installed on emacs-30, and closing the bug.

> Also, the elisp manual still mentions functions string-as-unibyte and
> string-as-multibyte in section "(elisp) Top > Non-ASCII Characters >
> Selecting a Representation". Should these be removed from the manual,
> or at least be labelled as obsolete?

I'm not yet convinced these functions should be removed from the
manual.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.