heirloom-ex-vi
src
heirloom-ex-vi | src | |
---|---|---|
6 | 746 | |
59 | 3,063 | |
- | 1.4% | |
0.0 | 10.0 | |
5 months ago | 4 days ago | |
C | C | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
heirloom-ex-vi
- Ask HN: What tools are you a 10/10 on?
-
OpenVi: Portable OpenBSD vi for Unix systems
Using Carsten Kunze's actively maintained continuation of Gunnar Ritter's (outstanding) traditional ex/vi project is highly recommended. See https://github.com/n-t-roff/heirloom-ex-vi/.
The parent project on SourceForge hasn't had any activity for 15 years, nor a release in 17+ years, but still contain various known bugs, all of which are fixed in Carsten Kunze's project.
-
POSIX command line editing standard?
Attempting this clone of traditional vi from GitHub instead of SourceForge (the SF version lacked libuxre which was available on the GH version), it looks like heirloom ex also cleared the screen, unlike ed(1).
-
The Unix EX Editor by Bill Joy (Basics)
I came across a more recently updated copy of that code which works with modern terminals "out of the box", and includes other bugfixes: https://github.com/n-t-roff/heirloom-ex-vi
src
- OpenBSD 7.3 を 7.4 へ アップグレード
-
OpenBSD Upgrade 7.3 to 7.4
The OpenBSD project released 7.4 of their OS on 16 Oct 2023 as their 55th release 💫
-
OpenBSD System-Call Pinning
Well since https://www.openbsd.org/ still says
> Only two remote holes in the default install, in a heck of a long time!
I'm assuming not, but I could always be mistaken.
- Project Bluefin: an immutable, developer-focused, Cloud-native Linux
-
From Nand to Tetris: Building a Modern Computer from First Principles
> building a cat from scratch
> That would be an interesting project.
Here is the source code of the OpenBSD implementation of cat:
> https://github.com/openbsd/src/blob/master/bin/cat/cat.c
and here of the GNU coreutils implementation:
> https://github.com/coreutils/coreutils/blob/master/src/cat.c
Thus: I don't think building a cat from scratch or creating a tutorial about that topic is particularly hard (even though the HN audience would likely be interested in it). :-)
-
OpenBSD – pinning all system calls
> I don't know how they define `MAX`, but I'm guessing it's a typical "a>b?a:b"
Indeed: https://github.com/openbsd/src/blob/master/sys/sys/param.h#L...
> Then `SYS_kbind` seems to be a signed int.
It's an untyped #define: https://github.com/openbsd/src/blob/master/sys/sys/syscall.h...
I believe your whole analysis is correct, that running an elf file with an openbsd.syscalls entry with .sysno > INT_MAX will allow an out-of-bounds write.
- Une nouvelle mise à jour de Systemd permettra à Linux de bénéficier de l'infâme "écran bleu de la mort" de Windows, mais la fonctionnalité a reçu un accueil très mitigé
-
tmux causing ANSI color-response garbage on attaching?
I can reproduce it. And this is the commit that causes the issue: https://github.com/openbsd/src/commit/d21788ce70be80e9c4ed0c52c149e01147c4a823
-
Sudo-rs' first security audit
This doesn’t really change your conclusion, but I think that’s the wrong file. This is the real doas afaict: https://github.com/openbsd/src/blob/master/usr.bin/doas/doas...
Still just a tidy 1072 lines in that folder though.
I spent 5 minutes staring at your file trying to understand how on earth it does the things in the man page, but of course it doesn’t.
-
OpenBSD: Removing syscall(2) from libc and kernel
OpenBSD developers are making serious effort to kill off indirect syscalls, the base system is completely clean, take a look at the work Andrew Fresh did to adapt Perl. He write a complete syscall "dispatcher" or emulator for the Perl syscall function so that it calls the libc stubs.
https://github.com/openbsd/src/commit/312e26c80be876012ae979...
The ports tree is also being cleansed of syscall(2) usage, until they're all gone.
msyscall, pinsyscall, recent mandatory IBT/BTI, xonly. OpenBSD is making waves, but people aren't really seeing them yet.
What are some alternatives?
nvi2 - A multibyte fork of the nvi editor for BSD
cosmopolitan - build-once run-anywhere c library
OpenVi - OpenVi: Portable OpenBSD vi for UNIX systems
bastille - Bastille is an open-source system for automating deployment and management of containerized applications on FreeBSD.
neovim - Vim-fork focused on extensibility and usability
buttersink - Buttersink is like rsync for btrfs snapshots
AppGrid - macOS window manager with Vim–like hotkeys
PHPT - The PHP Interpreter
pEmacs - pEmacs - Perfect Emacs
Joomla! - Home of the Joomla! Content Management System
multipass - Multipass orchestrates virtual Ubuntu instances
ctl - The C Template Library