61–70 of 71 posts
FWIW, IPython is built with Python Prompt Toolkit and Jupyter_console is IPython for non-python kernels; `conda install -y jupyter_console; jupyter kernelspec -h`. But those only do `%logstart -o example.out.py`; Markdown in notebooks on the CLI is basically unheard-of.
https://github.com/cronvel/terminal-kit
Sort of a document model for the terminal https://github.com/cronvel/terminal-kit/blob/master/doc/docu...
I'm a big fan of the Markdown Preview feature in VS Code Honest question: why do developers insist so much on using command line based tools? What's the advantage over using an IDE? (e.g. VS Code or PyCharm)
- works at the speed I think. It renders text quickly, responds to my keystrokes quickly, and lets me work my will quickly. That's nice when I have a lot to do or am inspired, which covers most of the time I'm coding
- It's open source and trustworthy. I'm not gonna wake up one day and find out a critical plugin I use is closing the source and making a change I hate, or that Vim itself was uploading my code to copilot, etc.
- It's basically a platform. You can do whatever you want in Vim, remap all the keybindings, make a music player, whatever.
- It's respectful of my computer's resources. It starts up almost instantly, and generally uses very little CPU and RAM.
Nice idea! I’m excited to check it out. I write a lot of docs in Markdown and this could be a great way to browse them. Out of curiosity, have you seen glow[0]? [0] https://github.com/charmbracelet/glow
I would like to run VSCode with a TUI like this in a terminal via SSH. Does anyone know a VSCode extension to do this?
FWIU coc.vim works with vim and nvim and works with VSCode LSP support: https://github.com/neoclide/coc.nvim There are many LSP implementations: https://langserver.org/ awesome-neovim Ctrl-F "DAP": https://github.com/rockerBOO/awesome-neovim#lsp mason.nvim: https://github.com/williamboman/mason.nvim : > Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP se…
Earlier quoted context omitted.
I get all three of those w/ my VS Code setup...could you explain in more detail?
VSCode isn’t much different from vim or emacs in terms of functionality: basic text editor that is configured for various tasks by plugins. Especially with the rise of LSP, the difference between VSCode and vim/emacs is basically preference.
Ease of extensibility is a big deal and vscode is much less easy to configure.
VSCode doesn't work uniformly throughout the application. In emacs, you'll quickly start to depend on all the places you can use M-r, M-n, and M-p to reverse search history for instance. This is one of many many examples where it's keyboard driven UX is superior.
Another big thing is that you can get help for every keybinding, click a link to it's function, and start modifying the implementation.
There was a recent podcast I can't recall that gave a good example of this... I'll look for it and post back if I find it.
I'm curious, how would you do what I describe here using isearch to query replace in vscode: https://old.reddit.com/r/emacs/comments/126w8xb/what_are_the...
Earlier quoted context omitted.
There's a few terminal browsers like w3m, browsh and links that should work for many basic HTML pages.
A full terminal web browser is a bit more than I was looking for, but this is definitely an option. Was thinking more something I could pipe text into to get an extraction and/or a simpler pager interface. The browsh repo front page is just insanely impressive[0]. `links` is impossible to query the web for the project, so if you had more guidance on that one, it would be appreciated. [0] https://github.com/browsh-org…
Elinks -dump google.comEarlier quoted context omitted.
VSCode isn’t much different from vim or emacs in terms of functionality: basic text editor that is configured for various tasks by plugins. Especially with the rise of LSP, the difference between VSCode and vim/emacs is basically preference.
> VSCode isn’t much different from vim or emacs in terms of functionality: basic text editor that is configured for various tasks by plugins. Ease of extensibility is a big deal and vscode is much less easy to configure. VSCode doesn't work uniformly throughout the application. In emacs, you'll quickly start to depend on all the places you can use M-r, M-n, and M-p to reverse search history for instance. This is one…
My point is just that the “why would anyone use a ‘text editor’ instead of an IDE” argument makes a little bit of sense when you’re comparing vim/emacs to IntelliJ, but VSCode is just as much a text editor out of the box as vim/emacs. And, despite being newer, it’s relatively uninspired compare to emacs.
Earlier quoted context omitted.
There's a few terminal browsers like w3m, browsh and links that should work for many basic HTML pages.
A full terminal web browser is a bit more than I was looking for, but this is definitely an option. Was thinking more something I could pipe text into to get an extraction and/or a simpler pager interface. The browsh repo front page is just insanely impressive[0]. `links` is impossible to query the web for the project, so if you had more guidance on that one, it would be appreciated. [0] https://github.com/browsh-org…
* http://jdebp.info/Softwares/nosh/guide/commands/console-docb...
It's probably only me but isn't Markdown's main "selling point"/feature the raw files are human readable? Looking at the screenshots, the only thing the "rendering" provides seem to be: 1) syntax highlights on code blocks; and 2) don't need to count the ordered bullets? I guess if you need to verify that your markdown can be rendered (e.g no syntax errors), this would be helpful, but for that use case maybe a markdow…
Markdown can also contain inlined HTML, which is not human readable.