bouncer
← Back

linkarzu · 3.8K views · 87 likes

Analysis Summary

20% Minimal Influence
mildmoderatesevere

“Be aware that the creator's preference for Rust-based tools is presented as a self-evident marker of quality, which may lead you to overlook non-Rust alternatives that could be equally stable.”

Transparency Transparent
Human Detected
98%

Signals

The video features a highly personal, unscripted technical demonstration with natural disfluencies and specific workflow nuances that are characteristic of a human creator. The presence of a linked raw livestream further confirms the content was recorded live by the individual.

Natural Speech Patterns Transcript contains numerous filler words ('um', 'uh'), self-corrections ('Well, it's not new, you know, but...'), and conversational tangents about specific people like 'Ed Fernandez'.
Live Demonstration Context The speaker interacts with their environment in real-time, describing keyboard shortcuts ('type the letter R', 'Ctrl Y') and reacting to on-screen UI elements like the 'Harper' plugin warnings.
Personal Anecdotes and Workflow The creator explains their specific daily note structure and personal habits (using Kitty terminal sessions) which are highly specific and non-generic.
External Verification The description provides a link to a 1.5-hour raw livestream of the recording process, which is a strong indicator of human labor.

Worth Noting

Positive elements

  • This video provides a highly practical, step-by-step configuration guide for users looking to bridge the gap between Obsidian's linking capabilities and Neovim's editing speed.

Be Aware

Cautionary elements

  • The creator uses 'revelation framing' to present a tool he discovered that same day as a definitive solution, which may bypass the viewer's usual vetting process for software stability.

Influence Dimensions

How are these scored?
About this analysis

Knowing about these techniques makes them visible, not powerless. The ones that work best on you are the ones that match beliefs you already hold.

This analysis is a tool for your own thinking — what you do with it is up to you.

Analyzed March 13, 2026 at 16:07 UTC Model google/gemini-3-flash-preview-20251217 Prompt Pack bouncer_influence_analyzer 2026-03-08a App Version 0.1.0

More on This Topic

Related content covering similar topics.

Transcript

If I type here P ed going to take me to this specific heading. [music] Okay, the cool thing about this is that you can see that there is one reference in this heading at the very top of the file. You can see that there are four [music] references R is going to show me in uh the [music] snacks picker. That's the one that I use the four different references that are pointing to this file. They have another one here specially dedicated to Ed. Ed Fernandez. Is Is it Fernandez? Yeah, Ed Fernandez. Ed [music] seems to like it hard as well. >> What are we going to be looking at today, [music] folks? We're going to be talking about a new LSP. Well, [music] it's not new, you know, but it's something that I discovered today, actually, and I just want to record a video and [music] share it with you guys. Okay, so I'm going to pretend that you guys know nothing about my setup because there's a lot of people that are just watching this for the first time. And um I'm just going to try to make you understand why an LSP is important when you're editing markdown files. It's not just for programmers, but you're going to see right now. So if you use Obsidian, and this is definitely for you, okay, so I use the daily notes a lot. That's one of the things that I use every [music] single day. Okay. So, if I quit this kitty session right now, just going to quit it here. I'm going to go to another kitty session. Okay. And uh just so you know how this [music] works for me. If I type the letter R, if I leave it pressed, it automatically creates a new session for me and opens my daily notes. That's it. Right? So, doesn't matter where I am. If I'm here, if I want to go to my daily note and write something down, I just type this and I'm there. Okay. And I write it down. It's pretty useful. Okay. This daily note lives in my Obsidian repo. Well, this used to be my Obsidian repo, but now it's just a folder that I open in any of them or a directory that I open any of them that has all my different nodes. Okay. But inside here, you'll be able to see that I have this 250 daily folder, the year, and the month. These are automatically created depending on the date. Okay? And this is automatic created as well. [music] I have some videos about the daily notes. That's not what we're going to cover in this video. You can go and check those out. But this LSP Markdown Oxide also has a daily note feature. Let's say that I'm here in my daily note today and today I learned how to navigate the vain resolve with H and L right so I could come to this other repo which is my obsidian repo I could open the Vincent resolve I could open this note here right and I could add this information here but as you guys see it takes [music] time right I need to open another repo I need to look for the file I need to so where I'm going to add this note. And [music] you know, it's good if you want to keep stuff organized, but it's not optimal. I'm just going to type here. Navigate Dinci. Oh, you know what? I'm going to link the note here. Okay. Dainci Resolve. Notice that the LSP automatically detects the [music] note. I'm just going to accept this. I could link to a heading if I want, but I'm going to link to this first result here. Ctrl Y to accept it with width, H, and uh L. Okay, >> try to use title case in headings. Okay, this is Harper. I'm just going to type something [music] in here. So, let's say that I want to store this and I don't want to go to the Dainci note, right? and I continue with my day, you know, but notice that I'm referencing that Denture Resolve note here. Then later during the day, I find out that I want to document something else because I figure this out. Clicking while leaving option [music] pressed. Okay, so let's do that as well. Just going to create a new heading here. Clicking just want to link it to the main note. [music] Okay, try to use title case in headings. This is Harper, the one that is showing that just in case that you guys don't know. I have my notes that I need there. Let's see. A Vinci. Okay. And I'm done with the day today. Another day, let's say a week after, I want to remember what this was. You know, [music] I want to remember about these two tips that I left here. And let's say that I'm in this other repo. You're going to notice this showed up at the top to references to [music] file, right? That's pretty cool. So, how can you see those references? [music] And that's one of the reasons why I left marksman because it's not able to show you back links. Okay, so if I type GR here, you're going to be able to see these two notes that I'm referencing right now. [music] This is one of the headings. This is the other one. Okay. So, I can go to this one if I want. It's just going to take me back to this [music] note. Click Ctrl O. I can go back here. You can link notes pretty easily. And then you can see the back links on the notes that you're referencing. And you cannot do that with marksman. At least not that I'm aware of. Right. If I type GR here, it's going to say no results found for LSP references. That's something that you need to keep in mind. You need to type GR or you need to type go to reference somewhere that is not a heading. Okay, so going to do it here, the R and it's going to show me the references. These are back links in Obsidian. It's the auto completion based on file names or the first H1 level. That's the beauty of New that you can configure stuff however you want. Okay, if I go to this repo, my Obsidian repo, you're going to be able to see that I have this file markdown oxide. Let's go to the documentation for this thing. And you're going to be able to see that configuration. You can specify the configuration for this file in with different options. You can do it like statically in this file, but I prefer to do it in a per project basis, you know, because you can have different settings per project. So, I added it at the root of my repo and that's [music] where it lives. If you like your nose to be the first heading or it can be the file name, I think if you set this to false. Yeah, but it's here somewhere in the settings. [music] This is what I use, so I'm keeping it that way. But, but it's configurable. Here's other examples. New images and new. Okay, this is linking to a different heading [music] in this file. This file that is called test markdown and this heading that is called image and vim to view images. Right? So, how do I jump to this file? I just type GD which is go to definition. If I type that here, GD, it's going to take me to that file directly to that heading and boom, we have [music] it there. Right. How do I go back to where I came from? Ctrl O takes me back [music] where I was. Okay, I have this other link here. Same file but different heading old block by itself. So if I type here ed going to take me to this specific heading. Okay, the cool thing about this is that you can see that there is one reference in this heading. Okay. And at the very top of the file, you can see that there are four [music] references total, right? One of those four references is in this heading. So, how can I go to [music] this reference? Dr. R. go to reference. Okay. So, you just do GR here. It's going to take me back. How do I jump to the other references that are here? Cuz notice that there's four of them, right? I can jump to a reference. If I do GR here, but if I do it in an empty space anywhere here, doesn't matter if it's not a heading or if it's not a tag, I can jump to the other references. Going to do it here. E R is going to show me and uh this next picker. That's the one that I use. The four different references that are pointing to this file. One of them or three of them are from today, right? We can see this them here. These were [music] the two that we were looking at a moment ago. This one I already marked it. Oh no, this isn't the same file as well. Yep, yep, yep. And this comes from another file [music] called test headings. Okay, that one comes from here. I did have a huge problem with marksman that it kept [music] stopping and I don't know why. Probably skill issue on my side. I think that's what that that's what it is you know because it worked [music] then it stopped working and I had to start it I even created a key map for it right so if I do here theater M and this one here capital R start or restart marksman I haven't had that issue with markdown oxide [music] at all just in case that you guys don't know what marksman is I also have a video about that it is the one that is shown here and I'm going to leave it in the video description cuz marks mount is available not only in neo but it's also available in a lot of different editors. This is the plugin markdown oxide. It's written in rust based on what I can see here. Just works man. It's pretty efficient. I don't know what's up with this furies, you know, that use Rust for everything, but stuff just works to be honest. You know, all of the different tools and even plugins that I use that are written in Rust are efficient, they're fast, and they work quite well. So, I'm not sure if they're pretty scaled or what's going on, but yeah, here's the link. Going to leave it in the video description as well. You can go and check it out. Make sure to start it cuz man, it's an amazing plugin so far. [music] Okay. And it seems that it's actively being developed. If you ever watch this video, amazing, amazing stuff. How do you navigate the LSP symbols? Okay, I'm using Lacy. Okay, and I'm going to show you the key maps that are configured there. If I type here little letter SK in laciv, you're going to see symbols. Okay, Pokei created these two emaps so you can configure them on your own editor as well or you know [music] it just opens the LSP symbols with the snacks picker. There's also this other key map you know with capital S that is going to show you the workspace symbols which is all of the symbols in the project. How do I navigate the headings in a file? Right? Do I go heading through heading and I just search them and that's just like useless like I'm not right. So if I type leader SS I will be able to see this picker and I can just search for the heading that I want. What if I want to search the headings in my entire repo not only in this file but in [music] the in the entire GitHub Obsidian main repo. Just going to do theater s capital S. Going to search for Oh, tiny mist. Look at this beauty. New fix lb issues. Tiny mist. Okay, so I was able to get to this. You know, if I know at least a word in one of the headings, I'll be able to get to it. Let's move on cuz these guys are just drunk and drugged. Okay, so let's move on. The hover feature. This was available on Marksman as well. Okay. So, if we go here to another link, let's see. Oh, this one for example, right? I have this here. And if I just type uppercase K, the same way that you do it everywhere, you'll be able to get the hover window and you can get a preview. Right? If I type it again, uppercase K, I can jump into this preview and I can just navigate it. You can use that preview pretty much um everywhere. If I type here uppercase K, I can see a preview of that there as well. We already demoed this gr to go to reference. Just didn't want to forget the R on a non heading to see the list. We already covered this as well. If you're coming from marksman and you're wondering, so [music] is this markdown oxide going to work with my marksman stuff or my marksman workflow? Let's see. Notice that I created these links in another video. They work fine. Okay. If I do GD here, takes me here, right? I can go back. [music] And if I do GD here, it's going to take me to this link and so on and so forth. Okay. [music] [music] Create a new note from a non-existent reference. Okay. So, I'm just going to type GD here and I'm going to jump to this note. Okay. And I want to create a new note. I don't want to go to a specific file and create [music] the note. I'm just going to type here these two square brackets. And I'm just going to type something YouTube video. [music] This note does not exist. And you're able to see here Obsidian LS unresolved reference. So I'm just going to move back and I'm going to create this note. Okay. So I'm going to execute a code action here. If I do space or leader D, [music] C is for code actions. Notice that I have these different options at least in the laciv distro. And I'm just going to type the letter A. And it's going to show me this menu of code actions. [music] And it's going to ask me if I want to create this file. Notice that it's asking me or it's showing me this directory 010 new notes. Okay. And it's going to title it this [music] recording the markdown oxide YouTube video MD. I'm just going to hit enter here and the note is [music] created. Okay. If I do here GD, it's going to jump into that note and I can see that there is a reference to that note and I can title it something. Let's say test [music] file. Where was this note stored and why? If we come back here to my Obsidian repo and I go to the root of the repo, you will be able to see again this moxide file. If I open it, I specify that here the config new file folder path 010 new nodes. So if I open this directory, you'll be able to see that is right here. I have another one here specially dedicated to Ed Ed Fernandez. Is is it Fernandez? Yeah, Ed Fernandez. Now, here's the notes that we just created. Recording the markdown oxide. You can use a template if you want. And I actually use templates. Let's do it in ads note. Okay. And I have here template uh blog post templates, right? And if I do Ctrl Y, it's going to insert [music] the template. And I can specify here the title, test, description. And I can jump here. So it would be 2026 here. And I can jump here to uh tags all. And you know, I just did the template that way, but that is [music] something that I do with the Lu Snip plugin, right? Luis Snip.la. This is the one that I use. [music] Here's where I have all my snippets. This is pretty interesting as well. References on a link allow me to see if I need to re rename it with CR. Okay, so this is very important as [music] well. If we jump back here to my Obsidian repo and I jump back to my test file, this test markdown file. Okay, let's say that I want to rename a heading, right? Let's say that I want to rename this. I see that there's no references pointing to this heading. If I just rename it, it's fine because it's not going to break any links. Okay, but what if I want to rename this heading? [music] Let's give that a try. Okay, let's give that a try. Let's jump back here to the daily note. And where is [music] that itself? Here. Notice that I'm referencing that link from this note. Okay, but notice what's going to happen if I just rename this like a crazy person, right? Load block by itself. >> I just renamed it. It's all good. At least I think that everything's good in life. But if I go back here, notice that there is an unresolved reference. So I things up already. I cannot go to this [music] reference anymore. If I type GD here, it's not going to find it, you know, cuz the LSP is not aware that this was changed. So, that's not the way that you should rename stuff if it's being referenced. Let's rename it correctly this time and let's see what happens. Little CR code block number two. Okay, so let's hit enter here. Let's go back. Where is the other file? Oh, there it is. code block number two. So you have to be careful when you see that there is a reference here. Don't rename it just like that because you're [music] gonna things up. Okay. So just use the LSP to rename it. Display code lens. Okay. [music] This is pretty cool as well because by default in lacy vim this code lens is not enabled in the markdown files [music] or in any of the files actually. So if I jump back here you won't be able to see this [music] for references to file. This is a code lens and um there is a key map in laciv theater c uppercase c. So it's not going to show by default, but if you type that, it's going to show here. [music] So you can see the references. I created an auto command in my config so that if it detects that it's a markdown file, it will automatically [music] do it just for markdown files. So I can see the references C and [music] here it is uppercase C. Refresh and display code lens. Okay, so that's what this is about. [music] Table of contents. Does anyone here use the markdown talk or markdown TOC plugin? I have bad news for you. Won't work. Won't work. And uh let me show you [music] right now. Contents. Table of contents. I automatically populate the table of contents, but it will not work with this specific markdown oxide plugin because it doesn't recognize this. You can link them. I want to jump there. Okay, [music] there it is. There it is. There it is. Okay, so notice that it's linked now. Okay, but I'm not going to do that for all of my different notes. Hell no. It works. If I type GD here, it's going to take me there, but it doesn't make sense. So, what I'm going to do then is just to delete the table of contents [music] from each one of the files because I don't need it to be honest. Okay. So, if I type here space SS, it's going to show me the LSP symbols. So, I can see all of the headings here, right? So, why would I keep a table of contents if I can access all of the headings through the LSP symbols and just search for them there? Here [music] or here? Here or here or here or here? What do you guys want to see me? if you want to see what other features [music] are available like tags are available in markdown oxide as Ed was mentioning um and there is some other features like footnotes if someone here uses footnotes you won't be able to see and find that as well in the documentation if we go here >> [music] >> uh GX here's the documentation in the features index you'll be able to see like images [music] that explain the different features for the tool the footnote modes, which is something that I don't use much. Well, I don't use at all as well, but Obsidian Freaks definitely use this. So, you'll be able to find the information there. Aliases as well are completed, just in case that you guys use aliases in the front matter for each one of the files. There's this really cool LSP saga plugin as well. Seems like a pretty cool idea because it allows you to edit the references [music] in place. Okay. So, you don't rename your headings in the heading directly, but you do it in a popup for this plugin and you [music] don't have to worry about it. >> There's a demo on that here in case you want to check that out as well. But everything's in the docs. I'm going to leave them in the video [music] description as well. In case that you guys are wondering, when I was typing throughout this video, there was [music] something complaining there. If I type this with an uppercase N, there's this tool that is telling me try to uh replace this with an uppercase right in titles. [music] That is Harper. It is another language server. It's another LSP that runs with Markdown Oxide, but it's useful for grammar [music] related stuff, right? So, if I type a bad word, let's type something here. This is a test. Notice that it's going to complain. Doesn't like this, right? So, it's it gives me [music] code actions and it gives me options. Um, I can replace it with something else or I can just delete it. If you're wondering or if you want to know more about Harper, I do have a video about as well. Oh, it's right here. Right [music] here. So you can go and check it out and I explain everything in detail there as well. [music] In case that you don't want to set this up by yourself in case that you're new to Neoim, if you came into my channel and you're like, "What the hell is this guy talking about? Where should I start?" If you don't want to configure everything yourself and go to my files, I think I have instructions here on how to try my config in case they want to try my config. I haven't pushed all the changes right now, so depending on when you watch this. Probably not all of the changes are there, but uh it'll give you an idea on how all of this works, [music] so you don't have to configure it yourself. LSP saga to edit in K preview window or anything else. Ed seems to like it hard as well. The last point that I have here is how do you set this up? First, make sure that you install it. I install it through Mason. Okay. So, if I open my Mason file, you'll be able to see it here. I have it at the bottom. Okay. So, [music] there's markdown oxide. Okay. You install it however you want. If you're a Mac OS gighat like me, you can install it through Brew. You can install it through Mason. All of that is specified in the documentation. Okay. Now, I also use the Markdown Lacy Extra and that one install marksman [music] via Mason. So, I disabled Marksman and then I uninstalled [music] it. So, you don't you you don't want to have both Marksman and Markdown Oxide cuz they're going to be fighting each other, I think, and you're just going to get in in trouble, right? So, just don't keep both. Keep one of them. I just disabled it in my NVM LSP config file and uh I disabled it there and I enabled markdown oxide. Let me quickly jump there. Nvim LSP config. Marksman is here. I set it to enabled balls [music] because it's already included and the lacy vim markdown extra which includes other stuff like markdown preview and other plugins. So I just disable it and here is markdown oxide. Okay, this section right here you can also uninstall marksman after you have ran this markdown oxide. If you open mason it's gonna remain installed, right? So you can uninstall it or or not cuz it's not going to be attached to any buffer. The config file, we already [music] went through this at the beginning of the video. We covered everything about Markdown Oxide. Hope this video was useful. If you liked it, remember give it a thumbs up. If you appreciate the plugin that this person created, go and give it a star. and if [music] you can sponsor the project. I'm not sure if it has sponsorships enabled or not on the GitHub repo. Okay, but uh go and check that out as well. If you like the channel, subscribe. Remember, you can also become a member. Well, guys love open source and are cheap, so that ain't happening, but still an option. I also want to thank the CEO, Web23, web23.com. The name showed up somewhere or it's going to show up somewhere. and uh all of the other YouTube [music] members. So, that thank you very much for joining me and uh recording this video. We're going to see if this works out or not. If you like for me to record videos this way, that's it for today, chat. I'll see you in the next video. Someone asked about this. This is my new logo. Let's see if the phone focuses. My daughter made this for me. So, [music] who uses Helix though? There's like three users. Is it still maintained? Was it abandoned already? Not yet. Did we [music] interview the helix that went to set again? Yes and no. E M A D S Emac 8 max and constantly swapping. Is that where it comes from?

Video description

Neovim + Obsidian Backlinks, Renames, Headings: Markdown-Oxide Setup. In this video I set up markdown-oxide (a Rust-based Markdown LSP) in Neovim, disable marksman, and show the exact workflow that makes a Markdown vault feel like “Obsidian features inside Neovim”: - Create notes from unresolved links - See references/backlinks to headings and files - Rename headings and update references safely - Hover docs, symbol navigation, and code actions - Auto-refresh codelens ONLY for Markdown buffers (so you don’t need manual refresh) I’m using LazyVim + Mason, but I also explain what to change if you’re on your own config. If you want to watch the 1.5 hour livestream of me recording the video: https://youtube.com/live/aEyFGjiTHN4 You wanna promote yourself in my channel: https://linkarzu.com/about/#community-driven-promotion ━━━━━━━━━━━━━ If you're not a YouTube member yet, you can join here: https://www.youtube.com/channel/UCrSIvbFncPSlK6AdwE2QboA/join ━━━━━━━━━━━━━ Playlist with all my interviews: https://www.youtube.com/playlist?list=PLZWMav2s1MZRr93uiz6vjEWCdXL93QzGz ━━━━━━━━━━━━━ What is this podcast about, why, and where to find it? https://linkarzu.com/about/#im-confused-is-there-more-than-1-podcast ━━━━━━━━━━━━━ Chapters ━━━━━━━━━━━━━ 00:00 - Why is an LSP important for Markdown? 05:03 - gr to go to reference 07:01 - Markdown-Oxide Configuration File 07:19 - Set title of notes as first heading 07:47 - gd to go to definition 09:44 - Marksman LSP kept stopping in Neovim for me 10:33 - Markdown-Oxide repo 11:23 - Navigate LSP symbols (Markdown Headings) 12:09 - See ALL Markdown Headings in a Project 12:50 - hover or preview feature 13:43 - Is it compatible with Marksman? 14:17 - Create a new note from Nonexistent Reference with Code Action 16:14 - I use snippets (templates) with the Luasnip plugin 17:06 - Rename with cr 19:09 - Codelens 20:05 - Table of Contents with markdown-toc won't work 21:22 - Docs are pretty good 22:09 - Lspsaga plugin 22:39 - What's that Grammar checker? Harper 23:45 - If you want to try all of this in my config 24:27 - How to set it up ━━━━━━━━━━━━━ What you’ll learn ━━━━━━━━━━━━━ 1) Install markdown-oxide via Mason 2) Disable marksman (LazyVim Markdown extra installs it) and optionally uninstall it 3) Configure markdown-oxide per repo with .moxide.toml (recommended) 4) Set new_file_folder_path so new notes always land in the right folder 5) Enable Markdown-only codelens auto refresh to keep references accurate 6) Optional: use lspsaga.nvim to edit references in place ━━━━━━━━━━━━━ Key workflow highlights ━━━━━━━━━━━━━ - “References/backlinks” are the reason I switched - `gr` on a heading: jump to references - `gr` elsewhere: list references - `K`: hover - Create note from nonexistent reference (code action) - Codelens for “who links to this heading” (plus auto refresh) ━━━━━━━━━━━━━ Config notes (paths I mention) ━━━━━━━━━━━━━ - Mason setup: ~/github/dotfiles-latest/neovim/neobean/lua/plugins/mason-nvim.lua - LSP config: ~/github/dotfiles-latest/neovim/neobean/lua/plugins/nvim-lspconfig.lua - Global config option: ~/.config/moxide/settings.toml - Per-repo config (recommended): ~/github/obsidian_main/.moxide.toml ━━━━━━━━━━━━━ Links / Resources ━━━━━━━━━━━━━ - markdown-oxide repo: https://github.com/Feel-ix-343/markdown-oxide - markdown-oxide docs: https://oxide.md/index - My dotfiles (LazyVim setup): https://github.com/linkarzu/dotfiles-latest - lspsaga.nvim (optional but recommended): https://github.com/nvimdev/lspsaga.nvim - My marksman video: https://youtube.com/watch?v=SXKsIyYJIrU - Grammarly alternative for Neovim (Harper): https://youtube.com/watch?v=he8V6gj9IG0 #neovim #obsidian #notetaking #markdown neovim obsidian, markdown oxide, markdown-oxide neovim, marksman lsp, neovim markdown lsp, obsidian vault neovim, backlinks neovim, references neovim markdown, rename headings update links, lazyvim markdown, mason lsp setup, lspsaga references, harper lsp

© 2026 GrayBeam Technology Privacy v0.1.0 · ac93850 · 2026-04-03 22:43 UTC