@Lycan-Thrope said in Unsaved Files Recovery Script:

No one, that makes their way here, can claim to be a computer neophyte. Period. If they have done any computer work previously, they will have learned the major rule. Save and save often. That NPP has an additional edge of protection, should not make them abandon their common sense computer behavior that should have been ingrained in them before they got here.
Because it’s suddenly fashionable to jump off a cliff, does that mean everyone should go jump off a cliff? Certainly not
(…)
the prudent way to mitigate data loss, is to purposely save the document, originally and often.

Once again, we agree on these points. However, they aren’t as relevant to the points we are making as you seem to think:

I have already acknowledged that most NP++ likely discover the Session feature by accident, but perhaps I wasn’t clear about linking this discovery to the independent usage that I also mentioned. Personally, I discovered this feature as I was using NP++ on my own, and I’m guessing that this is true for most of the other users who make use of this feature as well. So, your “fashionable to jump off a cliff” argument isn’t likely relevant here (at least not for the majority of users).

Either way, users who do make use of it learn that it is (surprisingly?) reliable - content is preserved in the vast majority of use cases. However, despite this high degree of reliability, I don’t think users are relying on it for important data, regardless of how they discovered it in the first place. Personally, I simply use it for things like scrap notes - content that isn’t important enough to warrant a new file in any of the various directories that I work out of, but important enough to be (potentially) useful again in the future, yet would not be significantly missed if lost.

Obviously, I can’t speak for other users, but I’d imagine that they use this feature for the same sort of thing. Either way, I certainly agree that anyone who relies on it for more important content is doing so unwisely. In fact, this principle would still apply if the feature were to be reinforced: the goal of the proposed reinforcement is not, as you seem to fear (and rightfully so), to make users comfortable with expanding the importance of the content within their preserved files, it is simply to mitigate inconveniences. So, it’s not crucial to reinforce any limitations that this feature might have, but it is undeniably preferable.

@Robert-Leduc

Suggestion: If you don’t know what a plugin is doing, perhaps uninstall it.

@External-Usage ,

Unfortunately, your question was severely lacking in details, which, as it currently stands, makes it impossible to meaningfully debug. You will have to provide more details if you want help.

Could you share your ?-menu’s Debug Info? if the Debug Info doesn’t say, also share what version of NppFTP you are using (Plugins > NppFTP > About NppFTP, Alt+PrintScreen, paste in your reply) Could you show screenshots of each page of your NppFTP Profile Settings for the profile that’s crashing feel free to use mspaint or other screenshot-editing tool to delete private information, like the URL of your server, or your username on Connection page, Connection Type, Porty, and Timeout are probably the most importrant the transfers and FTP Misc might have useful data but share each page, just in case Before the crash, does NppFTP show progress in its progress panel; does it show anything that you can copy or screenshot from the NppFTP Output window?

Are there any other hints you can give us?

The official release (v0.29.13, available in Plugins Admin) hasn’t been updated since 2023… but the github releases page does let you manually download “pre-release” versions. It may be that v0.30.19 will work better for you.

hi, i rename in a script the updater directory, after the installation.

something like that:

