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

Glow doesn't see markdown files. .gitignore #553

Open
4l1fe opened this issue Jan 7, 2024 · 3 comments
Open

Glow doesn't see markdown files. .gitignore #553

4l1fe opened this issue Jan 7, 2024 · 3 comments

Comments

@4l1fe
Copy link

4l1fe commented Jan 7, 2024

Describe the bug
Trying to browse files recursivelly in a directory

❯ tree .local
.local
├── README.md
└── tasks
    ├── 1.md
    └── 2.md

❯ glow -al .local

I don't know why but recently flag -a allowed me to browse the files with the same command and same directory.

If i make the folder normal, unhidden .local -> local glow works as expected.

Setup
Please complete the following information along with version numbers, if applicable.

  • Ubuntu 22.04
  • zsh 5.8.1
  • alacritty 0.9.0
  • tmux 3.2a
  • Locale en_US.UTF-8
  • glow 1.5.1 (ad21129)

To Reproduce

  1. Open files with the command glow -al .local

Expected behavior
To browse files.

Screenshots
See nothing
image

@4l1fe
Copy link
Author

4l1fe commented Jan 9, 2024

Found Reason

I figured out that glow binary behaves as described when a folder is named either .local or local. All the other derivatives can be seen, for example ..local is seen.

@4l1fe
Copy link
Author

4l1fe commented Jan 9, 2024

Problem Found

Such a misbehavior! glow simply ignores files and dirs which are in .gitignore! That not even confusing, but irritating haha.

I didn't find any mention about the hidden setting.

@4l1fe 4l1fe changed the title Glow doesn't see markdown files Glow doesn't see markdown files. .gitignore Jan 9, 2024
@jjspace
Copy link

jjspace commented Feb 2, 2024

This is related to #285. I also find this incredibly annoying and came looking for a similar solution. I don't think this should be the default behavior but even if it is there should be a way to bypass that.

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