| comptime { | |
| const builtin = @import("builtin"); | |
| std.debug.assert(builtin.target.cpu.arch == .x86); | |
| } | |
| pub const Instruction = union(enum) { | |
| mov_: Mov, | |
| int_: Int, | |
| ret_: Ret, | |
| lea_: Lea, |
It is quite often to include C library in Zig project. If it is a shared library, just link it in build.zig.
But if it is not, it can be included as a dependency. Here I use tiny-regex-c as an example.
First, add the c libaray as a dependency.
$ zig fetch --save=tiny_regex_c https://github.com/shahar99s/tiny-regex-c/archive/refs/heads/master.zip
It will show up in the build.zig.zon file. Then include it in build.zig
Terminal emulators typically receive window resize events by installing a signal handler for the SIGWINCH signal. Handling of these signals can create challenges due to their inherently racy properties. Resize events must be synchronized with other application state in a safe manner.
Standard control sequences exist to query the current terminal size from the
terminal and receive an in-band control sequence with the window size. However,
this system requires polling - which is not ideal. Usually, SIGWINCH handling
| #!/usr/bin/env bash | |
| # All my gist code is licensed under the terms of the MIT license. | |
| # GREPDIST | |
| # Print the number of matches in each 10% section of the file | |
| # | |
| # Example with grep: | |
| # $ grep -c 'Napoleon' war_and_peace.txt | |
| # 576 |
Table of Contents
| # Warning: This config does not include keys that have an unset value | |
| # $all is shorthand for $username$hostname$localip$shlvl$singularity$kubernetes$directory$vcsh$git_branch$git_commit$git_state$git_metrics$git_status$hg_branch$docker_context$package$cmake$cobol$dart$deno$dotnet$elixir$elm$erlang$golang$haskell$helm$java$julia$kotlin$lua$nim$nodejs$ocaml$perl$php$pulumi$purescript$python$rlang$red$ruby$rust$scala$swift$terraform$vlang$vagrant$zig$buf$nix_shell$conda$memory_usage$aws$gcloud$openstack$azure$env_var$crystal$custom$sudo$cmd_duration$line_break$jobs$battery$time$status$container$shell$character | |
| format = '$all' | |
| right_format = '' | |
| continuation_prompt = '[∙](bright-black) ' | |
| scan_timeout = 30 | |
| command_timeout = 500 | |
| add_newline = true |
In the following gist I'm going to guide you through the process of installing and booting an entire linux distribution with full desktop environment just like you would have with a classical VM, but with much better performance and much worse isolation :)
The reason why I did this was mainly because it's cool, but also to test new distros with decent graphics performance without actually booting them on my PC.
If you "try this at home" just keep in mind a container is not as secure as a VM, and some of the option we're going to explore will weaken container isolation from "a bit risky" to "totally unsafe" depending on what you choose.
Also, we're going to use systemd-nspawn for containers as it's probably the best fit for our use case and can also boot any linux partition without needing to prepare an apposite container image.
Less go!
| // Grasscutter 2.7.0 GM Handbook | |
| // Created 2022/05/31 17:46:25 | |
| // Commands | |
| sendmessage : Sends a message to a player as the server | |
| setfetterlevel : Sets your fetter level for your current active character | |
| setworldlevel : Sets your world level (Relog to see proper effects) | |
| setstats : Sets fight property for your current active character | |
| give : Gives an item to you or the specified player |
Moved to https://api.fmhy.net
| #!/usr/bin/env python3 | |
| """Flatpak CLI Shortcut Generator | |
| A simple no-argument tool that generates launchers with traditional non-flatpak | |
| command names for your installed Flatpak applications in ~/.local/bin/flatpak. | |
| Does full collision detection and warns you if you forgot to add its output | |
| directory to your PATH. Also overrules the command-line specified in the | |
| ``.desktop`` file if the Flatpak maintainer didn't include support for | |
| command-line arguments. |