MSGID: 2:221/1.58@fidonet 288d7068
REPLY: 2:280/464.113 696c5b86
PID: OpenXP/5.0.64 (Win32)
CHRS: ASCII 1
TZUTC: -0500
Hello Maurice Kinal!

** On Sunday 18.01.26 - 04:03, Maurice Kinal wrote to Aug:

 >> No..  I want to parse stderr that gpg produces.

 MK> Then you're on the right track except I would suggest changing NUL to
 MK> something else, say OUT and BOTH.

NUL and NUL2, (or NULx) are clearer indications for me that they are  
disposable files and just useful for the current process.  I don't care if  
they are overwritten or deleted later.

I've updated my script/commandline to always produce those NULx files in  
h:\temp dir.  I don't care to backup anything that I place in h:\temp

I wouldn't mind creating my own "temp" dir in ram, but Windows limits that to  
the system TEMP and TMP.  And.. that could probably interfere with program  
updates that require restarts causing legit files stored there to vanish at  
reboot.

I'm reading that creating a ramdisk in linux is fairly simple and a common  
feature.

Back on topic for this thread.. this is the linux version (via busybox for  
me) that works as desired:

H:\temp>busybox sh
H:/temp $ gpg --batch --yes -d ppp.txt >| NUL 2>| NUL2 ; grep \" NUL2
      "seanrima-gpgmail "
      "Philipe "
      "Phil Lejman "
      "Paul Kapaldo"



-- 
  ../|ug

--- OpenXP 5.0.64
 * Origin: Got Mobile? This echo = https://t.me/+RLI5gLJrHo6IIuzL (2:221/1.58)
SEEN-BY: 50/22 103/705 105/81 106/201 124/5016 128/187 129/14 153/757
SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/1 6 226/30 227/114
SEEN-BY: 229/110 112 134 206 300 317 400 426 428 470 664 700 705 240/1120
SEEN-BY: 240/5832 263/1 266/512 280/464 5003 291/111 292/8125 301/1
SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 423/81 460/58
SEEN-BY: 460/256 1124 5858 633/280 712/848 770/1 902/26 5020/400 8912
SEEN-BY: 5054/30 5075/35
PATH: 221/1 280/464 460/58 229/426