Add an alias to push and set git branch and tracking #21
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Why is this change needed? -------------------------- I want a better way of recording and organizing knowledge. I reviewed a bunch of tools in this space including, but not limited to, - roam - logseq - notion - obsidian I was surprised to find that Emacs provided the best tooling overall. I had a lot of requirements, but the key ones were - no writing style requirements - for example, Roam and Logseq require everything to be a node in a tree. I just want to start writing without any thought to format. Also, a tree is not always the best way to represent information. - stored in plain text - everything I write should be as portable as possible - stored in a place I can control or export - if I decide to switch tools or the tool I'm using goes away, that shouldn't make me start over - navigate by reference or tag - it should be easy to find linked or unlinked references to anything I write about, either because I'm implicitly mentioned it somewhere, I've explicitly linked it, or I've explicitly grouped the ideas together with a tag How does it address the issue? ------------------------------ Org Roam is the most popular zettelkasten package for Emacs and does the above once configured correctly. I also added Org Roam UI, a web interface for navigating your notes, to make it even easier to see knowledge relations and find notes I'm looking for. This implementation doesn't address all of my needs, but committing this is the last thing I need to do to switch laptops so it's happening anyway. In particular, I haven't - made sure that everything that's embedded in a note is stored in the note repository (e.g. adding an image should put the image in the repo) - actually turned the org roam directory into a repo for maximum storage safety - installed a flashcard solution - enabled transclusion - decided on a publishing feature (if I want one) Still, it should fire up and work just fine for anyone. I'm already using it fairly extensively. It might even eventually take the place of my tmp file. Any links to any relevant tickets, articles or other resources? ---------------------------------------------------------------
…oam_m1_with_setup
Why is this change needed? -------------------------- It was recommended by several people while I was setting it up, but I never want it. How does it address the issue? ------------------------------ I'm deleting it because it's bad to have code you never use. Any links to any relevant tickets, articles or other resources? --------------------------------------------------------------- https://3.basecamp.com/3093825/buckets/14355728/todos/4853961505
Why is this change needed? -------------------------- The second most common thing I do with Projectile after using it to find a file in a project is search the project for instances of a thing. I was using grep because it's easy, but I always use `ag` in my terminal so it makes sense to expand that option to Emacs. How does it address the issue? ------------------------------ Add the package Any links to any relevant tickets, articles or other resources? ---------------------------------------------------------------
Why is this change needed? -------------------------- It's the most common thing in the world. You make a new branch, then you want to push those changes to the remote and you get that message about needing to set the tracking branch or specify more info when you push. Most documentation about this makes it sound like it's very straightforward to automate, but I kept running into cases where the simple solutions didn't work and I'd have to type things out the long way. How does it address the issue? ------------------------------ Add the alias 'gpu' that does all of the steps idempotently. If you haven't pushed and set tracking, it does it for you. If that's already done, it pushes. I left a link to the most relevant SO in case the best way of doing this changes in the future. Any links to any relevant tickets, articles or other resources? ---------------------------------------------------------------
jason-o-matic
approved these changes
Jun 28, 2022
Member
jason-o-matic
left a comment
jason-o-matic
left a comment
There was a problem hiding this comment.
I only reviewed the one commit (5b3f6db) but it looks reasonable to me. 👍
mediocretes
approved these changes
Jun 29, 2022
Member
Author
|
Kk, will merge when I work out the dependent PRs with @mediocretes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details in the commit message.
This is branched from #20, which is branched from #19. Ideally, I wouldn't branch from things that haven't been merged yet, but I'm already using these things and it's inconvenient to flop around.