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

Improving search results #5174

Closed
davidwindell opened this issue May 23, 2017 · 6 comments
Closed

Improving search results #5174

davidwindell opened this issue May 23, 2017 · 6 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template. sprint/current
Milestone

Comments

@davidwindell
Copy link
Contributor

One of the main things we are missing coming from using a desktop IDE (Netbeans in my case) is a search feature that shows line numbers and links to the result in the file.

Please refer to the screenshot below:

screenshot from 2017-05-23 14-05-52

The key features are;

  • Column AND line numbers are shown for matches
  • Multiple matches in the same file are shown individually
  • When you click on a search result, the editor loads the file AND jumps straight to the matching line with all instances of the search term already highlighted

Most of the work I do relies heavily on the ability to quickly find basic strings across a very large project and at the moment I can't work in Che on the project because of this limitation.

Thanks!

@vparfonov vparfonov added kind/enhancement A feature request - must adhere to the feature request template. sprint/next team/ide labels May 23, 2017
@davidwindell
Copy link
Contributor Author

@TylerJewell does closing this issue mean it won't be considered in the epic or..?

@TylerJewell
Copy link

@davidwindell - I am just bulk closing a lot of older issues right now that are kind/enhancement and then allowing dev teams or other contributors to re-open them if they have a reasonable confidence it will be implemented in the upcoming 6 months or so. We have a large backlog of enhancement requests and trying to sort out which ones are more wishes that we cannot likely ever get to vs. those that are part of an upcoming dev plan. The backlog had 600 issues opened at start of the day and it's too big to properly manage, so trimming shears are out!

@davidwindell
Copy link
Contributor Author

@TylerJewell I got pinged on a couple of these. Thanks for the reasoning, I guess I just wanted to check that the "epics" you are leaving open that refer back to my feature requests/issues (you've now closed) will still be considered? Like this one for example.

@TylerJewell
Copy link

Yeah, the epics are all still valid and all intentions are that dev teams will be assigned to them over the coming year.

@vparfonov vparfonov reopened this Jul 6, 2017
@vparfonov
Copy link
Contributor

We will work on it soon here https://github.com/eclipse/che/tree/searchwithpossitions

@davidwindell
Copy link
Contributor Author

That's awesome news! Ping @broopdias

@vparfonov vparfonov self-assigned this Jul 24, 2017
@vparfonov vparfonov added status/in-progress This issue has been taken by an engineer and is under active development. and removed sprint/next labels Jul 24, 2017
@vparfonov vparfonov added this to the 5.17.0 milestone Aug 17, 2017
@vparfonov vparfonov removed the status/in-progress This issue has been taken by an engineer and is under active development. label Aug 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. sprint/current
Projects
None yet
Development

No branches or pull requests

3 participants