pythonscript: any ready pyscript to replace one huge set of regex/ phrases with others?



  • I use pythonscript, but I am not much conversant with its coding so I could do just simple macro and not make complex script so far.

    I have about 10 tables in which one set of regex/ phrases are to be replaced with other regex/ phrase, given correspondingly in the table itself.

    frankly, I am using foxreplace in firefox to do so, and it is working.

    tables are huge, some have 1000s of such phrases, and those 4-5 tables are to be replaced one after another on the same data.

    And the content of those tables change almost daily.

    I don’t think it will be possible to create py script for all of those regex/ phrases. That is not the way of programming, as I see it, those phrases are data, and there should be a script that picks data from those tables and does the replacement.

    Is there any such ready script that will read data from csv txt file and does the replacement, also include other option for replacement like fullwordmatch and casematch.

    Actually, I am looking for a script that does what foxreplace does.

    Please guide.

    Thanks a gig.



  • @V-S-Rawat said:

    I am looking for a script that does what foxreplace does.

    Since you have a solution that works, why go looking for another one? Does having N++ do this for you give you some advantage?



  • @V-S-Rawat

    So a script to do something like you want is not really hard, something like this maybe:

    # format for each line is: delimiter then search regex then delimiter then replace regex
    sr_list = [
        '!a!A',
        '@b@B',
        '!c!C',
        ]
    
    # or take input from a file:
    #with open(r'sr_list.txt') as f: sr_list = f.readlines()
    
    editor.beginUndoAction()
    
    for line in sr_list:
        (s,r) = line[1:].rstrip().split(line[0])
        editor.rereplace(s,r)
    
    editor.endUndoAction()
    

    Of course it would have to be adapted to the exact format of your regex “data” if you don’t like the format that is in the script now.



  • @Alan-Kilborn
    just tested and it works like magic. 👍

    little question about the python script plugin:
    do you, by any chance, know of any hidden button or hotkey, to directly open the path to the user scripts at …\plugins\Config\PythonScript\scripts from within the plugin’s menu items, instead of browsing there manually ?



  • @Meta-Chuh said:

    do you, by any chance, know of any hidden button or hotkey, to directly open the path to the user scripts at …, instead of browsing there manually ?

    Hmmm, not really…I guess if I wanted that I would make it a Favorite in the Explorer plugin. :)



  • @Meta-Chuh ,

    As I learned a few months ago (it’s buried in the docs, but I needed other users to point it out to me): to edit an existing script, instead of clicking normally on the script, use Ctrl+Click. After that, you can use the tabbar > right-click entry to open that directory in Explorer, if you find that easier for opening other scripts from the same folder.

    update: https://github.com/bruderstein/PythonScript/issues/108 was where I learned this.



  • Since you have a solution that works, why go looking for another one?
    My data is in npp. I have to copy-paste it to firefox and run foxscript, and bring the processed data back to npp.

    Thanks.



  • @PeterJones

    wow. so simple. thanks.

    in my case, ctrl-leftclick on the script name in the menu, opens that script in npp to edit. rightclick doesn’t do anything.



  • @PeterJones

    Yes, but seems like @Meta-Chuh was looking for something more direct.



  • @PeterJones said:

    use Ctrl+Click

    thats even better, thanks.
    editing/viewing existing scripts is the thing i’ll probably use most in the future i suppose.

    btw: i just read your old thread and i just had to copy the following sentence and apply it unchanged to myself ;-)

    Well, I (me, metachuh) feel silly. It’s documented right there in the Installation: Usage in the help file: “To edit the script, just hold Ctrl down and click the script in the Scripts menu”. I guess that proves I’ve only read the help file when looking for specific commands. Someday, I should really read the whole thing. :-)



  • Hi, @alan-kilborn,

    I cannot get your Python script ( see below ) running correctly ! I certainly misunderstood what it is for :-(( To my mind, assuming your list, it should replace any lower-case letter a, b and c with the corresponding upper-case letter, in current file, shouldn’t it ?

    # format for each line is: delimiter then search regex then delimiter then replace regex
    sr_list = [
        '!a!A',
        '@b@B',
        '!c!C',
        ]
    
    # or take input from a file:
    #with open(r'sr_list.txt') as f: sr_list = f.readlines()
    
    editor.beginUndoAction()
    
    for line in sr_list:
        (s,r) = line[1:].rstrip().split(line[0])
        editor.rereplace(s,r)
    
    editor.endUndoAction()
    

    I tested your script, with Python script v1.2.0.0 and Notepad++ v6.0 and here is my debug info :

    Notepad++ v7.6   (32-bit)
    Build time : Nov 12 2018 - 23:51:42
    Path : D:\@@\760\notepad++.exe
    Admin mode : OFF
    Local Conf mode : ON
    OS : Windows XP (32-bit)
    Plugins : BetterMultiSelection.dll ComparePlugin.dll CustomizeToolbar.dll DSpellCheck.dll LightExplorer.dll LuaScript.dll mimeTools.dll NppConverter.dll NppExec.dll NppExport.dll NppTextFX.dll PythonScript.dll 
    

    On the other hand, my Python installation seems correct as, for instance, your other script, below, works nice, highlighting the strings Hello there, in light blue Mark style 1

    https://notepad-plus-plus.org/community/topic/16897/style-token-1-5-search-does-not-follow-default-case-sensitivity-of-find-dialog/5


    So, Alan, what obvious thing am I missing ?!

    Best Regards

    guy038



  • @guy038

    I am sorry to hear it didn’t work for you. :-(

    It is really a simple script, I’m not sure what could go wrong. Maybe try putting this line before the rereplace line and perhaps it will provide a hint of some sort: console.write('s:{} r:{}\n'.format(s,r))

    Also, but this would have nothing to do with it, the strings in sr_list should be raw strings for best use with regex without getting “LTS”. Thus, '!a!A' should be 'r!a!A' and same for any other strings put into the sr_list.



  • @guy038

    what happens if you try a complete new pythonscript 1.3.0.0 install on a new 7.6.2 portable ?
    still the same, or does alan’s script work on that ?

    i’ve added the folder locations, from the other py thread, below as convenience if lib location or anything else of the add ons might be a trigger:

    get a new copy of PythonScript_Full_1.3.0.0.zip from here
    extract it and put it’s contents as listed below

    PythonScript.dll, plugin dll goes to:
    npp.7.6.2.bin\plugins\PythonScript\PythonScript.dll

    python27.dll goes to:
    npp.7.6.2.bin\python27.dll

    machine level scripts and python library go to:
    npp.7.6.2.bin\plugins\PythonScript\lib\
    npp.7.6.2.bin\plugins\PythonScript\scripts\
       contains sample scripts and startup. py

    manual, context-help files go to:
    npp.7.6.2.bin\plugins\doc\PythonScript\
       contains PythonScript.chm up to version 1.2.0.0
       contains html docs since version 1.3.0.0

    user level scripts go to:
    npp.7.6.2.bin\plugins\config\PythonScript\scripts\
       note: this folder will be created automatically as soon as a new script is created.



  • @Alan-Kilborn said:

    It is really a simple script

    it may be simple, but it definitively comes in very handy.
    i use it, love it, and without you i wouldn’t have it. 😃👍

    before using your script, i used your suggested way of using macros for multi pass, multi regexes on files.
    (and before that, there was pure darkness 😂 )

    but now i prefer your script, as the regexes are much easier to change or read than within a saved macro. 👍👍👍



  • Hello @alan-kilborn, @meta-chuh and All,

    Sorry, I preferred to take some time, doing numerous tests and … it works nicely ;-))

    Alan, it’s just my mistake, because I should have opened the console, immediately ! Indeed, I wrote some accentuated characters above \x7f, although in a comment ! So I added the directive #coding=utf-8 as first line of the script. You’re really lucky as an [A-Z] person ;-))

    In order to run S/R in an insensitive way, I just imported the re library and used the flag re.IGNORECASE

    I also tried your second solution with strings/regexes in a file and… no problem, too !

    Just notice that, in this case, the exact python code is, rather :

    f = open(r'<Drive_Letter>:\....\....\sr_list.txt')
    
    sr_list = f.readlines()
    

    I, first thought that, according your comments, the part, to be inserted, was, literally :

    open(r'sr_list.txt') as f: sr_list = f.readlines()
    

    But, of course, this code is wrong and an error occurs on word as -:))


    Hi, @meta-chuh,

    Hummmm…, I’m hungry, since a while… So be patient a bit ! I be back very soon and, as I’ve already installed a portable v7.6.2 version of N++, I’ll, simply, need to add the latest Python

    Just before posting, I’ve seen your last reply to Alan and I do agree to your compliments ! It’s really a magic script ;-))

    Best Regards,

    guy038



  • An aside on as:

    @guy038 said:

    I, first thought that, according your comments, the part, to be inserted, was, literally :
    open(r'sr_list.txt') as f: sr_list = f.readlines()

    @Alan-Kilborn said:

    with open(r’sr_list.txt’) as f: sr_list = f.readlines()

    Having just done some Python tutorials, I learned about the with statement, which is what enables the as – the with was literally part of what was needed in order for the as to work



  • @guy038 said:

    It’s really a magic script

    It’s just a tiny, obvious script, at least to me. :)

    BTW glad you got it going.

    I think Peter straightened out the with/as stuff. I’ll just say that the line that started out #with was correct as written. The intent was that one would simply remove the comment (with ONE keypress) to enable the line. Note that my coding style is that if a line is an informational comment it starts out as # plus space plus text. If it is code that is commented out, it is # (at correct indent level), then no space(!), then code.

    [A-Z] person

    What is that? Why is it a lucky thing?



  • @Alan-Kilborn

    Note that my coding style is that if a line is an informational comment it starts out as # plus space plus text. If it is code that is commented out, it is # (at correct indent level), then no space(!), then code

    very nice and clean to read 👍

    [A-Z] person

    hahaha, i never thought that [A-Z] person could be interpreted as a potential insult, or discrimination, but it is not. 😂😂😂

    it’s just an expression for languages without special characters and letters like áàñøö and so on.



  • Hello @alan-kilborn, @meta-chuh and All,

    First, Alan, the expression “An [A-Z] person” is a common way, for @scott-sumner to point out that he’s poorly concerned about accentuated characters and all relative questions ! That’s why I said that you’re lucky for not having to bother about these problems ;-))

    Not also that I said, above, “is a common way” and notwas a common way” as I do hope that Scott will be back, on our forum, very soon !


    Now, of course, the Python syntax, below, is totally exact !

     with open(r'sr_list.txt') as f: sr_list = f.readlines()
    

    It’s just that when I saw the two comment lines :

    # or take input from a file:
    #with open(r'sr_list.txt') as f: sr_list = f.readlines()
    

    I thought, wrongly, it meant, in fact :

    # or take input from a file with [ the sentence ]:
    # open(r'sr_list.txt') as f: sr_list = f.readlines()
    

    BTW, Alan, I tested, in the sr_list.txt, the syntax |^|Test, with some space chars after the word Test and, unfortunately, the ending spaces are not taken in account. Of course, I could have used |^|Test\x20\x20\x20

    So, may I ask for two improvements :

    • The possibility to repeat the separator, after the replacement string, to take extra blank chars in account, either, in the sr_list.txt file or in the script, itself

    • The possibility to add comments, beginning with the usual # char, in the sr-list.txt file

    For instance :

    # Add the string ABC, followed with 3 SPACES, at BEGINNING of line 
    |^|ABC   |
    # Add the string XYZ, followed with 3 SPACES  at END of line
    !$!XYZ   !
    

    Contrary to what I said, @meta-chuh, I didn’t come back and just preferred going to bed as I’ve planned to spend a ski-day, as weather was quite nice, Wednesday, on Grenoble and, in addition, I also met some friends of mine, in Chamrousse ski-station ;-))

    As promised, I installed the last 1.3.0.0. Python script version in my local N++ v7.6.2 installation

    Let’s suppose that is N++ v7.6.2 is installed in any folder XXXX, different from folder C\Program files and folder C\Program files (x86). Then,

    • I downloaded the PythonScript_Full_1.3.0.0.zip archive, in XXXX folder

    • With 7zFileManager, I extracted all archive’s contents, in the XXXX folder

    • I needed to execute an extra task :

      • Move the library PythonScript.dll from the plugins folder to the plugins\PythonScript folder
    • I opened Notepad v7.6.2

      • I chose the menu option Plugins > Python Script > New Script and, immediately closed the window, with the ESC key, in order to create the file tree XXXX > plugins > Config > PythonScript > scripts

    Finally, here is, below, the main file’s layout, right after installing the last Python script v1.3.0.0 ::

    XXXX, below, represents the INSTALL folder of N++ v7.6.2 , which must be DIFFERENT from, either, "C\Program files" and "C\Program files (x86)"
    
    It's IMPORTANT to note that this LOCAL installation needs the ZERO-LENGTH file, "doLocalConf.xml", along with "notepad..exe"
    
    XXXX
        \
        |-- autoCompletion (folder)
        |                \
        |                |-- ".xml" files
        |
        |-- localization (folder)
        |              \
        |              |-- ".xml" files
        |
        |-- plugins (folder)
        |         \
        |         |-- Config (folder)
        |         |        \
        |         |        |-- Hunspell (folder)
        |         |        |          \
        |         |        |          |-- en_US.aff
        |         |        |          |
        |         |        |          |-- en_US.dic
        |         |        |
        |         |        |-- PythonScript (folder)
        |         |        |              \
        |         |        |              |-- scripts (folder)
        |         |        |                        \
        |         |        |                        |-- Future USER ".py" scripts
        |         |        |
        |         |        |-- ".ini" files
        |         |        |
        |         |        |-- nppPluginList.dll
        |         |
        |         |-- doc (folder)
        |         |     \
        |         |      |-- PythonScript(folder)
        |         |                     \
        |         |                     |-- _sources (folder)
        |         |                     |
        |         |                     |-- _static  (folder)
        |         |                     |
        |         |                     |-- ".html" files and Miscellaneous files
        |         |
        |         |-- DSpellCheck (folder)
        |         |             \
        |         |             |-- DSpellCheck.dll
        |         |
        |         |-- mineTools (folder)
        |         |           \
        |         |           |-- mineTools.dll
        |         |
        |         |-- NppConverter (folder)
        |         |              \
        |         |              |-- NppConverter.dll
        |         |
        |         |-- NppExport
        |         |           \
        |         |           |-- NppExport.dll
        |         |
        |         |-- PythonScript (folder)
        |         |              \
        |         |              |-- lib (folder)
        |         |              |     \
        |         |              |      |-- Sub-folders
        |         |              |      |
        |         |              |      |-- ".py" files
        |         |              |
        |         |              |-- scripts (folder)
        |         |              |         \
        |         |              |         |-- Samples (folder)
        |         |              |         |         \
        |         |              |         |         |-- ".py" scripts
        |         |              |         |
        |         |              |         |-- startup.py
        |         |              |
        |         |              |-- PythonScript.dll
        |
        |-- themes (folder)
        |        \
        |        |-- ".xml" files
        |
        |-- updater (folder)
        |         \
        |         |-- GUP.exe
        |         |
        |         |-- gup.xml
        |         |
        |         |-- libcurl.dll
        |
        |-- doLocalConf.xml
        |
        |-- Notepad++.exe
        |
        |-- python27.dll
        |
        |-- SciLexer.dll
        |
        |-- ".txt" files
        |
        |-- ".xml" CONFIGURATION files
    

    Best Regards,

    guy038

    P.S. :

    In the future, I think that, at least, for portable installs, when all problems concerning “Plugins Admin” are solved, it would be reasonable to migrate the Config and doc directories from the plugins folder to the higher level, with the other directories localization, autoCompletion, themes and updater

    So, the plugins folder would only contains sub-folders relative to each plugin installed ! What do you think of my idea ?



  • Hello @alan-kilborn, @meta-chuh and All,

    I’m answering to myself, concerning the last question, at the end of my previous post

    Eventually, it would not be a nice solution to do so as, indeed, the Config and doc folders contain, both, files rather relative to plugins, too !

    Cheers,

    guy038



  • @guy038 said:

    may I ask for two improvements

    We don’t really need to repeat the delimiter, we just need to NOT ignore trailing space. What causes an ignoring of the trailing space in the original script is the rstrip() function. By default this function removes all whitespace from the right side of a string. If we change it to tell it to only strip line ending characters, it will leave blanks on that side: rstrip('\n'). Note that this will work for line endings of \n or \r\n in the file. I mention this because at first glance it would appear to only work for line endings of \n but that is not the case.

    Using # as a comment character is also easy, we can do it with this logic: if line[0] == '#': continue which means "if the first column of the data is # then “continue” the “for” loop by jumping back up to the “for” line, ignoring the rest of the indented lines under the “for”.

    A new version of the “magic” (still LOL!) script is:

    # format for each line is: delimiter then search regex then delimiter then replace regex
    sr_list = [
        '!a!A  ',
        '# I start with # so I am merely a comment line',
        '@b@B',
        '!c!C',
        ]
    
    # or take input from a file:
    #with open(r'sr_list.txt') as f: sr_list = f.readlines()
    
    editor.beginUndoAction()
    
    for line in sr_list:
        if line[0] == '#': continue
        (s,r) = line[1:].rstrip('\n').split(line[0])
        editor.rereplace(s,r)
    
    editor.endUndoAction()

Log in to reply