Possibility to reload the grepify profiles from within the application, without the need to restart the application.

The goal will be to implemented a lexical analyser and appropriate grammars to support most of the common akin to OpenGrok.

OpenGrok (https://github.com/OpenGrok/OpenGrok) uses JFlex (http://www.jflex.de/).

This will be one big bit of effort here so will need some upfront thought.

Changing the code path works, previous paths are not populated in the drop-down box.

The highlighting in code views is not always applied when opening a window. There doesn't appear to be an obvious difference between which files get highlighted and which don't.

Selecting text in code for searching would (in all but the most obscure cases) be done with the intent of performing a literal search.

The prompt asking about a literal search should therefore not be displayed and the appropriate escaping and searching be done.

It would be good to be able to open the code files into an external (user defined?) editor.

For example Notepad++

So that one can benefit from already present highlight mechanism or other goodies.

Gabriel

Sometimes one is provided with code on a VM where the code sits on a disk of its own. Browsing from root dirs would be useful in this case.

Perhaps present a warning but allow the user to continue if they understand the consequences.

From: Richard T

Friendly names for Grepify regexps (e.g. in my hardcoded credentials profile I have complicated regexps for finding static keys, it would be nice if the GUI just showed something like "static key" instead of the full horror of the regexp)

Feature request from Daniel Martin - Load notes button. Maybe a model splash screen with: restore workspace vs. clean slate

Currently closing the current tab will return you to viewing the left most tab. Ideally the user should be returned to the tab last viewed.

from RIchard T

From: Richard T

It would be nice to be able to mark search hits in some way to indicate that they've been looked at, maybe allow them to be set to a different colour?

Feature request from Daniel Martin - Select a word in code view and highlight all instances in the file

Currently we have the ability to send the filename, however we may want more granular send to options...

Is currently a bland placeholder file

Currently there is an automatic detection for the encoding of the text file.
The algorithm assumes that there is some BOM header part at the beginning of the file, which is rarely the case in my experience.

It would be good to allow the user to set the encoding himself/herself for the session, as it is unlikely that this property will change within the project.

Defaulting to UTF-8 is probably better than the local ANSI page (as it is currently), because many systems/application are using UTF-8 by default now, and UTF-8 is backward compatible with ASCII.

The current grepify comments regexs will exclude #define statements.

Suggested fix is to replace

^\s*#
with

^\s*#(?!define)

Closing a form in its Load method can cause an exception to be thrown. As the first method called by a form is its Load method the preferred time to decide whether to display the form or not is when the form is being created in other code.

Suggested fix is to remove the dialog box showing the error message about not being a Grepify scan and ensure that the new bool parameter is used when creating search forms.

I do close the note window quite often because I am using it on a small screen (VM), and it gets in the way.

Highlighting the match in the search results window would allow easier spotting of false positives.

E.g. Searching for "ssh" will hit on "IsShutdownInProgress". Highlighting will allow quicker recognition of what was found.

As per the wiki this is also vulnerable to format string:

NSRunAlertPanel

From: Richard T

other metadata for Grepify regexps (e.g. an explanation for why a reviewer should care about this, you suggested before this could maybe be a tooltip?)

Non-regex searches are case sensitive, regardless of the option's setting.

Hello
I downloaded a folder that had some php files to my computer by using a perl script. This application cannot search inside those files. I have checked file permission to make sure my user and admin have full control; also I ran NCC code navi with admin permission but I got no result (it can show the PHP codes if I browse to those file in NCC code navi app).
However, if I download a zip file by my browser and extract it, it works fine and it can search inside the files.
Unfortunately I cannot give you more details about the files and I don't know if you can replicate this issue or not. I guess it is related to files attribute but I am not sure.
I am using Windows 7 64b with NTFS.

Thanks

If you do a search for say strcpy( from within the code viewer it needs to be escaped.

Searching for an invalid regex e.g. "Encrypt(" will cause the search results windows to display "Search running...." until the end of time.

Can you include build instructions? I tried building on VS 2012 Pro and it fails with the following errors:

1>------ Build started: Project: Win.CodeNavi, Configuration: Debug x86 ------
1>c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "LineNumbersControlForRichTextBox". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "ScintillaNET". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmCodeViewNew.cs(22,7,22,19): error CS0246: The type or namespace name 'ScintillaNET' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmBrowser.cs(20,7,20,19): error CS0246: The type or namespace name 'ScintillaNET' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmMain.cs(25,7,25,19): error CS0246: The type or namespace name 'ScintillaNET' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\IniLexer.cs(31,7,31,19): error CS0246: The type or namespace name 'ScintillaNET' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmCodeViewNew.cs(64,59,64,79): error CS0246: The type or namespace name 'StyleNeededEventArgs' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmCodeViewNew.cs(71,16,71,25): error CS0246: The type or namespace name 'Scintilla' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmCodeViewNew.cs(88,27,88,36): error CS0118: 'Win.CodeNavi.frmCodeViewNew.Scintilla' is a 'property' but is used like a 'type'
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmCodeViewNew.Designer.cs(275,17,275,29): error CS0246: The type or namespace name 'ScintillaNET' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmBrowser.Designer.cs(214,17,214,29): error CS0246: The type or namespace name 'ScintillaNET' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\frmCodeView.Designer.cs(256,17,256,49): error CS0246: The type or namespace name 'LineNumbersControlForRichTextBox' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\IniLexer.cs(62,17,62,26): error CS0246: The type or namespace name 'Scintilla' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\IniLexer.cs(73,33,73,42): error CS0246: The type or namespace name 'Scintilla' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\IniLexer.cs(190,40,190,49): error CS0246: The type or namespace name 'Scintilla' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\IniLexer.cs(190,61,190,66): error CS0246: The type or namespace name 'Range' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\IniLexer.cs(225,26,225,35): error CS0246: The type or namespace name 'Scintilla' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\SourceCodeMarkUp.cs(123,74,123,106): error CS0246: The type or namespace name 'LineNumbersControlForRichTextBox' could not be found (are you missing a using directive or an assembly reference?)
1>D:\tools\ncccodenavi\Win.CodeNavi\Win.CodeNavi\SourceCodeMarkUp.cs(175,73,175,105): error CS0246: The type or namespace name 'LineNumbersControlForRichTextBox' could not be found (are you missing a using directive or an assembly reference?)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

A configurable amount of context would be useful in the search results. Similar to the -A and -B flags in grep.

Similar to the ability to tag lines. When I'm done with a big subset of entries I'd like to be able to remove them from the view

It gives the following error when I double click on files that have no extension:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string.
Parameter name: startIndex
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at Win.CodeNavi.frmCodeViewNew.frmCodeViewNew_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

Win.CodeNavi
Assembly Version: 1.2.0.0
Win32 Version: 1.2.0.0

CodeBase: file:///C:/CodeNavi/Win.CodeNavi.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll

ScintillaNET
Assembly Version: 2.5.2.0
Win32 Version: 2.5.2.0

CodeBase: file:///C:/CodeNavi/ScintillaNET.DLL

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

There will be a common plug-in architecture which will be able to extend up to four parts of the application:

• New plugin tool bar element
• Code view right-click context menu
• File browser right-click context menu
• Search results right-click content menu

Make the note window independent, so that one can place it at the bottom, instead of on the side.

Again, because I am using it on a small screen.

Possibility to create grepify profiles "on-the-fly" / in memory.

Gabriel

Revisit this functionality to add extra highlighting...

A fuzzy approach to resolving C++ function / class definitions. Will exist on the code view right-click context menu. Will be implemented using the new plug-in framework.

A fuzzy approach to resolving C function definitions. Will exist on the code view right-click context menu. Will be implemented using the new plug-in framework.

Been faced with Ruby code reviews lately and would like to use Code Navi.

After running a Grepify against one of the lists (e.g. Java) and spending a few hours walking your way through the items tagging stuff as "Done" it would be good if you could save that status, close CodeNavi and pick it up in the morning where you left of.

Currently if you right-click / press enter on an element of code to perform a search and regex searching is enabled and it contained a ( or similar then it is not escaped e.g. ( , leading to no results being found.

From: Richard T

Ability to close tabs in the main view (it can otherwise quickly get cluttered once a few source files have been opened)

Currently navigating between bookmarks will position the relevant line at the bottom or top of the view i.e. as soon as the line comes into view from the current position.

To get better context of the code, bookmarks should be centred in the view. i.e. the bookmark should be on the middle line.

If the path is too deep, the file name is truncated out of the window title. It is useful to quickly be able to see the file name you are working with.

Maybe smart truncation like the one in the browser's status bar (i.e. add some dots in the middle of the path) could be added.

Alternatively the file name could be presented in the right-hand side of the toolbar where all the rounded icons are so it's never out of sight.