@Ekopalypse many thanks, that indeed works and it basically removes it. saves a lot of time

See this old thread.

@Steven-Haymes

not exactly, you missed one duplicate line ;-)

@gurikbal-singh

it only works on consecutive lines, meaning
if you have something like

a a b b c c

you get

a b c

BUT if there are other lines in between like empty lines or different lines
then it doesn’t do anything. It basically checks always the previous line with the current line and if those are the same it will delete the current line.

The NppExec plugin did the trick! Just two simple lines were all I needed:
npp_menucommand Encoding\Convert to UTF-8
NPP_SAVEAS: c:\users\clay\downloads\people.csv

Yes, that is what I looking for.
Thanks.

@jhudis

there is a known issue open, maybe you suffering from the same.

https://notepad-plus-plus.org/community/topic/15739/faq-desk-request-for-help-without-sufficient-information-to-help-you

@Steven-Haymes said:

How about:

And I thought my response was making some assumptions. :-)

those were the docs for the auto-completion preferences; eventually, more details will be at http://notepad-plus-plus.github.io/npp-usermanual/content/auto-completion/ – or in an equivalent location at whatever the final URL for the new NPP documentation suite is.

@PeterJones said:

if the user tried a couple of single "replace"s to make sure it was working, and then hit “replace all”, and the behavior changed, that would be disturbing

Ha! I’m surprised that @guy038 hasn’t jumped in yet to talk about how exactly this sort of thing can and does happen!! :)

@PeterJones Many thanks – creating sub directory and moving .dll is the solution – all working now. :+)
Tortoise SVN plugin not available any longer via plugin manager but (as per Michael Vincent’s post ) available at http://www.incrediblejunior.com/npp_plugins/
Thanks

@Mon-Onkel said:

I still would like to know how to deal with (), ), and (

Whenever you are dealing with looking for the special characters in a regex (regular expression) you need to use a ‘delimiter’ to denote that it’s the literal character you want to search for, not the special meaning.

In Notepad++ we use \ as a delimiter. Thus \( means search for a literal ( (left curved bracket). If you wanted to search for () together as literals use \(\). There can be some exceptions but for clarity use \ for every special character. So even the \ is special so literally it is \\.

Terry

ok well, thanks anyways!

Even translated, what the OP minimally put forth, is unintelligible.

@Mon-Onkel

Another gotcha when posting here is that when you use * it gets turned into an italics font. See that? So the regular expression you posted makes no sense. It should be, AFAICT, (?s-i)Subject: Phonogram Digest.*?Reply-to: .*?\R

You can get the special text I just showed by wrapping it in backticks, also known as grave accents.

@lhackner
Maybe a movie session will be a little later)))

@Paul-van-'t-Hoff

Unfortunately, no you can’t.
Concerning udl docu, see here.

Perfect, thanks for the help, both of you. Appreciate it.

@Claudio-Gallego said:

I’ve found something : search : jpg.*ivia-rouge

That’s great if it works for you. But note that the regex as displayed does not work as advertised, because it is missing the underscores.

For future readers of this thread, the forum gobbled the _ characters from @Claudio-Gallego’s regex. For the regex to work with the quoted data, it must be search = jpg.*_ivia-rouge_.

To get it thru the forum without Markdown being applied to text, you need to enclose small pieces of exact text in back-ticks: `_ivia-rouge_` renders as _ivia-rouge_, instead of the italicized ivia-rouge that was seen without the proper Markdown. The PREVIEW window shows this. If you want to see more of the preview window at a time, hit the big black-circled ^ above the COMPOSE window.

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.