Notepad++ 7.7 Release

Marek Jindra

I am having an issue with typing some Czech accented characters in ANSI encoding.

If I open an ANSI file, I cannot type all characters on my keyboard (“ěčřůďťň ĚČŘŮĎŤŇ” appears as “ecrudtn ECRUDTN”).

If I open an ANSI file which contains them, it shows fine, but I cannot write any more of those accented letters.

On my Czech Windows system, ANSI encoding should be equal to Windows-1250 encoding.

If I first convert the file to UTF-8, it works better. However I need to save the file as Windows-1250, not UTF-8.

Meta Chuh

please have a look at this similar ansi issue for 7.7:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/5671

for testing purposes, please replace your SciLexer.dll with one from here:
https://notepad-plus-plus.org/temp/
(rename the 32 or 64 bit version you need to SciLexer.dll)

after that, either post your experiences at the issue mentioned above, or create a new topic at general discussion here at the community.

best regards.

Marek Jindra

@Meta-Chuh After replacing the SciLexer.dll with the one you provided (SciLexer32.signed.dll 27-May-2019 22:00), everything works fine. The issue is gone.

Jonas Andersson

I find 7.7 slower than 7.6.x with large files that have very long lines. I know this is a known issue in Scintilla but is it possible v4.14 made things even worse?

Squuiid

Dead link on all downloads it would seem.

Error 503 Backend fetch failed
Backend fetch failed
Guru Meditation:
XID: 214832709
Varnish cache server

prsy

@Squuiid Same here

John Sewell

All download links for 64-bit and 32-bit fail:
Error 503 Backend fetch failed

Backend fetch failed

Guru Meditation:

XID: 233345863

Varnish cache server

neyte 08

moi aussi

Monster smith

Whenever I try to download notepad++ any version I am prompted with

Error 503 Backend fetch failed
Backend fetch failed

Guru Meditation:
XID: 229971568

Varnish cache server

can anyone help out?

Anas Ahmed Elgarhy

I can not download the program 😢
link text

nblookup

A problem, click File->Save, save as type: normal text file,
saved files do not automatically add suffix txt

Meta Chuh

welcome to the notepad++ community, @nblookup

this is by design, to have full extension control at any given time.

if you prefer the old behaviour, please go to settings > preferences > default directory and disable use new style dialog.

many thanks and best regards.

makiimai

I couldn’t find answer if I can run c in off-line environment, please remove me from community here. Thank you very much.

PeterJones

@makiimai said:

I couldn’t find answer if I can run c in off-line environment

You could have tried asking in Help Wanted, we would have asked for clarification, and then probably would have eventually helped you find a way to run the c compiler from Notepad++

please remove me from community here.

If that’s what you desire, you can go to your own profile, click Edit, and click Delete Account.

Alan Kilborn

@Leandro-Lopez

Dude, why are you posting a question about a plugin in a release announcement thread? Please try the Help Wanted section.

andrecool-68

@Leandro-Lopez you got the wrong address))
https://github.com/pnedev/compare-plugin/issues

donho

@Leandro-Lopez
https://notepad-plus-plus.org/community/category/5/plugin-development

@chasegnil
https://notepad-plus-plus.org/community/category/8/boycott-notepad

Faceless YouTuber

There is an issue in this release with some hidden characters being added when editing and saving PowerShell scripts. So when you launch a PowerShell script that has been edited with NPP, you get lots of weird syntax errors although the code is all fine. If you edit the same block of code in PowerShell ISE or Notepad, PowerShell won’t throw any errors when launched. It’s easy to reproduce. Copy the function below (function extracted from https://github.com/microsoftgraph/powershell-intune-samples/blob/master/RBAC/RBAC_ScopeTags_DeviceAssign.ps1) and save it in NPP, you will get weird syntax errors running it in PowerShell although there are none. Do the same with either Notepad or the PowerShell ISE and no errors appear when you execute this same code in PowerShell.

###########BEGINNING OF CODE BELOW#################

Function Update-ManagedDevices()
{
<#
.SYNOPSIS
This function is used to add a device compliance policy using the Graph API REST interface
.DESCRIPTION
The function connects to the Graph API Interface and adds a device compliance policy
.EXAMPLE
Update-ManagedDevices -JSON $JSON
Adds an Android device compliance policy in Intune
.NOTES
NAME: Update-ManagedDevices
#>

[cmdletbinding()]

param(
	$id,
	$ScopeTags
)

$graphApiVersion = "beta"
$Resource = "deviceManagement/managedDevices('$id')"

try {
	If ($ScopeTags -eq "" -or $ScopeTags -eq $null)
		{
			
		$JSON = @"
				{
				"roleScopeTagIds": []
				}

"@

		}
	Else
		{
		$object = New-Object –TypeName PSObject
		$object | Add-Member -MemberType NoteProperty -Name 'roleScopeTagIds' -Value @($ScopeTags)
		$JSON = $object | ConvertTo-Json
		}

	$uri = "https://graph.microsoft.com/$graphApiVersion/$($Resource)"
	Invoke-RestMethod -Uri $uri -Headers $authToken -Method Patch -Body $JSON -ContentType "application/json"

	Start-Sleep -Milliseconds 100
	}
catch {
	Write-Host
	$ex = $_.Exception
	$errorResponse = $ex.Response.GetResponseStream()
	$reader = New-Object System.IO.StreamReader($errorResponse)
	$reader.BaseStream.Position = 0
	$reader.DiscardBufferedData()
	$responseBody = $reader.ReadToEnd()
	Write-Host "Response content:`n$responseBody" -foregroundcolor "Red"
	Write-Error "Request to $Uri failed with HTTP Status $($ex.Response.StatusCode) $($ex.Response.StatusDescription)"
	write-host
	break
	}
}

###########END OF CODE ABOVE#################

Could you please look into this and resolve this issue please? I think it’s got something to do with the JSON "@ string terminator and I suspect NPP is actually adding some hidden character before this string terminator which PowerShell doesn’t like and consequently breaks the whole syntax of the script.

For instance, if you save this code with NPP, it won’t work in PowerShell. If you open this NPP saved file afterwards in Notepad, make no modification to it and save it, it will work just fine.

Thanks very much in advance for resolving this real nasty issue!

C

Faceless YouTuber

Sorry, I forgot to mention (I had to wait for 1200 seconds to add this…) that it is not an encoding issue as I checked and weither you save it in ANSI or UTF-8 it makes no difference in the behaviour.

Thanks once more for your help.

C

andrecool-68

@Faceless-YouTuber New message you can do immediately without waiting 1200 seconds