Well I don't do much markdown right now... maybe in the future, but this video is very interesting. IMO starting for the fact you 're using windows. The use of Limelight and Goyo and a lot of other plugins are quite cool. I'll look more of your videos for sure. Keep your good work !
Came here accidentally, Liked, Subscribed You have nice set of plugins Was struggling to get live preview of Markdown files, non of RU-vid videos helped, your video and plugins saved me Thank You P.S. Can you point me to some playlist(youtube videos) where I could learn Markdown ?
There is another vim plugin that lets you copy paste images from clipboard directly to your markdown files. Just like gui editors. It would save the image in the working directory and create the alt link. All by just pasting the image.
I use Neovim proper, and try to keep my plugin count to a minimum, do you use any native vim feature `function` for navigating through markdown documents, I've hacked together my markdown filetype doc a little for working with markdown docs in (n)vim, but something that i haven't really utilized is jumping to headings under the cursor, a la to how vim jumps to a file under the cursor using `gf`, it'd really be nice to go to a toc for a markdown document navigate through the toc, find the heading that i'm looking for, and then using something similar to `gf` jump to the heading under the cursor. I like you maintain several large markdown documents that i mostly have shared on github using the github wiki feature, and up until this point i've been using the good ol, `/` to search for the heading in the document and then using `n` to move my cursor the place i'd like to be. if i could remove a few these steps, it'd help me a lot when editing markdown documents. Quality video, and recording BTW.
I don't know of any built in functions to create a TOC. I used github.com/plasticboy/vim-markdown in the past for a TOC but got rid of it for the native markdown support. Maybe you can rip out just that functionality from that plugin.
Yep that's fzf, I have it mapped to CTRL+p , here's the bind from my vimrc: github.com/nickjj/dotfiles/blob/085c4ac827290bc7aeea435ce193279798073c58/.vimrc#L479
Yep, I started with WSL 1 a few years ago but use WSL 2 nowadays. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-idW-an99TAM.html is a video where I pulled together all of the tools I use.
Agreed! I would just need new hardware since when I tried going native Linux I had issues with my audio crackling during recordings. I wrote about that situation here nickjanetakis.com/blog/i-tried-linux-as-my-main-dev-environment-but-was-forced-back-to-windows.
:MarkdownPrevier or Markdown it self not working what should i download for use? Plug 'godlygeek/tabular' Plug 'plasticboy/vim-markdown' anything else ?
I did play around with various editors but there was little point to do so anymore since VS Code. Don't matter whether you are on Linux or Windows and particularly indispensible on wsl2.
Hi Nick, Thanks for the Video. I'm new to markdown and try to keep myself up in vim. I'm facing a major problem in markdown. Could you please, help me out. PNG type Images do not render in browser (images should show up in browser), while TOC links do not redirect to appropriate heading (TOC links should redirect when clicked to a heading). Any idea why this is happening and where possible to look for the solution? Further details follow: Following plugins installed: Plug 'godlygeek/tabular' Plug 'plasticboy/vim-markdown' Plug 'iamcco/markdown-preview.nvim', { 'do': { -> mkdp#util#install() } } Plug 'SidOfc/mkdx' " ================ 'plasticboy/vim-markdown' ===================== let g:vim_markdown_conceal = 0 let g:tex_conceal = "" let g:vim_markdown_math = 1 let g:vim_markdown_frontmatter = 1 " for YAML format let g:vim_markdown_toml_frontmatter = 1 " for TOML format let g:vim_markdown_json_frontmatter = 1 " for JSON format let g:vim_markdown_anchorexpr = "''" let g:vim_markdown_auto_insert_bullets = 0 " ================ 'iamcco/markdown-preview.nvim' ===================== let g:mkdp_auto_start = 0 let g:mkdp_auto_close = 0 let g:mkdp_refresh_slow = 0 let g:mkdp_command_for_global = 0 let g:mkdp_open_to_the_world = 0 let g:mkdp_open_ip = '' let g:mkdp_browser = '' let g:mkdp_echo_preview_url = 0 let g:mkdp_browserfunc = '' let g:mkdp_preview_options = { \ 'mkit': {}, \ 'katex': {}, \ 'uml': {}, \ 'maid': {}, \ 'disable_sync_scroll': 0, \ 'sync_scroll_type': 'middle', \ 'hide_yaml_meta': 1, \ 'sequence_diagrams': {} \ } let g:mkdp_markdown_css = '' let g:mkdp_highlight_css = ''" let g:mkdp_port = ''" let g:mkdp_page_title = '「${name}」' let g:vim_markdown_new_list_item_indent = 2 " ================ 'SidOfc/mkdx' ===================== let g:mkdx#settings = { 'highlight': { 'enable': 1 }, \ 'enter': { 'shift': 1 }, \ 'links': { 'external': { 'enable': 1 } }, \ 'toc': { 'text': 'Table of Contents', 'update_on_write': 1 }, \ 'fold': { 'enable': 1 } } let g:polyglot_disabled = ['markdown'] "
Hi, TOC links jumping to an anchor point isn't part of the markdown spec. That's just something github does for you behind the scenes in their web UI. If you want that behavior you'd have to drop in the anchors manually as HTML. As for the png issue, can you gist your markdown file? They shouldn't be any different than loading gifs or jpgs.
What does the '|' character do in your Plugin listings is it a pipe or a logical "or" character? for instance: " Add spelling errors to the quickfix list (vim-ingo-library is a dependency). Plug 'inkarkat/vim-ingo-library' | Plug 'inkarkat/vim-SpellCheck' " Distraction free writing by removing UI elements and centering everything. Plug 'junegunn/goyo.vim' " A bunch of useful language related snippets (ultisnips is the engine). Plug 'SirVer/ultisnips' | Plug 'honza/vim-snippets' Plug 'godlygeek/tabular' | Plug 'tpope/vim-markdown'
In this context, if you removed "|" and put each Plug line on their own separate line it would work the same way. I like using "|" in this case because it visually hints there's a dependency between these 2 packages. For example the snippets and ultisnips packages are highly related and the vim-ingo-library package is a straight up dependency of vim-spellcheck.
@@NickJanetakis yeah yeah I get that. Its just I personally haven't seen vim being used like that inside wsl before. Since there is a version for windows, why not use that one?
@@NickJanetakis thanks! you could make a serie or a course with how to setup WSL to be a very good developing envirnoment. I'm trying to setup it and when I watch your videos I see that you just owned it
@@LuizFelipe-sm2xp Yeah I could do that, maybe one focused on WSL and my terminal. A while back I made a video that covers a bunch of Windows tools that composes my entire dev environment (inside and outside of WSL). That's at ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-5gu8wWX3Ob4.html but at this point it's a bit out of date on some of the tools (such as using Vim now instead of VSCode and wsltty as my terminal instead of the default Ubuntu one -- everything else is about the same tho). It also doesn't cover installing WSL specifically, but truthfully it's just a free app you install from the MS store.
