HN user
bronzecarnage
Wasn't satisfied with zotero and mendeley for pdf reference management. Wanted something terminal based and simple, so I wrote a shell script that I eventually rewrote in python. Given a pdf, it reads it, tries to find the article doi and fetches metadata from crossref to rename the file and store metadata in the file itself. I Plan on integrating features like interactive tagging and tag browsing from the terminal.
Any help with code review or additional features are welcome :)
This is ultimately due to the general problem of neovim internals being in so much flux. So much keeps changing, updating, and breaking in the internals and plugins. It does take some upkeep at every level, and after a point I think people get tired of it. At the end of the day, you only have so much time and patience.
I had written a script to manage my pdf literature using crossref and arxiv to fetch metadata and store them in pdf tags, and just renaming the pdf in place. No hidden complexity, no gui.
I hacked it into a python package a couple of months ago in an ADHD hyperfocus induced frenzy. Sounds like you might like it. Still a long way to go, but it's out there and FOSS. Contributions are welcome.
Nix has potential to be a universal installer, although it's still a bit cumbersome when working with languages like python. Another pain point is the need for superuser privilege to write to /nix
Slight detour, but I believe it's the same issue with politicians around the world.
You can also customize Zathura using ~/.config/zathura/zathurarc with the following (for instance):
``` set default-bg "#2E3440"
## Start in dark mode by default set recolor true
## Nord colors for dark more set recolor-darkcolor "#D8DEE9" set recolor-lightcolor "#2E3440" ```
My biggest gripe with nix is that you need sudo rights to get it running properly on another distro. I know you can do the nix-user-chroot thing, but it's not possible on machines where kernel namespaces aren't accessible for unprivileged users.
I spent time understanding it, and getting it working, but it really doesn't work just universally. Once the install process becomes more like, say, miniconda -- where an unprivileged user can install it locally with ease -- nix will get a massive boost in my books. Until then, I can only yearn.
This is the second comment in the entire thread. And the poster is just one person. What makes you generalize something to an entire community, seemingly without any basis?
It's about creating a habit, like many people mentioned here. For me, the git commandline process was a bit too much hassle and typing to do if I wanted to do it atomically. In the end, I wound up using lazygit[0] and the nvim plugin[1] to make life easier. It makes committing only selected chunks a lot easier, not to mention easier cherry picking and other stuff.
[0] https://github.com/jesseduffield/lazygit [1]: https://github.com/kdheepak/lazygit.nvim
Wow. I had used coolors and sadly failed to bookmark it the first time around. I looked for it again last week but couldn't find it. Thank you for this!
I use lazygit[0] to essentially do the same thing. (or even vim-fugitive[1])
Previously I avoided creating messy commits simply because it was "tedious" to reorganize commits. And making overly atomic commits and typing out git commands more frequently didn't appeal to me either.
Once I got used to the above tools, life got so much easier. Lazygit makes it super easy to amend, reword, and even re-position commits in a TUI environment. Real life-changer for me. I can stage hunks super easily too, though that's even easier in neovim.
The only issue I face is my C-j/C-k keys are already bound to tmux, but are needed by lazygit to reposition commits.
[0] https://github.com/jesseduffield/lazygit [1]: https://github.com/tpope/vim-fugitive
If you want the lazy way (the way I have it):
setxkbmap -option altwin:swap_lalt_lwin,caps:ctrl_modifier
xcape -e 'Caps_Lock=Escape;Alt_R=Control_L|space'
I know that there are better ways to do this. But I never get around to trying them out.Arch, i3wm. Love having a personalized keyboard-first setup that I can say I've built over time.
A tip for those who may just be starting out: switch your LEFT-ALT and WIN keys. Also make caps lock act like ESC on tap and CTRL on long press. See xmodmap, setxkbmap and xcape for this.
Regarding your first point, why not just run scripts with `bash script.sh` or even better, use shebangs and `./script.sh`?
The standard shell experience is decades old, and makes it cumbersome to keep up with the pace of today. The appeal of zsh/fish is the user experience and extensibility. I have a shell config using zinit [^1] that installs my dev environment for me (fzf, tmux, nvim, and my zsh-plugins) as long as zsh exists on the new machine. While one may argue that they prefer strictly standard bash so that everything is POSIX compliant, you just have to ensure that your scripts are run with bash or whatever shell the script was made for.
"Yes!"
Thanks for the recommendation.
What is also fascinating is the marketing and advertisement influence in all this.
In villages here a couple of generations ago, they would dry coconuts and make the oils at home. No industrial refinement, heating, and deodorization. But a few years ago there was a huge push against coconut oil, probably from the other segments of the cooking oil industry. Now there are studies saying coconut oil is actually better than most seed oils.
It's the same thing with sugar/fat and cigarettes.
And that brings us to the underlying problem: How does the public form an informed opinion when industry-funded research skews results one way and also has the "propaganda" benefit?
I'm a little late, but here goes.
How many software engineers does it take to change a lightbulb?
(None. It's a hardware problem)
This is classic jugaad. Well done, and to great effect!
Just a quick thank you to the author.
I've been putting off looking for an audiobook reader for linux to improve my german. HN makes life easier ;)
This is so cool, and well done. Thank you :)
Nature has the highest percentage of affected papers. Huh.
This is great! I did something similar for myself that also renames the input pdf file based on metadata from CrossRef. Hopefully I can get around to contributing code to this project.
Great work! I'm looking forward to using it full time. A couple of quick comments.
1. It doesn't seem to work with when $TERM is set to some non-default setting. (panic: terminal entry not found) 2. When term is forced to xterm-256-color, aerc crashes when the window is resized.