macOS build support

[ebraminio]

Currently trying to build it in e8d40f6 using rustup install nightly and cargo build --config .cargo/release.toml --release in macOS results in,

$ rustc --version
rustc 1.89.0-nightly (4d051fb30 2025-05-18)
$ cargo build --config .cargo/release.toml --release
   Compiling edit v1.0.0 (/Users/ebrahim/edit)
error[E0425]: cannot find function `ppoll` in crate `libc`
    --> src/sys/unix.rs:202:33
     |
202  |                 let ret = libc::ppoll(&mut pollfd, 1, &ts, null());
     |                                 ^^^^^ help: a function with a similar name exists: `poll`
     |
    ::: /Users/ebrahim/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libc-0.2.171/src/unix/mod.rs:1418:5
     |
1418 |     pub fn poll(fds: *mut pollfd, nfds: nfds_t, timeout: c_int) -> c_int;
     |     --------------------------------------------------------------------- similarly named function `poll` defined here

error[E0425]: cannot find function `__errno_location` in crate `libc`
   --> src/sys/unix.rs:228:30
    |
228 |                 match *libc::__errno_location() {
    |                              ^^^^^^^^^^^^^^^^ not found in `libc`

error[E0425]: cannot find function `__errno_location` in crate `libc`
   --> src/sys/unix.rs:307:35
    |
307 |         let err = unsafe { *libc::__errno_location() };
    |                                   ^^^^^^^^^^^^^^^^ not found in `libc`

error[E0425]: cannot find value `ELIBACC` in crate `libc`
   --> src/sys/unix.rs:410:50
    |
410 |             .ok_or_else(|| errno_to_apperr(libc::ELIBACC))
    |                                                  ^^^^^^^ not found in `libc`

error[E0425]: cannot find value `ELIBACC` in crate `libc`
   --> src/sys/unix.rs:426:39
    |
426 |             Err(errno_to_apperr(libc::ELIBACC))
    |                                       ^^^^^^^ not found in `libc`

error[E0425]: cannot find function `__errno_location` in crate `libc`
   --> src/sys/unix.rs:568:54
    |
568 | ...unsafe { *libc::__errno_location() })) } else { Ok(ret) }
    |                    ^^^^^^^^^^^^^^^^ not found in `libc`

For more information about this error, try `rustc --explain E0425`.
error: could not compile `edit` (lib) due to 6 previous errors

I wonder however how there isn't a mention of this in #30 I assume that one runs the program remotely or in a container not natively in macOS, which I wish the macOS native one also happens.

[lhecker]

I considered porting it to macOS to be part of #30 but I'd be happy to track it separately here. The reason it doesn't already work on macOS is simply because I currently don't own a desktop device from Apple. If you want to give it a try, I'd be happy to accept a PR for it! Otherwise, I'll try to fix it as soon as I get a chance.

[XinyueZ]

pls make it

[kallebysantos]

I was eager to contribute too, but without osx support is complicated 🫠

[SuperKenVery]

There are tons of existing rust crates that does stdio or memchr in a cross-platform manner. Why did we manually call libc and write unsafe code?

[lhz07]

There are tons of existing rust crates that does stdio or memchr in a cross-platform manner. Why did we manually call libc and write unsafe code?

Microsoft's love for libc😅

[lhecker]

Regarding memchr: Because this project's memchr is faster for our use case of seeking line feeds in documents. In the future it could be even faster by using HADD for counting newlines (= even more custom SIMD code).

It should not come as a surprise to anyone here that fast software requires bespoke code. If you find this interesting, please come and join me tinkering in this project! If you consider this silly, that's fine too. I consider this a great learning opportunity.

Regarding stdio, that's primarily a hold-over because this project initially wasn't written in Rust. However, I would likely have written my own stdio code regardless, because the core to a text editor is pretty much 50% editing and 50% IO, so I think a tight integration with the IO portion is intrinsic to writing a coherent experience.

[reynoldskr]

It does launch with the basic changes in #72, but I notice it has the same issue as #154 - the arrow keys and tab are dead, so no keyboard navigation on the dialogs for you.

[DHowett]

The dialog issue is #36. The arrow keys are likely fixed by #159.