Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
03-07-2017, 05:30 AM
|
#1
|
Senior Member
Registered: Feb 2011
Distribution: Ubuntu, Centos
Posts: 1,240
Rep:
|
testing Next in sed
(source: http://docstore.mik.ua/orelly/unix/sedawk/ch06_01.htm)
This is the text:
Code:
Consult Section 3.1 in the Owner and Operator
Guide for a description of the tape drives
available on your system.
Code:
/Operator$/{
N
s/Owner and Operator\nGuide /Installation Guide\
/
}
The substitution is self-explanatory. The problem is that when I try sed -f script file.txt, I always get an indentation for the second line, like the following:
Code:
Consult Section 3.1 in the Installation Guide
for a description of the tape drives
available on your system.
Not sure what is causing this.
|
|
|
03-07-2017, 06:02 AM
|
#2
|
Senior Member
Registered: Feb 2011
Distribution: Ubuntu, Centos
Posts: 1,240
Original Poster
Rep:
|
Yes, the problem was actually the indentation made in the script file. After deleting all of spaces before N, s and / in the script file, it worked. I thought sed was supposed to ignore that.
Last edited by vincix; 03-07-2017 at 06:05 AM.
|
|
|
03-07-2017, 06:13 AM
|
#3
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,238
|
Why would you think that ?. You supplied the continuation after all ...
|
|
|
03-07-2017, 06:40 AM
|
#4
|
Senior Member
Registered: Feb 2011
Distribution: Ubuntu, Centos
Posts: 1,240
Original Poster
Rep:
|
What do you mean by "you supplied the continuation"?
I thought so because some guy on a lynda course about SED said so. He pointed out that you can indent as much as you want in the script file to make the text more readable and sed will ignore the leading spaces. And of course, in the examples that he provided, including the use of Next, it worked just fine.
Last edited by vincix; 03-07-2017 at 06:44 AM.
|
|
|
03-07-2017, 06:48 AM
|
#5
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 22,702
|
the s command (of sed) uses 3 delimiters (that is by default /):
Code:
s/substitute/replacement /modifiers
everything between the 2nd and 3rd occurrence is the replacement string, including spaces, tabs. Those cannot be ignored.
Last edited by pan64; 03-07-2017 at 06:55 AM.
Reason: include code tags
|
|
|
03-07-2017, 06:52 AM
|
#6
|
Senior Member
Registered: Feb 2011
Distribution: Ubuntu, Centos
Posts: 1,240
Original Poster
Rep:
|
Now I understand exactly where the problem was. It was the newline, obviously, and that example wasn't in the lynda course. The rest of the lines can be indented, but the \ line cannot be indented unless I want to add some spaces or whatever else after the newline. So that's exactly where the problem was.
Thanks
|
|
|
All times are GMT -5. The time now is 02:43 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|