Skip to content

silver searcher in emacs - #20

Merged
esquivalient merged 4 commits into
masterfrom
silver_searcher
Jul 6, 2022
Merged

silver searcher in emacs#20
esquivalient merged 4 commits into
masterfrom
silver_searcher

Conversation

@esquivalient

@esquivalientesquivalient commented Jun 28, 2022

Copy link
Copy Markdown
Member

Add Silver Searcher as an option for projectile searching

This is branched off of #19, because I can't live without OrgRoam. It makes the diff pretty useless right now, but you can tell what's happening if you just look at the most recent commit.

esquivalientand others added 4 commits March 12, 2022 11:44
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?
---------------------------------------------------------------
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?
---------------------------------------------------------------
@esquivalientesquivalient changed the title silver searchersilver searcher in emacsJun 28, 2022
@esquivalient
esquivalient merged commit 832f573 into masterJul 6, 2022
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@esquivalient@mediocretes