feature request - word wrap per tab



  • @Alan-Kilborn

    No, I don’t use it.
    I have ALT+S bound to

    current_editor = eval('editor{}'.format(notepad.getCurrentView()+1))
    current_editor.setViewWS(not current_editor.getViewWS())
    current_editor.setViewEOL(not current_editor.getViewEOL())
    

    which basically toggles the WS and EOLs of the current view. :-)



  • @Alan-Kilborn

    tststs Alan, you are too impatience :-D



  • @Ekopalypse said:

    Alan, you are too impatience

    Maybe…just didn’t want you to forget. Thought a second person actually trying it might uncover a stopper in the process that would have caused the OP to throw up hands.

    I have ALT+S bound to

    Is this related to what we’re talking about here?

    current_editor = eval(‘editor{}’.format(notepad.getCurrentView()+1))

    Why not this instead of your code?:

    editor.setViewWS(editor.getViewWS())



  • @Alan-Kilborn

    Is this related to what we’re talking about here?

    No, just mentioned that I’m using something similar but also very different.

    Why not this instead of your code?:

    Because this was one of my first scripts I copied from somewhere and it did what it should and I never thought about it anymore and even today I didn’t think about but you are right, editor.setViewWS(not editor.getViewWS()) is the proper solution if you want to toggle.
    :-D
    You see, once something runs, I forget about it until something happens which might
    force me to reconsider what I’ve done previously. :-D



  • I’m considering going down the hacking path mentioned previously. I remember it being long and arduous and fraught with peril. I looked at the recommended python plugin above … seems like a specific version of python for specific versions of Notepad++. So if Notepad++ gets updated, is everything going to break?



  • @Clyfton-In said:

    hacking path

    LOL. Scripting plugins exist so one can add functionality. It’s only a hack if consider it a last resort. Which you do, so hack it is. :)

    seems like a specific version of python for specific versions of Notepad++

    Hmmm, not sure what this means…

    So if Notepad++ gets updated, is everything going to break?

    In general, no. But sometimes big changes have to be made in software for it to evolve. Recently we’ve seen some of these types of changes in Notepad++ and some of the plugins have lagged.



  • I only said hacking cause you said hacking 7 months ago:
    You can achieve your desired functionality right now if you don’t mind a bit of hacking.

    When I said … seems like a specific version of python for specific version of Notepad++ … it’s because the link you provided 3 days ago says this …

    for notepad++ 7.6.4, 64 bit (installed version):
    download and extract PythonScript_Full_1.3.0.0_x64.zip from >>> here <<< to your desktop.
    note: do not use any other available release type, except this zip.

    So if doing all the work to get a wrap toggle could just break in the next notepad++ update, no sense in pursuing.



  • @Clyfton-In said:

    I only said hacking cause you said hacking 7 months ago

    Haha. So I did. Maybe my views on hacking versus “endorsed solutions for augmentation” have slightly changed. :)

    no sense in pursuing

    Yea, probably that’s true.

    I guess I retract my advice.



  • +1 for this feature request, I have to flip my word wrap settings back and forth all the time, it’s getting annoying!



  • @Stan-Dm said in feature request - word wrap per tab:

    +1 for this feature request, I have to flip my word wrap settings back and forth all the time, it’s getting annoying!

    Might be a good idea. But +1-ing it here won’t affect the status of the feature request at https://github.com/notepad-plus-plus/notepad-plus-plus/issues/5232 .

    if it’s annoying for you, both this forum and the issues page show a PythonScript workaround that you can use while you are waiting to see if the feature is ever accepted or implemented. But given there’s a simple PythonScript workaround, there’s a good chance it never will be. (The developer philosophy for this project is that if it can easily be or has been implemented using a plugin, it’s not likely to be implemented as a native feature.)


Log in to reply