Hello @Leszek-Dedko,

yes, can be done by disabling backup functionality.

Settings->Preferences->Backup
uncheck Enable session snapshot and periodic backup

Cheers
Claudia

Thanks Claudia, that seems to have cured it :-)

This also worked but if we have millions of rows then its better we use

Search > Replace >

In dialog box ’ Find what ': \n
Replace with : Blank

And Replace All

Changing the old ugly interface:
http://docs.notepad-plus-plus.org/index.php/Toolbar_Customisation

With the simplification it worked fine :)

Thank you so much Claudia.

Hello @Vaidas-SS,

when you are saying real time you mean that you get these informations while typing html code, correct?
If so, no, npp doesn’t have a html debugger.
From plugin point of view there is a html preview which might be helpful
and the xml tools could be also used to detect missing tags.

What you could also do is using online validators together with npp and
Run function or nppExec.

Cheers
Claudia

Hello @Adam-Kley,

I described here a way to make it happen.

Cheers
Claudia

It seems the content of your clipboard is a type which can not pasted into NP++. e.G. a picture.
Try to paste it into Word or Writer and you will see the clipboards content.

Hello @Steven-N-Senart

put the cursor before the number to search and press CTRL+F3.
The next number gets selected and you can delete it. Press F3 for next find.

Cheers
Claudia

Hello @Max-Mustermann,

Excel is responsible what goes to the clipboard and npp gets it from
the clipboard.

What you can do, if the double quote is unique, to record a macro to
find and replace double quote with nothing once and rerun it whenever you need it.

Cheers
Claudia

Thank you @Claudia-Frank ! I think the code you point to is indeed where the problem occurs.

I am not sure about the intricacies of NpptoR, but the plugin manages to take lines, selections and scripts in N++, and pastes and/or executes them in the R console window (so not in the N++ window like nppExec does). I’d like to learn how to apply nppExec for R, but it would probably be best to leave that for another time :)

The issue is mentioned here at SourceForge and here at Github but the bit of code you refer to does not seem to be identified there, so thanks a lot for bringing it up.

I hope it will come to the attention of the NpptoR developers, unless the N++ developers revert this part of the code as you suggest elsewhere.

@Ivan-Aleksandrov

Keep in mind, when comparing font/encoding with different programs,
make sure they use the same font/encoding.

Cheers
Claudia