exploding string into individual characters using a shell script
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I like this!
But you're (unknowingly) pointing at something I've always wondered: If you write a sed rule like 's|(\something\)|\1 something|g' (note that something is *after* the \1, and the 'g' option), is there a risk on any platform, that sed will apply the same rule to the something that is after \1? Or will parsing go on with what is after the initial \(something\) consistently on all platforms?
In short, is there a risk to write a rule that will infinitely recurse?
Well, If such a bug existed, it would have manifested itself since 1978, where the first sed was made available (Unix version 7), and I'm not aware of that.
Another side note, both my answer and yours are in fact non portable, as they use a gnu extension allowing \n to be present in the replacement string.
With standard Unix sed, one should use something like:
echo "$URL" | sed 's/./&\^J/g'
Where ^J is a real newline, entered as is or with the sequence control-V control-J.