function Rename-Updater { param ( [string]$instpath ) Write-Log "Updater-Renaming started." if (Test-Path "$instpath\updater_old") { Write-Log "Removing old updater folder at: $instpath\updater_DisabledZi" Remove-Item -Path "$instpath\updater_old\*" -Force -Recurse Remove-Item -Path "$instpath\updater_old -Force -Recurse } Rename-Item -Path "$instpath\updater" -NewName "updater_old" Write-Log "Updater folder renamed to updater_old"

and then after the installation part in the script:

# Perform updater renaming $instpath= "$env:ProgramFiles\NOTEPA~1" Rename-Updater -instpfad $instpath Write-Log "Script ended successfully."

—

moderator added code markdown around text; please don’t forget to use the </> button to mark example text as “code” so that characters don’t get changed by the forum

@External-Usage ,

Notepad++ uses a library called “Lexilla” for doing the lexing. Lexilla has a “testbed” editor called SciTE which shows they have the same problem

a51ce8b6-9c94-43aa-8498-356479d7781f-image.png

Per this recent discussion here, there is an open request with the Lexilla team to allow nested CSS (and the & selector). Until Lexilla is able to fix their library to handle nested CSS properly, Notepad++ will not be able to; once they release a version with that fix, and once Notepad++ updates to that version, then it will be fixed in Notepad++… but since the request has been active since 2023, I am doubtful it will happen any time soon. Sorry.

@guy038

To be honest, no, I didn’t look further into boost::regex and Unicode after the problems, probably only caused by my ignorance, occurred with Nim. I admit that an implementation for the EnhanceAnyLexer plugin would be beneficial, but the interaction with cpp code still gives me a stomach ache.

@PeterJones

Ok, I have another suggestion then

How about a script that auto-replies to queued post

something like

“Your post $title has been received and is in moderation queue”

The notification bell at the top upper right corner is very hard to ignore, it’s probably the best way to stop users thinking their post got lost somehow.

Lastly, I logged in from a long lasting, good standing github account.

I would have much preferred login in from my usual disposable single use email account, but ok you guys are legit and you can have a little bit of my identity. But I would suggest that login for accounts with a long history oauth identifiers could then be given leniency with the modding queue ?

Well, anyway, this isn’t that big of a deal ! Hopefully you don’t have to have this conversation with every tourist like me that stops by ah ha !

good bye !

@guy038 ,

When I look at the event history, it shows that you approved the @R0binBl00d post and two copies of essentially the same post by another user (that’s the one that I then deleted two of their three posts, because it was effectively the same post three times, posted due to queue impatience).

So don’t worry, I don’t think any posts were accidentally lost.

update: And going forward, @R0binBl00d should have enough reputation to bypass the post queue.

@Alan-Kilborn said in Windows XP support being dropped...how do people feel?:

Developers did nothing for Linux; (…) [they] aren’t putting effort into maintaining compatibility with this OS.

To clarify, I was referring to Wine developers, not NP++ developers. Any XP compatibility would have to come from the XP community; if Linux users can figure out how to adapt Windows software to work on Linux, XP users should be able to figure out how to adapt newer Windows software to XP.

@Michael-Fuerst said in Bold text:

Several web sites can convert plain text to bold, italic, etc. which can be then copied into Facebook. For example https://capitalizemytitle.com/bold-text-generator/ If the NP++ encoding is set to UTF-16, some of the output from these converting web sites will appear as bold or italic when pasted into NP++.
However, this text will not retain its bold/italic if edited.
This suggests that bold or italic text could some how be directly typed into NP++

The way this website works is that it replaces your characters with Unicode characters in peculiar ranges. Thus, if you enter:
Show me.
into that website, you get back:
𝐒𝐡𝐨𝐰 𝐦𝐞.

But those are not the letters S, h, o, w, etc. rendered in a bold font; they are different characters entirely. If you paste into this web site
you’ll see the analysis — the letters are actually mathematical symbols.

So, when you edit and type using the keyboard, you’re typing ordinary letters, not these odd Unicode characters.

eeee@PeterJones Thank for the information. I tried looking and could not find it. I will certainly post there for the feature.

@Malstroem-Phi said in Too frequent updates are disruptive:

Side notes I had to agree to this in order to post something (which I did not want to):

Our Logging-in FAQ has more on that…

Essentially, the “personal information” it collects was what is sufficient to create your account, defaulting to whatever you’ve put in your Google or GitHub name/email/avatar fields, after which you can edit what is shown.

For the email, there has not been an “update” email sent to the entire userbase in the 9 years I’ve had an account here. For the the notification emails, they are 100% under your control settings – there’s a whole page in your settings devoted to setting your individual preferences, and you can turn off all those emails you want. When we were offering a digest, you could also disable it on the same page, but we turned off digests recently because it was causing too many server errors and causing our email server to be blacklisted as spam.

And most of my last paragraph was essentially explained in the message you read.

So I am confused why you were worried enough to proclaim:

I’ll probably delete the account after a while if it turns out emails are too frequent.

The message you quoted was pretty clear that they wouldn’t be frequent unless you set them to be, and was quite explicit that you could turn off notifications that you didn’t want. I am not sure why this message set off your “worry” reflex.

—

Back to the main content:

I think that if the update were a matter of a single click with a very quick restart,

The updater now has the one-click silent update feature, so going forward, the update process should be fairly painless – or at least, have fewer clicks than it used to require. (Though I agree, it asks at an inconvenient time for some – many would want to wait for the update until they are done with the app, rather than immediately after it was launched; the developer has not seemed willing to change the timing of it.)

in a perfect world I would recommend a granular notification system where you can choose what can of update you want to know about, for instance you could choose to skip small fix about features you never use but be notified for security updates or other more critical stuff.

Notepad++ has never really distinguinguished different types of releases. All releases include minor bugfixes, new features, and any needed security fixes. So every release would fall under all the categories (or at least two of the three – security fixes are likely not as frequently needed, depending on your definition of “security fixes”).

And in case you didn’t look at the “read this post first” or the FAQ it points you to – this forum is the Community of fellow Notepad++ users, so none of us here have the decision making power for how Notepad++ implements updates.

@mkupper,

Yes, the “Start in” was a wrong folder, because this was just a demo, and I overlooked it. (I still had to decide if this was worth doing.) Sorry about that.

Now I’ve set up the different n++ portable versions, and everything works as expected. No more fiddling with direct write, no more adjusting UDLs to match the current theme, no more forgetting to turn backup back on. This a is revolutionary change. Thanks!

@Dave-Torr said:

But seems clear it has replaced a convenient one-click option with 2 click - more exercise for my clicking finger!

Again: It was previously a 2-click operation; now it’s a 3-action operation. Read above (clearly you didn’t) for detail on that.

What the change has done has made the right-click “open” command actually usable for me (and guessing here, other users), at a slight inconvenience to you. Sorry for that but IMO the software is better for the change.

@xomx said in Random crashes began 1-2 months ago:

IDK. There are individuals whose version info does not show Win8, but still have problems with N++ shell extension crashes. Moreover I tried to run my N++ on Win10&11 in that Win8 compatibility mode but so far so good.

Well, unfortunately, I’m not using Win11 for the forseeable future, and can’t test against that version.

Only one other thing I can think of, and I think this happened to me quite awhile ago, I had erroneously had both Win32 and Win64 Standard versions of Notepad++ installed under my Win 8.1 and then later Win10. I stopped allowing the updater to Update my version of NPP until I could figure out why it kept trying to upgrade me to the 64bit version (now I/we know). @PeterJones had pointed out to me that’s wasn’t advisable. After a thorough uninstalling and cleaning of the Regex, only then did those problems go away.

I wasn’t as involved in the community before then, so I can’t give more accurate troubleshooting, except to say that NppShell.dll message hasn’t come up since then, other than when having an outdated incompatible plugin installed, but that check and notfication that was put in checking against plugins stopped that happening again.

Only one other possible, that I can think of is memory corruption. It is coincidence that about the same time I was doing that I was also upgrading this 8 year old laptop with an SSD and complete memory fill. A lot of problems from then on, stopped so it’s possible that a bad memory chip could have been the cause of the intermittent issues I was having prior, and may also explain these ones as well. Just more thoughts. :-)

@Rob-DF

Try to disable the DirectWrite mode (uncheck N++ menu Settings > Preferences… > MISC. > “Use DirectWrite” checkbox).

@N8-Holt said in Is there a Hot key combo for "Clear all Bookmarks":

It would be convenient for me as I step through a sizeable source code file, setting bookmarks along the way, to be able to optionally set a bookmark when I find a key point in the program but quickly (hot key) be able to first clear all of the trailing bookmarks accumulated up to that point in time.

One of the things about this that’s giving me pause is that bookmarks are semi-persistent. They are stored in the session.xml file. As long as you keep a file or tab open in Notepad++ then the editor will remember the bookmarks when you close or exit Notepad++ and restart it. However, if you close a tab and then immediately re-open it using the recently closed file list then all of the bookmarks for that file are gone.

That said, I’m wondering what you mean by “trailing bookmarks accumulated up to that point in time.” Let’s say you start Notepad++ and see that there are already five bookmarks in a file. You add three more. Would you expect this “clear” function to remove the three you added in this session or would you expect it to clear all eight bookmarks, or do you want to clear some other subset of the bookmarks?

The thing @Terry-R suggested is to add a keyboard shortcut to the Search / Bookmark / Clear all bookmarks function. You may want to start out by first getting used to holding the Alt key down and then tapping the letters S B C followed by Enter. That will navigate to and use Notepad++'s Clear all bookmarks function if that is the thing you are seeking.

If you are not seeking to clear all bookmarks then the answer is “no” to the original question but please provide more information as it may well be possible to work out a way to define and clear a subset of the bookmarks.

@mkupper said :

Which also gets the topic of this thread back onto Notepad++

It never left.