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

could you make -c for config directory! #9

Open
blackcodersec opened this issue Apr 10, 2024 · 10 comments
Open

could you make -c for config directory! #9

blackcodersec opened this issue Apr 10, 2024 · 10 comments

Comments

@blackcodersec
Copy link

could you make -c for config directory!

@blackcodersec
Copy link
Author

image

how can I filter this type of garbage urls?

@xnl-h4ck3r
Copy link
Owner

could you make -c for config directory!

Hi @blackcodersec. Thanks for taking the time to raise an issue. Just wondering why you need that? Do you need different config files for different things?

@xnl-h4ck3r
Copy link
Owner

image

how can I filter this type of garbage urls?

I haven't got chance to look at this properly yet, but I will get to it and give you a proper reply soon

@blackcodersec
Copy link
Author

ok thanks

@xnl-h4ck3r
Copy link
Owner

image

how can I filter this type of garbage urls?

From the information I can see, all those urls that look similar apart from a differeing parameter value should have been condensed to one line. Is that screenshot from the output of urless?

@blackcodersec
Copy link
Author

yes that output is from urless and check this new screenshot I filter .js extension, but I think not working -fe.

image

@xnl-h4ck3r
Copy link
Owner

Hi @blackcodersec. From the screenshot you posted, it looks like you've started the -fe value with a double quote, and then tried closing with a single quote. The next double quote is at the end of the -fk value. So actually the -fe values doesn't have .js, it has .js' -fk 'bog as a value. If you use -v option you can double check the values you are using. Can you correct the quotes and let me know if you still have a problem? Thanks

@blackcodersec
Copy link
Author

ohh sorry sorry, I didn't see I close with a single quote.
Now ok, its working fine.

@xnl-h4ck3r
Copy link
Owner

could you make -c for config directory!

Hi @blackcodersec. I was going to close this, but realised I hadn't addressed the initial issue! I was ust wondering why you need have an option -c to provide a config directory? Do you need different config files for different things? Is there an issue with the default that other programs use too, e.g. ~/.config/TOOLNAME?

@blackcodersec
Copy link
Author

I want to use config file from different directory. That's why I made this issue.

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

2 participants