### ImageMagick version

7.1.1-18

### Operating system

Windows

### Operating system, version and so on

10

### Description

The external program writes image data through a pipe to the STDIN of `magick.exe`, causing temporary file to be created on `C:/Users/<user>/AppData/Local/Temp/magick-xxxxxxxxxxxxxxxxxxxx`. Even when setting `MAGICK_TEMPORARY_PATH` to a nonexistent path, temp file are still created in the CWD.

### Steps to Reproduce

```
const magick = spawn('magick', [
  '-debug', 'Cache',
  '-',
  'avif:-',
], {env: {'MAGICK_DISK_LIMIT': 0, 'MAGICK_MAP_LIMIT': '128GB', 'MAGICK_AREA_LIMIT': '128GB', 'MAGICK_MEMORY_LIMIT': '128GB'}});
magick.stdin.write(fs.readFileSync('./image.jpg'));
magick.stdin.end();
magick.stderr.on('data', data => process.stderr.write(data));
```

### Images

_No response_
Image pipe to STDIN are always write disk cache even `MAGICK_DISK_LIMIT=0`
This is a GitHub Issue
repo:ImageMagick
owner:ImageMagick
Title : Image pipe to STDIN are always write disk cache even `MAGICK_DISK_LIMIT=0`
Issue date:

--- start body ---
### ImageMagick version

7.1.1-18

### Operating system

Windows

### Operating system, version and so on

10

### Description

The external program writes image data through a pipe to the STDIN of `magick.exe`, causing temporary file to be created on `C:/Users/<user>/AppData/Local/Temp/magick-xxxxxxxxxxxxxxxxxxxx`. Even when setting `MAGICK_TEMPORARY_PATH` to a nonexistent path, temp file are still created in the CWD.

### Steps to Reproduce

```
const magick = spawn('magick', [
  '-debug', 'Cache',
  '-',
  'avif:-',
], {env: {'MAGICK_DISK_LIMIT': 0, 'MAGICK_MAP_LIMIT': '128GB', 'MAGICK_AREA_LIMIT': '128GB', 'MAGICK_MEMORY_LIMIT': '128GB'}});
magick.stdin.write(fs.readFileSync('./image.jpg'));
magick.stdin.end();
magick.stderr.on('data', data => process.stderr.write(data));
```

### Images

_No response_
--- end body ---

The issue describes a behavior in ImageMagick where image data piped to STDIN results in temporary files being created on disk, despite the environment variable `MAGICK_DISK_LIMIT` being set to 0. This behavior may lead to unintended disk usage, but it does not constitute a security vulnerability as it does not expose sensitive data or allow for unauthorized access.