Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open File at Line doesn't always jump to the line #9041

Closed
jankrassnigg opened this issue Oct 21, 2020 · 5 comments
Closed

Open File at Line doesn't always jump to the line #9041

jankrassnigg opened this issue Oct 21, 2020 · 5 comments

Comments

@jankrassnigg
Copy link

Description of the Issue

When I use grepWin to open a text file at a specific line, Notepad++ won't always jump to the desired line. It will always open the correct file, but often it stays at the top of the file. However, if I open the file a second time from within grepWin, while np++ still has the file open, it will jump to the correct line.
If, however, I close the file in np++ before opening it again from grepWin, I will typically get the same incorrect behavior again.

Note that this doesn't happen always (but on my machine with a very high probability), so maybe it's a timing issue.

Steps to Reproduce the Issue

See description above. I used grepWin when I noticed the issue, but you can probably reproduce this in any way that opens a file at a specific line.

Expected Behavior

It should always jump to the specified line when opening a file.

Actual Behavior

It sometimes stays at the top of the file.

Debug Information

Notepad++ v7.8.8 (32-bit)
Build time : Jun 24 2020 - 00:15:36
Path : C:\Program Files (x86)\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS Name : Windows 10 Enterprise (64-bit)
OS Version : 2009
OS Build : 19042.572
Current ANSI codepage : 1252
Plugins : mimeTools.dll NppConverter.dll NppExport.dll NppFTP.dll

@Yaron10
Copy link

Yaron10 commented Oct 21, 2020

@jankrassnigg
Copy link
Author

Awesome! I'm surprised I wasn't on the latest version, I thought it had updated just a few days ago :-|

Thanks anyway!

@Yaron10
Copy link

Yaron10 commented Oct 21, 2020

You're welcome.

@ArkadiuszMichalski
Copy link
Contributor

ArkadiuszMichalski commented Oct 21, 2020

@Yaron10 this fix apply to #8007?

@Yaron10
Copy link

Yaron10 commented Oct 21, 2020

@ArkadiuszMichalski,

Yes, it should fix 8007.
Note: related #8679 is still valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants