Hello,
Invoking ed -s file.txt, where file does not contain a newline at
the end, sends to stderr in spite of -s flag: newline appended.
Is this normal behaviour?
Yes, the -s option concern only messages printed on stdout.
Does ed/sed spoil files with non ascii bytes (for example unicode
Yes, the -s option concern only messages printed on stdout.
Sorry, this is bullshit.
The message: newline appended is an informational message, not a
diagnostic (error message). I supposed this is why it is not concerned
by the -s option.
On 2015-05-09 18:38, hru...@gmail.com wrote:
Invoking ed -s file.txt, where file does not contain a newline at the
end, sends to stderr in spite of -s flag: newline appended. Is this
normal behaviour?
Definitely normal behaviour. If it is *correct* behaviour is another,
philosophical, matter
Invoking ed -s file.txt, where file does not contain a newline at the
end, sends to stderr in spite of -s flag: newline appended. Is this
normal behaviour?
Does ed/sed spoil files with non ascii bytes (for example unicode characters)?
By experience seems to me that they, as also lex, do
4 matches
Mail list logo
