notify
pulldown-cmark
notify | pulldown-cmark | |
---|---|---|
10 | 8 | |
2,505 | 1,923 | |
1.5% | 1.6% | |
8.0 | 9.1 | |
17 days ago | 8 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | MIT License |
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.
notify
-
Needing Additional Inputs on an Implementation of an Asset Manager with Hot Reloading Support
To support hot reloading, the asset manager definitely has to have some watcher thread, but I have that part dealt with already since I have decided to utilize notify. The other half is to find a way to reload all assets that have changes as determined by the watcher thread. What I am not sure about is how to implement this in a Rustic fashion and with clean architecture while also considering the fact that asset pointers may be held by other objects (such as an object representing an OpenGL program object).
-
FIM v0.4.6 - Realtime File monitoring tool
It is a great question. We have based the development on a library called notify, kudos to https://github.com/notify-rs/notify. This library adds a layer of abstraction to each system. It implements kernel-specific hooks as you mentioned. In some cases like Audit extended data, we have developed an integration that detects changes on the Audit log file and processes the given information including a lot of information into Linux systems. We have plans to include it in Windows as well.
-
Building a static site generator in 100 lines of Rust
In order to detect files changes, we use hotwatch, a simple wrapper over notify that will allow us to save a few lines.
- Let Rust detect changes in the Markdown file and generate HTML.
-
Track what process modify file
The notify crate uses the inotify API on Linux. However, it's probably not what you want, since one of its limitations is:
-
Hey Rustaceans! Got an easy question? Ask here (48/2021)!
If you want to build this yourself, you'll want to build on something like notify - there are libraries like linemux built on top of it that will do a lot of this for you too.
-
Async file watcher, like notify-rs
Hey rust community, I'm currently writing a small app using Tokio, but running into a problem when trying to add a file watcher to it. I looked into available crates and found https://github.com/notify-rs/notify to be a good option, though it only exposes a sync interface.
-
Effectively monitoring very large number of files
I'm most well versed in Python so I started with that and eventually ended up with a POC using watchdog, but the program took more than a day and a half to traverse everything and register all of the watches. I've been trying to learn Rust for a while, and decided to perhaps use this as an excuse to try something 'real' and not just a learning exercise. I found the notify crate (https://github.com/notify-rs/notify) and basically copied their example listed on their GitHub, but even this takes about 16-18 hours to place all the watches before it starts processing events. I did not see any obvious ways to enable asynchronous or async/await code in notify, so I don't know of a way to parallelize the disk I/O with this approach.
-
Proper way of reading a constantly mutating file?
The notify crate is probably what you're looking for. It uses inotify on linux by default.
- Notify: Cross-platform filesystem notification library for Rust
pulldown-cmark
-
CryptoFlow: Building a secure and scalable system with Axum and SvelteKit - Part 3
As a platform that allows expressiveness, we want our users to be bold enough to ask and answer questions with either plain text or some markdowns. Compiling markdown to HTML in Rust can be done via the pulldown-cmark crate. We used it in this utility function:
-
Building a high performance JSON parser
I also really like this paradigm. It’s just that in old crusty null-terminated C style this is really awkward because the input data must be copied or modified. But it’s not an issue when using slices (length and pointer). Unfortunately most of the C standard library and many operating system APIs expect that.
I’ve seen this referred to as a pull parser in a Rust library? (https://github.com/raphlinus/pulldown-cmark)
- Let Rust detect changes in the Markdown file and generate HTML.
-
Show HN: A Graphviz Implementation in Rust
Really glad to see this! Really want an easy way to render graphs in Rust without resorting to the graphiz binary.
What is the current status? Not seeing it listed anywhere, like if there are features that are not supported or if it uses certain layout algorithms but others are desired.
Would you be willing to make a `[lib]` available? I see you have a `lib.rs` but it'd be great if using it didn't require pulling in `[[bin]]` dependencies (you can mark them as optional and mark `required-features` on your bin like pulldown-cmark does [0] or split it into a separate crate in a workspace). It'd also be good to find an available name for the lib and get it published (looks like someone might be squatting on `layout`).
[0] https://github.com/raphlinus/pulldown-cmark/blob/master/Carg...
-
Using Rust with Elixir for code reuse and performance
Author here. I actually was not aware of cmark.ex - thanks for pointing it out.
In this case the code reuse was more important than pure native speed. We already had a Rust library that used pulldown-cmark [1] with some custom tweaks that we wanted to duplicate. Maybe this behavior could have been copied using cmark.ex too (we thought about doing this in pure Elixir, as mentioned in the post), but given how straightforward Rustler made integrating our existing code, this seems like the better choice.
[1] https://github.com/raphlinus/pulldown-cmark
It turned out that making the most popular Elixir Markdown processor, Earmark (originally written by Dave Thomas) and pulldown-cmark, a Rust Markdown processor, produce the same output was going to be difficult. We also required some customization that was not available in both libraries.
-
What are some examples of particularly well written crates?
The crate that's closest to production quality code is pulldown-cmark, but I don't hold it up as an example of well-written code, because it's not particularly easy to understand and there's a lot of very low level code to consume the CommonMark syntax - that helps with code bloat and compile time, but not clarity.
-
What are the Markdown features/extensions enabled in mdbook?
The Markdown processor is pulldown-cmark, which supports these extensions:
What are some alternatives?
rust-fuse - Rust library for filesystems in userspace (FUSE)
mdBook - Create book from markdown files. Like Gitbook but implemented in Rust
fd - A simple, fast and user-friendly alternative to 'find'
nimler - Erlang/Elixir NIFs in Nim
linemux - Asynchronous tailing library in Rust
doctave - A batteries-included developer documentation site generator
redbpf - Rust library for building and running BPF/eBPF modules
cmark - CommonMark parsing and rendering library and program in C
path_abs - ergonomic paths and files in rust
rust - Empowering everyone to build reliable and efficient software.
dutree - a tool to analyze file system usage written in Rust
cmark - 💧 Elixir NIF for cmark (C), a parser library following the CommonMark spec, a compatible implementation of Markdown.