325 karma · joined May 3, 2015
https://daniel.perez.sh
my public key: https://keybase.io/tuvistavie; my proof: https://keybase.io/tuvistavie/sigs/oBOnOhiTkwy1TZdg0sNlOyU02V0cDPt2IV-E8YSZti8
* Start editing in Chrome
* It becomes long so copy-paste to Atom and edit there
* Copy-paste back to Chrome
To avoid this, I have then be using https://chrome.google.com/webstore/detail/wasavi/dgogifpkoil... to edit directly in Chrome but thought that it would be better to use a real editor rather than a subset, which is why I created this package.
I have an editor opened almost all the time, so pressing a shortcut and being able to edit directly there without copy-pasting around is actually saving me some time compared to my previous workflows.
What I meant was not a post-fetch (which if I understand, runs only once) step but rather an init script that would load the scripts at each shell startup, what pathogen would do for vim, for example.
I looked a little at peru docs and the links you gave me, and that is pretty much the point I gave in my other comment:
> I would rather manage my packages using a simple fish shell script rather than making the setup more complex with something too general.
I know there are plenty of powerful tools that can manage pretty much anything, I do use Ansible locally to setup my machine and could easily have it download my fish packages as well. However, when it comes to a particular software, especially when loading the downloaded resources is neither automatic nor obvious (e.g. vim, emacs, fish), I find a simple and specialized tool in the target much more pleasant to use, which was my motivation for this one.