Newlines in BSD sed vs gsed The Next CEO of Stack OverflowInsert after a second pattern in sedHow can I instruct BSD sed to interpret escape sequences like n and t?sed on OSX insert at a certain lineadd newlines in .cshrc command outputAre there standard versions of `sed` on which `-E` is unsupported?Using sed command arguments to be compatible with both GNU & BSD Unix (in-place editing)Using BSD jot for generating file with random contentHow to add some text before another with sed in FreeBSD?Does Apple modify the GNU and BSD tools that comes with macOS?Are there multiple flavors of the GNU tools?
How did people program for Consoles with multiple CPUs?
Which one is the true statement?
INSERT to a table from a database to other (same SQL Server) using Dynamic SQL
What steps are necessary to read a Modern SSD in Medieval Europe?
How to avoid supervisors with prejudiced views?
Why is quantifier elimination desirable for a given theory?
Math-accent symbol over parentheses enclosing accented symbol (amsmath)
How to install OpenCV on Raspbian Stretch?
Does soap repel water?
Is there always a complete, orthogonal set of unitary matrices?
What was the first Unix version to run on a microcomputer?
Is micro rebar a better way to reinforce concrete than rebar?
Is it my responsibility to learn a new technology in my own time my employer wants to implement?
Why didn't Khan get resurrected in the Genesis Explosion?
RigExpert AA-35 - Interpreting The Information
Why do airplanes bank sharply to the right after air-to-air refueling?
Is it ever safe to open a suspicious HTML file (e.g. email attachment)?
How many extra stops do monopods offer for tele photographs?
Why don't programming languages automatically manage the synchronous/asynchronous problem?
How to invert MapIndexed on a ragged structure? How to construct a tree from rules?
Why do remote US companies require working in the US?
Is it possible to replace duplicates of a character with one character using tr
Proper way to express "He disappeared them"
Running a General Election and the European Elections together
Newlines in BSD sed vs gsed
The Next CEO of Stack OverflowInsert after a second pattern in sedHow can I instruct BSD sed to interpret escape sequences like n and t?sed on OSX insert at a certain lineadd newlines in .cshrc command outputAre there standard versions of `sed` on which `-E` is unsupported?Using sed command arguments to be compatible with both GNU & BSD Unix (in-place editing)Using BSD jot for generating file with random contentHow to add some text before another with sed in FreeBSD?Does Apple modify the GNU and BSD tools that comes with macOS?Are there multiple flavors of the GNU tools?
The sed, which comes with FreeBSD 11.2 p7, gives:
$ seq 10 | sed 'N; l; D; p'
1$
2$
2$
3$
3$
4$
4$
5$
5$
6$
6$
7$
7$
8$
8$
9$
9$
10$
While gsed (GNU sed 4.7) gives for the same script:
$ seq 10 | gsed 'N; l; D; p'
1n2$
2n3$
3n4$
4n5$
5n6$
6n7$
7n8$
8n9$
9n10$
10
How can we explain this difference in behavior?
sed gnu newlines bsd
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
add a comment |
The sed, which comes with FreeBSD 11.2 p7, gives:
$ seq 10 | sed 'N; l; D; p'
1$
2$
2$
3$
3$
4$
4$
5$
5$
6$
6$
7$
7$
8$
8$
9$
9$
10$
While gsed (GNU sed 4.7) gives for the same script:
$ seq 10 | gsed 'N; l; D; p'
1n2$
2n3$
3n4$
4n5$
5n6$
6n7$
7n8$
8n9$
9n10$
10
How can we explain this difference in behavior?
sed gnu newlines bsd
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
add a comment |
The sed, which comes with FreeBSD 11.2 p7, gives:
$ seq 10 | sed 'N; l; D; p'
1$
2$
2$
3$
3$
4$
4$
5$
5$
6$
6$
7$
7$
8$
8$
9$
9$
10$
While gsed (GNU sed 4.7) gives for the same script:
$ seq 10 | gsed 'N; l; D; p'
1n2$
2n3$
3n4$
4n5$
5n6$
6n7$
7n8$
8n9$
9n10$
10
How can we explain this difference in behavior?
sed gnu newlines bsd
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
The sed, which comes with FreeBSD 11.2 p7, gives:
$ seq 10 | sed 'N; l; D; p'
1$
2$
2$
3$
3$
4$
4$
5$
5$
6$
6$
7$
7$
8$
8$
9$
9$
10$
While gsed (GNU sed 4.7) gives for the same script:
$ seq 10 | gsed 'N; l; D; p'
1n2$
2n3$
3n4$
4n5$
5n6$
6n7$
7n8$
8n9$
9n10$
10
How can we explain this difference in behavior?
sed gnu newlines bsd
sed gnu newlines bsd
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
edited 7 hours ago
Jeff Schaller♦
44.4k1162143
44.4k1162143
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
asked 8 hours ago
wolf-revo-catswolf-revo-cats
873935
873935
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
BSD sed, when using l to output characters in a visually unambiguous form, does not output newlines in a visually unambiguous form.
From sed(1) on OpenBSD:
[2addr]l
(The letter ell.) Write the pattern space to the standard output
in a visually unambiguous form. This form is as follows:
backslash \
alert a
backspace b
form-feed f
carriage-return r
tab t
vertical tab v
(note lack of mentioning of newlines).
GNU sed, however, includes newlines in the set of characters to display unambiguously. It does this as an extension to the set of characters that the POSIX standard for sed mentions (which is the set that BSD sed uses). GNU sed behaves this way even if --posix is used on the command line.
GNU sed also outputs 10 twice, while BSD sed does not. Running GNU sed with POSIXLY_CORRECT set or with --posix will make it output 10 only once, like BSD sed does.
This is because GNU sed by default ignores the part of POSIX definition of the sed N command that says
If no next line of input is available, the
Ncommand verb shall branch to the end of the script and quit without starting a new cycle or copying the pattern space to standard output.
Note also that the p in your sed program never executes, as D starts a new cycle.
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
2
Another difference is 10 being displayed once with BSD sed, and this time GNU sed behaves like BSD sed with POSIXLY_CORRECT. That's why you generally want to use$!Ninstead ofNwhen-nis not enabled.
– Stéphane Chazelas
7 hours ago
@StéphaneChazelas Thanks. I did not notice that difference at first.
– Kusalananda♦
7 hours ago
Note that ast-open's sed behaves like GNU sed wrtndisplayed byl. I suspect the POSIX requirement is an oversight here (they say it's not applicable which doesn't make sense here, I suspect they say that because the pattern space normally doesn't contain newline by default but overlook the fact that it can be added by N, G, s...; if they wanted to require the original sed behaviour, they would have said something like newline shall be output literally or something like that)
– Stéphane Chazelas
7 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509606%2fnewlines-in-bsd-sed-vs-gsed%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
BSD sed, when using l to output characters in a visually unambiguous form, does not output newlines in a visually unambiguous form.
From sed(1) on OpenBSD:
[2addr]l
(The letter ell.) Write the pattern space to the standard output
in a visually unambiguous form. This form is as follows:
backslash \
alert a
backspace b
form-feed f
carriage-return r
tab t
vertical tab v
(note lack of mentioning of newlines).
GNU sed, however, includes newlines in the set of characters to display unambiguously. It does this as an extension to the set of characters that the POSIX standard for sed mentions (which is the set that BSD sed uses). GNU sed behaves this way even if --posix is used on the command line.
GNU sed also outputs 10 twice, while BSD sed does not. Running GNU sed with POSIXLY_CORRECT set or with --posix will make it output 10 only once, like BSD sed does.
This is because GNU sed by default ignores the part of POSIX definition of the sed N command that says
If no next line of input is available, the
Ncommand verb shall branch to the end of the script and quit without starting a new cycle or copying the pattern space to standard output.
Note also that the p in your sed program never executes, as D starts a new cycle.
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
2
Another difference is 10 being displayed once with BSD sed, and this time GNU sed behaves like BSD sed with POSIXLY_CORRECT. That's why you generally want to use$!Ninstead ofNwhen-nis not enabled.
– Stéphane Chazelas
7 hours ago
@StéphaneChazelas Thanks. I did not notice that difference at first.
– Kusalananda♦
7 hours ago
Note that ast-open's sed behaves like GNU sed wrtndisplayed byl. I suspect the POSIX requirement is an oversight here (they say it's not applicable which doesn't make sense here, I suspect they say that because the pattern space normally doesn't contain newline by default but overlook the fact that it can be added by N, G, s...; if they wanted to require the original sed behaviour, they would have said something like newline shall be output literally or something like that)
– Stéphane Chazelas
7 hours ago
add a comment |
BSD sed, when using l to output characters in a visually unambiguous form, does not output newlines in a visually unambiguous form.
From sed(1) on OpenBSD:
[2addr]l
(The letter ell.) Write the pattern space to the standard output
in a visually unambiguous form. This form is as follows:
backslash \
alert a
backspace b
form-feed f
carriage-return r
tab t
vertical tab v
(note lack of mentioning of newlines).
GNU sed, however, includes newlines in the set of characters to display unambiguously. It does this as an extension to the set of characters that the POSIX standard for sed mentions (which is the set that BSD sed uses). GNU sed behaves this way even if --posix is used on the command line.
GNU sed also outputs 10 twice, while BSD sed does not. Running GNU sed with POSIXLY_CORRECT set or with --posix will make it output 10 only once, like BSD sed does.
This is because GNU sed by default ignores the part of POSIX definition of the sed N command that says
If no next line of input is available, the
Ncommand verb shall branch to the end of the script and quit without starting a new cycle or copying the pattern space to standard output.
Note also that the p in your sed program never executes, as D starts a new cycle.
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
2
Another difference is 10 being displayed once with BSD sed, and this time GNU sed behaves like BSD sed with POSIXLY_CORRECT. That's why you generally want to use$!Ninstead ofNwhen-nis not enabled.
– Stéphane Chazelas
7 hours ago
@StéphaneChazelas Thanks. I did not notice that difference at first.
– Kusalananda♦
7 hours ago
Note that ast-open's sed behaves like GNU sed wrtndisplayed byl. I suspect the POSIX requirement is an oversight here (they say it's not applicable which doesn't make sense here, I suspect they say that because the pattern space normally doesn't contain newline by default but overlook the fact that it can be added by N, G, s...; if they wanted to require the original sed behaviour, they would have said something like newline shall be output literally or something like that)
– Stéphane Chazelas
7 hours ago
add a comment |
BSD sed, when using l to output characters in a visually unambiguous form, does not output newlines in a visually unambiguous form.
From sed(1) on OpenBSD:
[2addr]l
(The letter ell.) Write the pattern space to the standard output
in a visually unambiguous form. This form is as follows:
backslash \
alert a
backspace b
form-feed f
carriage-return r
tab t
vertical tab v
(note lack of mentioning of newlines).
GNU sed, however, includes newlines in the set of characters to display unambiguously. It does this as an extension to the set of characters that the POSIX standard for sed mentions (which is the set that BSD sed uses). GNU sed behaves this way even if --posix is used on the command line.
GNU sed also outputs 10 twice, while BSD sed does not. Running GNU sed with POSIXLY_CORRECT set or with --posix will make it output 10 only once, like BSD sed does.
This is because GNU sed by default ignores the part of POSIX definition of the sed N command that says
If no next line of input is available, the
Ncommand verb shall branch to the end of the script and quit without starting a new cycle or copying the pattern space to standard output.
Note also that the p in your sed program never executes, as D starts a new cycle.
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
BSD sed, when using l to output characters in a visually unambiguous form, does not output newlines in a visually unambiguous form.
From sed(1) on OpenBSD:
[2addr]l
(The letter ell.) Write the pattern space to the standard output
in a visually unambiguous form. This form is as follows:
backslash \
alert a
backspace b
form-feed f
carriage-return r
tab t
vertical tab v
(note lack of mentioning of newlines).
GNU sed, however, includes newlines in the set of characters to display unambiguously. It does this as an extension to the set of characters that the POSIX standard for sed mentions (which is the set that BSD sed uses). GNU sed behaves this way even if --posix is used on the command line.
GNU sed also outputs 10 twice, while BSD sed does not. Running GNU sed with POSIXLY_CORRECT set or with --posix will make it output 10 only once, like BSD sed does.
This is because GNU sed by default ignores the part of POSIX definition of the sed N command that says
If no next line of input is available, the
Ncommand verb shall branch to the end of the script and quit without starting a new cycle or copying the pattern space to standard output.
Note also that the p in your sed program never executes, as D starts a new cycle.
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
edited 7 hours ago
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
answered 7 hours ago
Kusalananda♦Kusalananda
138k17258428
138k17258428
2
Another difference is 10 being displayed once with BSD sed, and this time GNU sed behaves like BSD sed with POSIXLY_CORRECT. That's why you generally want to use$!Ninstead ofNwhen-nis not enabled.
– Stéphane Chazelas
7 hours ago
@StéphaneChazelas Thanks. I did not notice that difference at first.
– Kusalananda♦
7 hours ago
Note that ast-open's sed behaves like GNU sed wrtndisplayed byl. I suspect the POSIX requirement is an oversight here (they say it's not applicable which doesn't make sense here, I suspect they say that because the pattern space normally doesn't contain newline by default but overlook the fact that it can be added by N, G, s...; if they wanted to require the original sed behaviour, they would have said something like newline shall be output literally or something like that)
– Stéphane Chazelas
7 hours ago
add a comment |
2
Another difference is 10 being displayed once with BSD sed, and this time GNU sed behaves like BSD sed with POSIXLY_CORRECT. That's why you generally want to use$!Ninstead ofNwhen-nis not enabled.
– Stéphane Chazelas
7 hours ago
@StéphaneChazelas Thanks. I did not notice that difference at first.
– Kusalananda♦
7 hours ago
Note that ast-open's sed behaves like GNU sed wrtndisplayed byl. I suspect the POSIX requirement is an oversight here (they say it's not applicable which doesn't make sense here, I suspect they say that because the pattern space normally doesn't contain newline by default but overlook the fact that it can be added by N, G, s...; if they wanted to require the original sed behaviour, they would have said something like newline shall be output literally or something like that)
– Stéphane Chazelas
7 hours ago
2
2
Another difference is 10 being displayed once with BSD sed, and this time GNU sed behaves like BSD sed with POSIXLY_CORRECT. That's why you generally want to use
$!N instead of N when -n is not enabled.– Stéphane Chazelas
7 hours ago
Another difference is 10 being displayed once with BSD sed, and this time GNU sed behaves like BSD sed with POSIXLY_CORRECT. That's why you generally want to use
$!N instead of N when -n is not enabled.– Stéphane Chazelas
7 hours ago
@StéphaneChazelas Thanks. I did not notice that difference at first.
– Kusalananda♦
7 hours ago
@StéphaneChazelas Thanks. I did not notice that difference at first.
– Kusalananda♦
7 hours ago
Note that ast-open's sed behaves like GNU sed wrt
n displayed by l. I suspect the POSIX requirement is an oversight here (they say it's not applicable which doesn't make sense here, I suspect they say that because the pattern space normally doesn't contain newline by default but overlook the fact that it can be added by N, G, s...; if they wanted to require the original sed behaviour, they would have said something like newline shall be output literally or something like that)– Stéphane Chazelas
7 hours ago
Note that ast-open's sed behaves like GNU sed wrt
n displayed by l. I suspect the POSIX requirement is an oversight here (they say it's not applicable which doesn't make sense here, I suspect they say that because the pattern space normally doesn't contain newline by default but overlook the fact that it can be added by N, G, s...; if they wanted to require the original sed behaviour, they would have said something like newline shall be output literally or something like that)– Stéphane Chazelas
7 hours ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509606%2fnewlines-in-bsd-sed-vs-gsed%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
