-
Notifications
You must be signed in to change notification settings - Fork 15
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
lsfuncs.fish: Prints list of user-defined Fish functions, brews and other local scripts in users $HOME #2
Comments
|
This is pretty cool, thanks for sharing! |
I've explored your functions a bit more and saw you had already implemented some related functions ( Currently I don't have a systematic way of organizing my TODOs, notes, project repos, and bookmarks to content I've researched (In particular I want full-text search across all my web bookmarks via a private-cloud or local indexer & db). I've been researching various approaches like yours and twas interested to try out your time and task tracking tools -
|
If you're on a Mac, you might want to check out
[Hook](https://hookproductivity.com/) for linking all of your notes,
bookmarks, images, etc. to a project. I even wrote [a
CLI](https://discourse.hookproductivity.com/t/a-hook-cli-for-terminal-goodness/1678)
for it.
…-Brett
On 18 Mar 2022, at 18:46, Mac Cowell wrote:
I've explored your functions a bit more and saw you had already
implemented some related functions (`describe_functions.fish`) so I'm
glad you like it.
Currently I don't have a systematic way of organizing my TODOs, notes,
project repos, and bookmarks to content I've researched (In particular
I want full-text search across all my web bookmarks via a
private-cloud or local indexer & db).
I've been researching various approaches like yours and twas
interested to try out your time and task tracking tools -`doing.fish`,
`na`, etc. The directory-based scoping of how `doing` resolves which
`taskpaper` to target is a cool idea - as is the distributed flat-file
architecture of potentially having these `taskpaper` or `md` project
files scattered around.
`doing` does a fine job at creating todos for projects and helping
track time spent on them. I'm trying to settle on a similar
systematic process and documentation/serialization format for
organizing my `markdown notes`, `bookmarks`, + `markdown + image
snapshots` of bookmarks, and a way of relating them by association to
a project, repo, and/or tags. I am playing around w obsidian md right
now but it's just part of the puzzle.
--
Reply to this email directly or view it on GitHub:
#2 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Hi @ttscoff, I just came across your work earlier today and have been impressed and intrigued with the collection of productivity and info-management tools you've made and shared.
I'm also a
fish
user and was interested to read your blog posts about useful fish funcs and other tools. Thanks for generously sharing your collection of scripts in All my Fish functions! It inspired me to (try) to share one of my ow scripts that you and other may find useful.lsfuncs.fish
is inspired by and complimentary toapropos
. I found myself with an increasing library of either self-written or at least manually-curated scripts, packages, tools, and other executables for a variety of specific of obscure tasks and experiments. I had a hard time remembering what I had named many of the fish functions. I wanted to$ apropos keyword
and have a good shot of rediscovering that script from several years ago I knew was around somewhere. My unix-fu was insufficient to the task to expanding apropos' reach (feeding its dbs new entries - which I believe some dark and ancient process generates from man files... at least historically, on osx)... so I took a shot at a fish script.lsfuncs
searches predefined user directories for.fish
functions, collects--description
strings if available, and then presents a list of the results in a nice table in the terminal. It does the same for the user's installed homebrewbrews
andkegs
and also for other polyglot executable scripts and binaries that the user may have stashed someplace like~/dev/bin/
.Check out the
lsfuncs
if it sounds useful, and also please let me know if you have experienced similar friction points and have your own solutions, I'd be interested to learn about them.If you'd like to add
lsfuncs
to your repo, it would motivate me to organize and publish some more of my scripts in a proper public repo like yours, so just let me know and I'll send you a PR.Cheers, and thanks for sharing your work! Mac
https://gist.github.com/100ideas/b27e44a5c07360917ce99cd6997e2b7b
The text was updated successfully, but these errors were encountered: