On Tue, Nov 19, 2013 at 09:34:22PM +, Stuart Henderson wrote:
On 2013/11/19 14:10, Theo de Raadt wrote:
In general, new non-standard options are bad.
I know and this is my own opinion to, in general.
Basically, if we add this someone will use it in a script. Then it will
become
Jan Klemkow j.klem...@wemelug.de wrote:
here is a diff that adds optional linebuffering to tr(1) with command
line switch -u like in sed(1). I need this to remove '\r' characters
from a continues input steam which lines have to be there immediately.
It's really odd to make tr output
On Tue, Nov 19, 2013, at 03:10 PM, Theo de Raadt wrote:
In general, new non-standard options are bad.
Basically, if we add this someone will use it in a script. Then it will
become non-portable. You cannot just invent something on your own like
this, without doing research to find out if
On 2013/11/20 07:40, Shawn K. Quinn wrote:
On Tue, Nov 19, 2013, at 03:10 PM, Theo de Raadt wrote:
In general, new non-standard options are bad.
Basically, if we add this someone will use it in a script. Then it will
become non-portable. You cannot just invent something on your own
On 2013/11/20 07:40, Shawn K. Quinn wrote:
FreeBSD and Dragonfly BSD have this option in tr. So, this actually
improves portability.
It's just spreading the disease. portable means it works everywhere.
Increasing the number of people who can write nonportable code is not
the same as
On Wed, Nov 20, 2013, at 12:49 PM, Ted Unangst wrote:
On 2013/11/20 07:40, Shawn K. Quinn wrote:
FreeBSD and Dragonfly BSD have this option in tr. So, this actually
improves portability.
It's just spreading the disease. portable means it works everywhere.
Increasing the number of
FreeBSD and Dragonfly BSD have this option in tr. So, this actually
improves portability.
It's just spreading the disease. portable means it works everywhere.
Increasing the number of people who can write nonportable code is not
the same as increasing portability.
How many others
On 20 Nov 2013, at 21:40, Theo de Raadt dera...@cvs.openbsd.org wrote:
FreeBSD and Dragonfly BSD have this option in tr. So, this actually
improves portability.
It's just spreading the disease. portable means it works everywhere.
Increasing the number of people who can write nonportable
FreeBSD and Dragonfly BSD have this option in tr. So, this actually
improves portability.
It's just spreading the disease. portable means it works everywhere.
Increasing the number of people who can write nonportable code is not
the same as increasing portability.
How many others
Hi,
here is a diff that adds optional linebuffering to tr(1) with command
line switch -u like in sed(1). I need this to remove '\r' characters
from a continues input steam which lines have to be there immediately.
Please write me if something is wrong with this diff or the change
itself. I
In general, new non-standard options are bad.
Basically, if we add this someone will use it in a script. Then it will
become non-portable. You cannot just invent something on your own like
this, without doing research to find out if someone else added a different
option. I don't see evidence
On 2013/11/19 14:10, Theo de Raadt wrote:
In general, new non-standard options are bad.
Basically, if we add this someone will use it in a script. Then it will
become non-portable. You cannot just invent something on your own like
this, without doing research to find out if someone else
12 matches
Mail list logo
