Recently picked up that an "IDE" is a largely uncustomized, out-of-the-box experience, and that (Neovimmers) call the result of their customizations a "PDE", a "Personal Development Environment" instead.
Made me wonder:
Is the notion that IDE's are what they are, mostly unchangable, a common one?
@ctietze I’m not sure if that’s an accurate way to describe IDEs. Xcode, perhaps, but while Visual Studio is no Emacs, it allows you to configure the UI elements, the colourscheme, the key bindings, set up custom commands, install plugins, etc. I don’t know how common it is to use all these features (I, for one, have barely scratched the surface), but there’s a lot in there.
:syntax match WordsWithNumbers /\w*\d\w*/ containedin=ALL contains=@NoSpell
...but that will also prevent other highlighting from starting inside those words, which may or may not be an issue for you.
If it is an issue, you might be able to get around it by tacking on an extra contains=ALL, but it really depends on the rest of your syntax highlighting as to whether that will improve things or make it worse!
Wait, why is #Neovim loading .vim/after/plugin/foo.vim if the foo plugin isn't installed at all?
(Sharing dotfiles across machines, and I was hoping that /after/ made sure that it's only sourced when the plugin itself is installed on that particular machine.)
I know that I can use exists() to check for a plugin command or whatever to conditionally do things, I was just hoping I didn't have to.
I was today years old when I learned that I can just type the plain small integers when referencing a git stash. For over a decade I've been typing out "stash@{2}" every time. Jeeeeeezuuuusssss.
I've been hearing so much about #Obsidian, I decided to give it a try. I always keep my notes in #Markdown, so an editor that visually renders Markdown as I type it is fantastic.
But is there no way to disable line wrap? I already have "Settings -> Editor -> Display -> Readable line length" toggled off. But long lines still wrap. I'm not seeing any other option that would affect line wrapping.
@atoponce If we’re splitting hairs, it accepts :q! as “correct” but that command will only quit Vim if you only have one window/tab open* AND don’t have any unsaved hidden buffers.
I see a lot of people switching their CapLock key with Esc key to make a more ergonomic to exit interactive mode. But CTRL+C is built-in to both vim (and neovim) to exit interactive
And if you use CTRL+Z to throw vim into the background and the fg command to bring it forward like a professional then it should feel natural
Also stop using arrow keys ❤️
Using hjkl for that matter should be rare, needing to move 1 position should be a rare event
@infektor@ekis it’s because they don’t always do the same thing.
:help i_CTRL-C says, “Do not check for abbreviations. Does not trigger the InsertLeave autocommand event.” Depends on your configuration and habits as to whether the difference is significant.
@ekis@infektor Good point! I should’ve mentioned that too. Behaviour is also subtly different exiting visual mode with CTRL-C. I agree CTRL-[ is the best substitute without config.
Personally (if you’re interested) I remap single taps of Caps Lock to Esc and holding it down with another key as Ctrl as popularised (invented?) by Steve Losh. Takes me a while to get used to computers without that mapping though whenever I have to use them!
VIM is great in many ways but why is the default behavior of "paste" to overwrite the register? This seems like a huge problem that I'm always fighting, every... single... day...
Is there some ancient reason why this was a great default behavior? #vi#vim
@livingcoder Not sure of the original reasoning for it. It’s occasionally useful if you then want to immediately paste the text you just replaced somewhere else. But otherwise, in recent versions of Vim, paste with capital P to do it without overwriting the register.
@sergio_101@ellane Would you mind if I asked what inspired you to try out Obsidian when you were already a (happy?) user of Org Mode? Will you be going back to Org now, or sticking with Obsidian for a bit?
It probably goes without saying that #Vim is a huge part of my life, so I'm deeply saddened to learn of Bram Moolenaar's passing. I use Vim pretty much every day and on every computing device I own—at work and outside it—and it has given me a tremendous amount of joy over many years. It saves me time with its editing model and features and then immediately takes that time right back again with the desire it brings out in me for tinkering. Thank you, Bram.
I’d probably only been using #Vim a year or two when I felt compelled to write this Stack Overflow answer explaining why I thought it was worth learning:
what's a popular command line tool (other than git) that you wish had a clearer / more intuitive UI? I'm thinking of tools like dig which has this IMO pretty arcane output format
@scy wrote about how to use a macro to "surround" words/phrases with some text in vanilla #Vim. Here's an alternative technique for their specific example of changing:
foo bar and .com → \texttt{foo bar} and \texttt{.com}
@benjaminhollon@Anachron iVim has Git built in as an IAP. I haven’t tried it. a-shell & iSH both allow you to mount folders from other apps (e.g. iVim) and allow use of lg2 (a-shell) or git (iSH) (plus they have Vim built in). IIRC all the above is OSS.
@benjaminhollon Feel free to give me a shout if you want more details on any of my suggestions. I wouldn’t classify any of them as “brilliant” (possible exception of Byword, but I don’t think that works for you).