> > I think that turning off ksh's history is a minor issue which can be
> > handled is various ways
> Really? Actually, there was a thread on that topic on this list
> recently. If you have a solution, I'd appreciate hearing it. Or are
> you just guessing?
Just guessing. I refuse to believe that someone would write
a shell whose history file feature cannot be turned off.
> > I don't think that the content of the file (i.e. the base64-encoded
> > data) is ever passed to the shell, so there's no reason for it to
> > appear in the history. I believe that either you're confused or (if
> > you've actually witnessed such a thing)
Looks like I'm confused.
> As we speak, I have a 380k-and-growing (broken for mail)
[...]
> ^@mimencode -u -b <<'/////' >"/local/dev/tlroche/webassign/Format.pm"
> cGFja2FnZSBNYXRoOjpGb3JtYXQ7CiMgdmVyc2lvbiBiZWxvdwoKPXBvZAoKPWhlYWQxIE5BTUUK
> Ck1hdGg6OkZvcm1hdCAtIHBhY2thZ2UgZm9yIGZvcm1hdHRpbmcgQmlnSW50cyBhbmQgQmlnRmxv
> YXRzCgo9aGVhZDEgU1lOT1BTSVMKCgoKPWhlYWQxIERFU0NSSVBUSU9OCgo9aGVhZDEgUkVRVUlS
> RVMKCk1hdGg6OkJpZ0ludApNYXRoOjpCaWdGbG9hdAoKPWN1dAoKdXNlIE1hdGg6OkJpZ0ludCAx
Oh no! Here-documents!
Kai, is there a good reason for using here documents here ?
Isn't it possible to do
mimencode -u -b >"/local/dev/tlroche/webassign/Format.pm"
blablablablablba
blablablablablabla
\C-d
-- Stefan
