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

Make it aware of lowercase readme by default #134

Closed
StreetStrider opened this issue Jan 12, 2020 · 6 comments
Closed

Make it aware of lowercase readme by default #134

StreetStrider opened this issue Jan 12, 2020 · 6 comments
Labels
enhancement New feature or request

Comments

@StreetStrider
Copy link

Make runner aware of readme.md as well. Some people prefer all files to be lowercased, including readme. Now it's required to pass such name explicitly, wasting time.

@muesli muesli added the enhancement New feature or request label Jan 12, 2020
@muesli
Copy link
Contributor

muesli commented Jan 12, 2020

Good point, I'll make the search list case-insensitive.

@muesli
Copy link
Contributor

muesli commented Jan 13, 2020

Fixed by c5517ad.

@muesli muesli closed this as completed Jan 13, 2020
@StreetStrider
Copy link
Author

Thank you for your efforts.

@StreetStrider
Copy link
Author

Hello. This isn't working in v1.1.0. I see some intro page when running without arguments.
Was this feature dropped or it's just a flaw?
Also, the intro page doesn't mention local readme file if it is lowercased.

@muesli
Copy link
Contributor

muesli commented Nov 12, 2020

Starting Glow v1+ without any arguments will launch a TUI mode which should list all markdown files it can find in the current working dir (and below). Is this not working for you?

@StreetStrider
Copy link
Author

I understand. I've been using it when it opens readme by default. So this behavor has been changed with major release, OK.

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

Successfully merging a pull request may close this issue.

2 participants