Recursive custom-dir
See original GitHub issueHi,
I would like to classify my md files in directories like:
~/eg
~/eg/glossary
~/eg/tech
and in my config file, just having something like:
custom-dir=~/eg
Actually, when a md file is in a subdirectory, it is not found. Is there a way to change that ?
Thanks.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
recursive-clients, what value ? - Google Groups
Hello,. I'm working on bind 9.2 on linux mandrake and I had lots of logs containing : Jun 14 09:23:30 hostname named[1045]: client:...
Read more >Recursive Client Rate Limiting - FAQ - ISC Knowledgebase
Recursive Client Rate limiting provides new tuning controls intended to optimize recursive server behavior in favor of good client queries, ...
Read more >Recursive Labs Visual Engagement Tools - Cobrowse, Video ...
Recursive Labs offers next generation customer engagement software in the form of secure no-download cobrowse, screenshare, video chat, & mobile cam CRM ...
Read more >What is recursive DNS? - Cloudflare
A recursive DNS lookup is where one DNS server communicates with several other DNS servers to hunt down an IP address and return...
Read more >Recursion
Reengineering drug discovery through digital biology. We are discovering transformative new treatments by combining automation, machine learning, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm that is a good idea. I don’t think there’s any way to do that currently… I need to revisit how we resolve paths.
If there isn’t a config file fix I will add it.
Your preferred way for it to work would be to just detect
.md
files anywhere in the directory tree?A few complicating cases occur to me that I’ll need to think through. Currently if you have
~/eg/find.md
, runningeg find
will show the contents of your custom file before the contents of thefind
file that ships witheg
. If multiple files with the same name are defined in your custom directory, eg something like:what behavior would you expect? Showing contents of both files and then the default
ssh
examples?Great. I have at least one more edge case to fix, at which point I will create a PR, merge, and close. I try to do releases on the 5th of each month, so I’ll ship a new version around April 5th.
This was a great idea, thanks for the suggestion. Some tools and combinations of flags I want to use only at work, and I hadn’t found a good way to put them in
eg
without running the risk of leaking them in my dotfiles repo. Nested directories is a great workaround.For this reason I decided to show all files if you have more than one. So if you have:
eg find
will concatenate all three together, showing first the one inpersonal-machine/
, then the one inwork-machine/
, and then the default examples that ship witheg
.