3 ms·
One thing I like to do and have been doing for a very long time, is have an optional flag '-e file'. This will redirect stderr to a file. I use it because: 1
by jmclnx 5y ago
One thing I like to do and have been doing for a very long time, is have an optional flag '-e file'.
This will redirect stderr to a file. I use it because:
1. I used tcsh and older systems csh
2. works great on DOS (like FreeDOS) and Microsoft Windows
I wish more people (ie: large companies) followed this guide, but in this day and age of mega-builds, I am afraid those days are over
- Cockbrand 5y agoOut of curiosity: how's this different from the following? command 2>outfile.txt Or is the intention just to be clearer/more obvious?
- jmclnx 5y agotcsh/csh cannot redirect stderr, there is no '2>'. There is a way but hard for me to remember
- legalcorrection 5y agoBetween every program being modified to work around your old shell or you switching to a modern shell like everyone else, which one do you think sounds more reasonable?
- jmclnx 5y agoUN*X has many shells for a reason, if you do not understand that then not much I can say to you. Also I never said people should change their programs, I do that on the ones I write for my purposes.
- jmclnx 5y agoI cannot edit, but I can see how you could have thought I was advocating '-e', I was not :) I was advocating the "Hints" article
- gumby 5y agoYou can do this straight from the shell without needing every program to be modified. I understand there are less powerful shells, as you list, but if for some reason you can’t use a more modern shell, aren’t you even less likely to be able to install updated apps?
- NateEag 5y agoAs one who has worked on ancient servers: Yes, installing updated third-party tools is very unlikely to happen. Installing updates to your own tools is likely a regular occurrence. So, your development style evolves to fit those constraints.