[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[AUCTeX-devel] Process filter and coding system (was: [AUCTeX] Re: debug
From: |
Ralf Angeli |
Subject: |
[AUCTeX-devel] Process filter and coding system (was: [AUCTeX] Re: debugging of multifile documents with TeX-next-error (2)) |
Date: |
Sat, 07 Jul 2007 17:27:42 +0200 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (gnu/linux) |
* David Kastrup (2007-07-05) writes:
> Ralf Angeli <address@hidden> writes:
>
>> * David Kastrup (2007-07-03) writes:
>>
>>> Ralf Angeli <address@hidden> writes:
>>>
>>>> Hm, but pasting together random stuff will not be trivial.
>>>
>>> Would be the job of the filter routine.
>>
>>> Given TeX's byte-centricity,
>>> it would have to be done even before decoding the byte stream into
>>> characters.
>>
>> Is the string passed to the filter function still a byte stream?
>
> set-process-coding-system is a built-in function in `src/process.c'.
> (set-process-coding-system PROCESS &optional DECODING ENCODING)
>
> Set coding systems of PROCESS to DECODING and ENCODING.
> DECODING will be used to decode subprocess output and ENCODING to
> encode subprocess input.
>
> [back]
>
> Setting DECODING to no-conversion will give byte streams to the filter
> function. There is the problem of how to deal with incomplete
> characters in this case.
How would the output finally be decoded? By calling
`detect-coding-region' and then `decode-coding-region' on the whole
output buffer after process exit?
Followup-To: auctex-devel
--
Ralf
- [AUCTeX-devel] Process filter and coding system (was: [AUCTeX] Re: debugging of multifile documents with TeX-next-error (2)),
Ralf Angeli <=