bug#122: 23.0.60; Slowdown in directory scanning over time.

[Kenichi Handa]

In article <E1KfIlu-00027F-0p@fencepost.gnu.org>, "Richard M. Stallman" 
<rms@gnu.org> writes:

>     (1) A coding system can have pre-write-conversion function,
>     and that function can call code-conversion function
>     recursively.

> I read in the doc string of define-coding-system
> that the pre-write-conversion function is called
> before doing the ordinary work of encoding.

> Is it possible to call the pre-write-conversion function
> before obtaining the work buffer?

No.  If the source of encoding is a string, it is inserted
in a working buffer to allow pre-write-conversion function
to modify it.

>     (2) If REPLACE arg is non-nil in insert-file-contents and a
>     file need a decoding, we call decode_coding_c_string while a
>     work buffer is in use.

> I see why decoding is needed in this case, but why is a work
> buffer already in use?  It seems to me that there is only one
> act of decoding to be done in that call to insert-file-contents.

insert-file-contents uses the working buffer to hold the
output of decoding.  So, when decode_coding_c_string is
called, we have already called code_conversion_save to make
the working buffer.

---
Kenichi Handa
handa@ni.aist.go.jp