If you have further search-and-replace (“matching”, “marking”, “bookmarking”, regular expression, “regex”) needs, study this FAQ and the documentation it points to. If you want to clearly communicate your text data to us, you need to properly format it. It is very important that you use these formatting tips – using single backtick marks around small snippets, and using code-quoting for pasting multiple lines from your example data files – because otherwise, the forum will change normal quotes ( "") to curly “smart” quotes ( “”), will change hyphens to dashes, will sometimes hide asterisks (or if your text is c:\folder\*.txt, it will show up as c:\folder*.txt, missing the backslash). ![]() For more about how to use Markdown in this forum, please see post in the “how to markdown code on this forum” topic, and my updates near the end. This forum is formatted using Markdown, with a help link buried on the little grey ? in the COMPOSE window/pane when writing your post. ![]() ![]() Note that assumptions like these are good reasons for providing sufficient data to tell what you really want, and what are allowed and not allowed situations. having a space, with how artificial your data was, I assumed you may have oversimplified the example, and didn’t want to risk you coming back and saying “but I had a space”. I was originally going to replace with a space, but I realized that, even though your data doesn’t show any of the lines inside an. If it does, pick any other unicode character you are sure isn’t in your data. ![]() By way of explanation: I chose a smiley face as a “record separator” that was unlikely to occur in your data.
0 Comments
Leave a Reply. |