Hacker Newsnew | past | comments | ask | show | jobs | submit | kps's commentslogin

Maybe when `:!` works the way vi does and POSIX says it must.

Just kidding, that will never happen.


vi compatibility is explicitly a non-goal for neovim

https://neovim.io/charter/


What are referring to, out of interest? Does this apply just to nvim, or vim as well?

In Vim, :! cleans up the tty context and hands it off to the child program, to do whatever it wants, you can open any TUI program and it will work as expected. In Neovim, :! just uses a plain pipe. Actually I believe GVim has the same problem. Since both Vim implementations now have a built in terminal handling stack anyway, I wonder if that could be used to unify the behavior.

Just nvim. Neovim runs :! commands non-interactively, capturing the output in a pipe. vim, on the other hand, suspends itself and runs the command in an external shell.

This isn't a problem, really, for non interactive commands, but causes issues with interactive ones. I personally prefer vim's approach, though not enough to abandon neovim.


Preach! I tried to point this out in the Neovim discord once and was basically told to pound sand. Very frustrating.

My initial issue: https://github.com/neovim/neovim/issues/35258 The interactive issue: https://github.com/neovim/neovim/issues/1496

I really just want a, do the old thing setting. It was simpler and worked better.


:Silent [0] is an effort to work similarly in Neovim to Vim's `:!`

[0] https://gist.github.com/Konfekt/8e484af2955a0c7bfe82114df683...


There's no market for it.

Not real talk.

To have a market for something you need people to find it valuable.

What drove the shift in values?


Some modern phones do DisplayPort over USB C.

I plugged my iPhone 16 into my usb-C docking station the other day to charge it and was pretty surprised to discover it just started mirroring my phone screen. Keyboard worked too!

It depends on the app — mirroring is the default, but apps can do smarter things as well. See for example the NYT crossword app.

QuickTime, when new, was at the forefront of mass-market digital media. The ‘Time’ part referred to synchronized video and audio playback.

What I'd like to see is a lazy person's HOWTO for the last paragraph:

> You could tell Codeberg to push new commits to GitHub, but this allows users to still file PRs and comment on issues and commits 2. Some folks have dealt with this by disabling issues on the GitHub repo, but that is a really destructive action as it will 404 all issues, and pull requests cannot be disabled. Some repos like libvirt/libvirt have written a GitHub Action that automatically closes all pull requests.


Disabling PRs is now possible on GitHub: https://github.blog/changelog/2026-02-13-new-repository-sett...

You can limit them to contributors as well.


Thanks. Doesn't seem to be supported by `gh` yet.

Terry Gilliam's Brazil, California, and geographic Brazil, yes.

My Mac is staying releases back, but iOS26 no longer respects light mode. Since I see astigmatic halation, this will be my last iDevice.

I run light mode on my iPhone and haven't noticed it switching to dark mode in any way. Do you have the automatic mode selection enabled accidentally?

No, this is not switching to dark mode, it's particular system features now being dark only, like notifications, search, control panel, and some other lesser things I don't specifically now remember.

> input is broken under Wayland

Drop the ‘Steam’, it's cleaner. Wayland's raison d'etre is to push frame buffers without tearing. Input is an afterthought.


> Input is an afterthought

This. You need more than graphics to have a windowing system. Wayland team threw out X11, did graphics and left the rest for the others to figure out.


That's odd, I'm using Wayland on my desktop and, for example, Japanese input works 問題ない. Then again, I haven't tried every possible input method/peripheral in existence, so I may just be the one in [some arbitrary large number] who lucked out.

Those were FBI agents. Expect a knock on your door any time now.

It's unfortunate that the US lawyers did not cite the reply given in Arkell v Pressdram.

Arkell v Pressdram was in response to a civil claim that never reached a court, so slightly different. I take the wider point though.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: