@Keith-Neemann

Which version do you use?

Cheers
Claudia

@Gilberto-SC

you can use procmon in order to find out which dll gets loaded, from where and when.
Run procmon, define a filter for npp and then start npp.
It needs a bit of training but if you are really interested in finding out what does what
check out the sysinternals tools as well as everything Mark Russinovich has posted/blogged.

Once you are at the level to understand how process, threads, libraries, drivers … work together
download hxd and start investigating memory.

Other useful tools can be found at nirsoft.

Cheers
Claudia

@Alex-Woolf,

As @Claudia-Frank said, “Same applies to UDL”, and she said earlier that the custom syntax highlighting settings, which are known UDLs (User Defined Languages: Language > Define Your Language) are stored in userDefineLang.xml. You could either copy that single file to the new PC, or you could use the UDL window’s interface:

Original PC: Language > Define Your Language Use the pulldown to select the User Language: ____ you want to transfer, and click the Export... button Copy that file on the new PC New PC: Language > Define Your Language: click the Import... button, and select that file Repeat for every UDL (syntax highlighting definition) that you want to transfer.

If you’ve got more than one, it’s probably simplest to just copy the whole file, but if you only have one, or you don’t want to duplicate them all, you can do it using the UDL window.

BTW: Since it wasn’t mentioned, those files are by default in %AppData%\Notepad++\, though if you’ve got a portable version of NPP, or if you chose to not use %AppData% when installing, they will be in the same folder as your notepad++.exe.

@Deny-Parkinson Hi. Some months ago I found that bug to. I download latest version NP++ and bug is out. You have Windows7x64?

@mkupper: Thanks for taking the time to write up this guide. It seems to cover all my requirements and then some. I am definitely going to give that a go.

As for Alt-F4, I dislike having to kill a program to make it do what I want, but I should get over that here.

Too bad sessions don’t have assigned file extensions. It would be easier to just double click on a session and having NPP open all the files for you.

But, the title of this thread has “feature request?” in it. Maybe a workflow like yours will make it to a plugin or an extension to NPP. That would be very nice!

@Scott-Sumner is correct and mapping alt-backspace to a different function prevents the BEEP. Probably NPP capture it and fully handle it before it reaches the BEEPING control.

I got curious enough to actually open the code. This exist in NPP shortcut table:
{TEXT("SCI_UNDO"), SCI_UNDO, true, false, false, VK_Z, IDM_EDIT_UNDO},
{TEXT(""), SCI_UNDO, false, true, false, VK_BACK, 0},

Initially I thought that maybe NPP is at fault after all because ctrl-z has IDM_EDIT_UNDO which is missing from alt-backspace.
But after commenting out the alt-backspace line and compiling I had a version of NPP where alt-backspace no longer UNDO but still BEEPS.
Since ALT-xxx shortcuts are often associated with menus I guess that this is the beeping component.

Hello all,

FYI, I tried disabling the Scintilla buffering and worked with N++ some time this way. In some occasions I observed flickering in the Sci view that was not present with buffering enabled. So it appears the buffering is actually necessary.
Thanks.

BR

@Carlos-Eduardo-Guerra-Silva

see here.

Cheers
Claudia

@Alan-Kilborn You could always include this (see http://patorjk.com/software/taag/#p=display&h=1&f=Small&t=Never change this!):

_ _ _ _ _ _ _ | \| | ___ __ __ ___ _ _ __ | |_ __ _ _ _ __ _ ___ | |_ | |_ (_) ___| | | .` |/ -_)\ V // -_)| '_| / _|| ' \ / _` || ' \ / _` |/ -_) | _|| ' \ | |(_-<|_| |_|\_|\___| \_/ \___||_| \__||_||_|\__,_||_||_|\__, |\___| \__||_||_||_|/__/(_) |___/

:-)

For something with a name that begins “Really Simple,” the implementations are terrible, IMO. But I think I’ve found a project to help me create something useful while learning how to use this editor.