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

Search on extension #160

Open
quasarea opened this issue Oct 9, 2017 · 6 comments
Open

Search on extension #160

quasarea opened this issue Oct 9, 2017 · 6 comments

Comments

@quasarea
Copy link

quasarea commented Oct 9, 2017

Maybe it would be possible to introduce similar to fn parameter for extension, like:
fe - File extension. E.G. fe:cs

I'm fighting with unknown types and it would be great to be able to determine scope of each

@boyter
Copy link
Owner

boyter commented Oct 9, 2017

Certainly it is possible.

So one of the issues with this is that the number of extensions grows as a massive rate. I implemented this on searchcode.com and you run into the situation of what to do with things like Dockerfiles which have no extension. Do you treat the whole thing as an extension?

What about files with multiple periods in them, for example typings.d.ts

Its something I am looking at doing. What might work better though is that if #158 was implemented and if you could easily see what files are categorised as "Unknown" and easily add them to be classified correctly.

@quasarea
Copy link
Author

quasarea commented Oct 10, 2017 via email

@boyter
Copy link
Owner

boyter commented Oct 10, 2017

Actually the reversed filename is a dammed good idea.

@boyter
Copy link
Owner

boyter commented Oct 10, 2017

Give that a go. In master.

screen shot 2017-10-10 at 5 06 37 pm

@quasarea
Copy link
Author

reindexing...
still I would rather see it like something complementary to fn: functionality
surely working only in filename scope rather then on whole code,
maybe highlighting reverse results in some way, so you actually that it met reverse condition.
maybe even merging results from both searches, together under certain condition.

if asterisk is in the middle, you know prefix and postfix already, so such search is not needed,
but it its at the end, it means you don't know one of those. so you could merger results for both

  • filename* would produce results for filename.test and test.filename

I will play a bit with this as I may talk nonsense

@boyter
Copy link
Owner

boyter commented Oct 10, 2017

Agreed but I would need a solution to the above. Its something that if I can get a good solution to I will implement.

@boyter boyter added this to ToDo in Release 1.3.12 Oct 29, 2017
@boyter boyter added this to TODO in Release 1.3.13 Feb 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants