emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs-26 8f18d12: Improve documentation of decoding into a unibyte b


From: Robert Pluim
Subject: Re: emacs-26 8f18d12: Improve documentation of decoding into a unibyte buffer
Date: Mon, 27 May 2019 11:47:35 +0200

>>>>> On Sat, 25 May 2019 15:10:40 -0400 (EDT), address@hidden (Eli Zaretskii) 
>>>>> said:

    Eli> branch: emacs-26
    Eli> commit 8f18d121210aa27dc05555140ab21a8489f0de50
    Eli> Author: Eli Zaretskii <address@hidden>
    Eli> Commit: Eli Zaretskii <address@hidden>

    Eli>     Improve documentation of decoding into a unibyte buffer
    
    Eli>     * doc/lispref/nonascii.texi (Explicit Encoding): Document what
    Eli>     happens when DESTINATION of decoding is a unibyte buffer.
    
    Eli>     * src/coding.c (Fdecode_coding_region)
    Eli>     (Fdecode_coding_string): Document what happens if DESTINATION
    Eli>     is a unibyte buffer.

A related issue: C-h f string-as-unibyte

    string-as-unibyte is a built-in function in `src/fns.c'.

    (string-as-unibyte STRING)

      This function is obsolete since 26.1;
      use `encode-coding-string'.
      Probably introduced at or before Emacs version 20.3.
      This function does not change global state, including the match data.

Having trawled through the elisp manual, for the life of me itʼs not
clear which coding system I should use. 'raw-text'? 'us-ascii'?
Something Else?

Robert



reply via email to

[Prev in Thread] Current Thread [Next in Thread]