August Abolins wrote to All <=-
What's the best way to get the output of this:
H:\temp>gpg ppp.txt
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 4096-bit RSA key, ID 34C35AA4CB59468A, created 2024-12-24
"seanrima-gpgmail <thecivvie@gmail.com>"
gpg: encrypted with ECDH key, ID FB7964717AABB346
gpg: encrypted with 256-bit ECDH key, ID DB93C9CDECB10521, created 2025-06-04
"Philipe <philipe_rm1@hotmail.com>"
gpg: encrypted with 2048-bit RSA key, ID 6C0F8C1358D82C2D, created 2010-10-18
"Phil Lejman <phil.lejman@gmail.com>"
gpg: encrypted with ECDH key, ID 740397B0612F2FC7
gpg: encrypted with 256-bit ECDH key, ID C42D963F2DAC8CC7, created 2020-10-17
"Paul Kapaldo"
..to just produce this:
"seanrima-gpgmail <thecivvie@gmail.com>"
"Philipe <philipe_rm1@hotmail.com>"
"Phil Lejman <phil.lejman@gmail.com>"
"Paul Kapaldo"
???
I'd use: gpg ppp.txt | grep '"'
On Linux, at least. Now that I look again, it looks like you're using Windoze, so not sure how to do it there.
I'd use: gpg ppp.txt | grep '"'
On Linux, at least. Now that I look again, it looks like
you're using Windoze, so not sure how to do it there.
If busybox is a good emulation of linux, this did not work:
H:\temp>busybox sh
H:/temp $ gpg ppp.txt | grep ""
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 4096-bit RSA key, ID 34C35AA4CB59468A, created 2024-12-24 "seanrima-gpgmail <thecivvie@gmail.com>"
gpg: encrypted with ECDH key, ID FB7964717AABB346
gpg: encrypted with 256-bit ECDH key, ID DB93C9CDECB10521, created 2025-06-04 "Philipe <philipe_rm1@hotmail.com>"
I'd use: gpg ppp.txt | grep '"'
On Linux, at least. Now that I look again, it looks like
you're using Windoze, so not sure how to do it there.
Sorry, I missed the " enclosed in ' quotes; however, same
result:
H:\temp>busybox sh
H:/temp $ gpg ppp.txt | grep '"'
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 4096-bit RSA key, ID 34C35AA4CB59468A, created 2024-12-24 "seanrima-gpgmail <thecivvie@gmail.com>"
gpg: encrypted with ECDH key, ID FB7964717AABB346
gpg: encrypted with 256-bit ECDH key, ID DB93C9CDECB10521, created 2025-06-04 "Philipe <philipe_rm1@hotmail.com>"
August Abolins wrote to Dan Clough <=-
I'd use: gpg ppp.txt | grep '"'
On Linux, at least. Now that I look again, it looks like
you're using Windoze, so not sure how to do it there.
Update BELOW..
If busybox is a good emulation of linux, this did not work:
H:\temp>busybox sh
H:/temp $ gpg ppp.txt | grep ""
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 4096-bit RSA key, ID 34C35AA4CB59468A, created 2024-12-24 "seanrima-gpgmail <thecivvie@gmail.com>"
gpg: encrypted with ECDH key, ID FB7964717AABB346
gpg: encrypted with 256-bit ECDH key, ID DB93C9CDECB10521, created 2025-06-04 "Philipe <philipe_rm1@hotmail.com>"
Sorry, I missed the " enclosed in ' quotes; however, same
result:
H:\temp>busybox sh
H:/temp $ gpg ppp.txt | grep '"'
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 4096-bit RSA key, ID 34C35AA4CB59468A, created 2024-12-24
"seanrima-gpgmail <thecivvie@gmail.com>"
gpg: encrypted with ECDH key, ID FB7964717AABB346
gpg: encrypted with 256-bit ECDH key, ID DB93C9CDECB10521, created 2025-06-04
"Philipe <philipe_rm1@hotmail.com>"
H:\temp>busybox sh
H:/temp $ gpg ppp.txt | grep '"'
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 4096-bit RSA key, ID 34C35AA4CB59468A, created
2024-12-24
"seanrima-gpgmail <thecivvie@gmail.com>"
gpg: encrypted with ECDH key, ID FB7964717AABB346
gpg: encrypted with 256-bit ECDH key, ID DB93C9CDECB10521, created
2025-06-04
"Philipe <philipe_rm1@hotmail.com>"
I guess busybox *isn't* a good emulation of Linux. It
works as expected on actual Linux. Maybe a Windows user
will chime in here.
H:/temp $ gpg > NUL -d ppp.txt 2> NUL2 ; grep \" NUL2
Hej August!
H:/temp $ gpg > NUL -d ppp.txt 2> NUL2 ; grep \" NUL2If you have 'tee' handy then try this;
H:/temp $ { gpg ppp.txt | tee NUL2; } &> NUL1 ; grep \" NUL2
'tee' will only output stdout to NUL2. Both stderr and stdout will get written to NUL1 which if you don't need it could be redirected to /dev/null or whatever your sh enviroment uses to represent the void.
Het leven is goed,
Maurice
o- o- -o o- o- -o o- -o o- o- -o -o o- -o -o -o
/) /) (\ /) /) (\ /) (\ /) /) (\ (\ /) (\ (\ (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Hwæt bið betst and wyrst? Ic ðe secge, mannes word.
What is the best and the worst thing? I tell you, man's word.
If you have 'tee' handy then try this;
H:/temp $ { gpg ppp.txt | tee NUL2; } &> NUL1 ; grep \" NUL2
'tee' will only output stdout to NUL2. Both stderr and stdout will get
written to NUL1 which if you don't need it could be redirected to
/dev/null or whatever your sh enviroment uses to represent the void. Het
leven is goed, Maurice
No.. I want to parse stderr that gpg produces.
August Abolins wrote to Dan Clough <=-
H:\temp>busybox sh
H:/temp $ gpg ppp.txt | grep '"'
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 4096-bit RSA key, ID 34C35AA4CB59468A, created
2024-12-24
"seanrima-gpgmail <thecivvie@gmail.com>"
gpg: encrypted with ECDH key, ID FB7964717AABB346
gpg: encrypted with 256-bit ECDH key, ID DB93C9CDECB10521, created
2025-06-04
"Philipe <philipe_rm1@hotmail.com>"
I guess busybox *isn't* a good emulation of Linux. It
works as expected on actual Linux. Maybe a Windows user
will chime in here.
Do you have an actual gpg output to show me?
You're forgetting that only the decrypted part goes to stdout,
and gpg errors and info go to stderr.
No.. I want to parse stderr that gpg produces.
No.. I want to parse stderr that gpg produces.
Then you're on the right track except I would suggest changing NUL to something else, say OUT and BOTH.
I'm reading that creating a ramdisk in linux is fairly simple and a
common feature.
I'm reading that creating a ramdisk in linux is fairly simple and a
common feature.
# mount -t tmpfs -o size=8g none /dev/lfs
creates a 8G ramdisk mounted on /dev/lfs.
# umount -v /dev/lfs
wipes it out.
What version of busybox do you have? That looks to be your salvation.
BusyBox v1.37.0
So.. no tmpfs.
However I see enough to make groovy things happen not unlike what you're doing with gpg. I have to wonder if mingw32's iconv is up to the task.
In your busybox env try 'iconv -l' and see what shows up. That should provide you a list of supported codepages. See if you can top this
list;
437//
500//
500V1//
850//
busybox's is not as long
UTF-8
UTF8
If whoever compiled the busybox you currently have, built in utf8 support then this should tell the tale;
$ echo -e "A M\uf8\uf8se once bit my sister ..."
You might not be able to read them properly but they *should* output the correct codes if indeed your busybox is up to the task.
Not sure what I was supposed to see.
H:\temp>busybox echo -e "A M\uf8\uf8se once bit my sister ..."
I built the same version of busybox on the Europoint
echo -e "A M\xf8\xf8se once bit my sister ..." | iconv -f latin1 -t utf8H:/ $ echo -e "A M\xf8\xf8se once bit my sister ..." | iconv -f latin1 -t utf8 A MA,A,se once bit my sister ...
busybox sh
busybox sh H:/ $ echo -e "A M\xf8\xf8se once bit my sister ..."| iconv -f latin1 -t utf8 A MA,A,se once bit my sister ... H:/ $
A limiting factor could certainly be the Font selected for my OpenXP terminal. Currently using Lucinda Console TTF
While in busybox, what is the output of
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
What are you using for your OpenXP terminal?
Or another option, that from what I've read has better UTF-8 support, would be to use PowerShell.
A limiting factor could certainly be the Font selected for my OpenXP terminal.
Currently using Lucinda Console TTF
Currently using Lucinda Console TTF
That shouldn't mess with the actual codes stored within the message. If it does then you have a crippled terminal. Even an old abandonware DOS editor will honour the codes despite the fact it cannot reproduce the proper charaters for display purposes. My best guess is that OpenXP has issues that have nothing to do with your choice in fonts. On the plus side it is in good company, msged and golded come to mind.
via simple Alt-[key] presses get the desired umlaut version for the
letters I needed. That was all done in a terminal of sorts with
Frontdoor editor, no problem.
If you have a choice, use UTF-8.
Windows-1257 - *Baltic*
ISO-8859-13 - *Baltic Rim*
IBM Code Page 775 (CP775) - *Baltic DOS*
via simple Alt-[key] presses get the desired umlaut version for the
letters I needed. That was all done in a terminal of sorts with
Frontdoor editor, no problem.
That still works in linux even on the commandline. In the case of the 'ø' character I just inserted it in vim using that exact method -
holding the left-Alt down while typing 2, 4 and 8 in that exact order. Note that it is automajically converted to utf8 by my current vimrc but could easily be an 8-bit Latvian character set. Pick one and I'll prove it.
Anyhow it looks like your busybox is capable. Too bad about your
crippled OS but thems the breaks when dealing with MS products.
At this stage, I would love to have my Alt-[key] functionality back.
Even the Windows keyboard language toggle seems to have stopped
working on my Win7 pc!
Hej Maurice!
I built the same version of busybox on the Europoint
$ ./_install/bin/busybox date -Ins
2026-01-19T03:31:42,219647248+00:00
:::evil grin:::
I'm a bad, bad boy.
H:\temp>busybox date -Ins
2026-01-20T20:25:49,906250000-05:00
Hej August!
H:\temp>busybox date -InsThank you. Definetly a good sign. You've renewed my faith.
2026-01-20T20:25:49,906250000-05:00
Het leven is goed,
Maurice
-o o- o- o- o- o- o- o- o- o- -o o- -o o- -o -o
(\ /) /) /) /) /) /) /) /) /) (\ /) (\ /) (\ (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... All'alba vincerò! Vincerò! Vincerò!
At dawn, I will win! I will win! I will win!
$ ./_install/bin/busybox date -Ins
2026-01-19T03:31:42,219647248+00:00
..but isn't yours,
$ ./_install/bin/busybox date -Ins
2026-01-19T03:31:42,219647248+00:00
..incorrect with the TZ offset?
$ TZ=PST8PDT date --date="2026-01-19T03:31:42,219647248+00:00"
| Sysop: | fluid |
|---|---|
| Location: | wickliffe, ohio |
| Users: | 2 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 66:55:48 |
| Calls: | 58 |
| Files: | 15,838 |
| Messages: | 57,151 |