private_comments
lammps-docset
| private_comments | lammps-docset | |
|---|---|---|
| 2 | 1 | |
| 42 | 1 | |
| - | - | |
| 0.0 | 10.0 | |
| 6 months ago | over 1 year ago | |
| Scheme | Python | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
private_comments
-
I’m a Productive Programmer with a Memory of a Fruit Fly
I wrote Private Comments[1] specifically to address this problem in code. My coworkers can maintain context about how a given thing works months after the fact. I can't. So, I leave private comments throughout the code. Things they'd never want committed, but save me hours of re-leaning when next i encounter a given piece of code.
Currently has plugins for Vim (proof of concept) and Emacs (actually good). It'd be lovely if one of you folks would make a VSCode plugin for it. I've thoroughly documented the API and diagrammed the code flow you'd need[2], so that this would be as easy as possible to add to your favorite editor.
[1]: https://github.com/masukomi/private_comments
[2]: https://masukomi.github.io/private_comments/
-
I will pay you to write this plugin for me
A while ago I wrote a mini API server in order to let me leave "private comments" on a codebase.
lammps-docset
-
I’m a Productive Programmer with a Memory of a Fruit Fly
I'm a computational physics student; my work involves using multiple software with varied options. Frequently, I need to check to make sure all my parameters are correct, and having these docs at hand is important for me. Using offline documentation is always faster than Google. Since the docsets for these special pieces of software for computational physics or quantum chemistry is lacking, I build these docsets myself. Up till now, I have written code (and sometimes scrape web pages) to build these docsets myself:
1. LAMMPS: https://github.com/chazeon/lammps-docset
What are some alternatives?
emacs-virtual-comment - Virtual Comments for Emacs
i3-cheatsheet-hot-key - Provides a hot key for creating/opening a custom cheatsheet for the window(application) in focus
phantom-inline-comment - visible but not affect the source code
qe-docset - Dash docset generator for Quantum ESPRESSO.
Dash-User-Contributions - Dash repo of user contributed docsets
vim_private_comments - a vim plugin for private comments
doc-browser - A documentation browser with support for DevDocs, Dash and Hoogle, written in Haskell and QML
ase-docset
devdocs - API Documentation Browser