Find and replace ... HELP

  • hi,

    I have a script file that contains many of these:

    ♪ All I need Is my buddies ♪

    ♪ High with a little help
    from my friends ♪

    I would like to edit something like this:
    6 ♪ All I need Is my buddies ♪
    7 ♪ High with a little help from my friends ♪

    can anyone help me on this? Many thanks.


  • I would do it in two stages:

    1. FIND = (\d)\R+(?=♪), REPLACE = \1\x20 (which is the digit followed by a space), MODE = regex
    2. FIND = (?s)\d ♪[^♪]*?\K\h*\R, REPLACE = \x20, MODE = regex

    If some numbers have more than two lines of lyrics, run #2 a total of n-1 times to merge n-lines of lyrics per number.

    regex gurus might be able to tweak that into a miracle single-regex, but this should be enough for your needs

    FYI: I often add this to my response in regex threads, unless I am sure the original poster has seen it before. Here is some helpful information for finding out more about regular expressions, and for formatting posts in this forum (especially quoting data) so that we can fully understand what you’re trying to ask:

    This forum is formatted using Markdown, with a help link buried on the little grey ? in the COMPOSE window/pane when writing your post. For more about how to use Markdown in this forum, please see @Scott-Sumner’s post in the “how to markdown code on this forum” topic, and my updates near the end. 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). If you want to clearly communicate your text data to us, you need to properly format it.

    If you have further search-and-replace (“matching”, “marking”, “bookmarking”, regular expression, “regex”) needs, study this FAQ and the documentation it points to. Before asking a new regex question, understand that for future requests, many of us will expect you to show what data you have (exactly), what data you want (exactly), what regex you already tried (to show that you’re showing effort), why you thought that regex would work (to prove it wasn’t just something randomly typed), and what data you’re getting with an explanation of why that result is wrong. When you show that effort, you’ll see us bend over backward to get things working for you. If you need help formatting, see the paragraph above.

    Please note that for all regex and related queries, it is best if you are explicit about what needs to match, and what shouldn’t match, and have multiple examples of both in your example dataset. Often, what shouldn’t match helps define the regular expression as much or more than what should match.

  • I did #1 and it worked but #2 does not work. can you double check #2? thanks!

  • @Jin-Wook-Lee said:

    can you double check #2?


    looks right to me.


    If it doesn’t work for you, maybe your data didn’t match your example, or something else is going on. Feel free to supply more details.

Log in to reply