book
bash-preexec
Our great sponsors
book | bash-preexec | |
---|---|---|
21 | 8 | |
1,688 | 826 | |
0.6% | - | |
0.0 | 5.0 | |
25 days ago | about 2 months ago | |
Handlebars | Shell | |
MIT License | 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.
book
-
Implement React v18 from Scratch Using WASM and Rust - [1] Build the Project
For more information, you can refer to the Rust and WebAssembly.
-
Hello, I am React Developer who wants to start use wasm in rust.
As a starting point for Rust in general, you should read the book. And if you got some grasp of Rust, you should take a look at the book about Rust and Wasm.
-
WASM: memory.buffer byteLength smaller than the offset of the pointer
I am following the Rust Wasm book. I have the following struct.
- I’ve fallen in love with rust so now what?
-
Any idea about what Figma is using to run Rust/c++ code in browser?
https://rustwasm.github.io/docs/book goes over how to compile to WASM and rendering to a canvas.
-
Rust で WebAssembly (wasm) - Arch Linux + Webpack (Rust 1.66)
Rust 🦀 and WebAssembly 🕸 (英語)
-
Rust for Web for somebody who's never done any kind of WebUI before
I'm a little confused about how Rust fits into your UI-for-a-Python-API thing. Web UIs are typically written in Javascript or something that compiles to Javascript. Compiling Rust to Javascript is a not a common use of Rust at this time. The typical use of Rust in a web application would be the part that runs on the server (the "backend"), not the part that runs in the web browser (the "UI"). While you can write web UIs in Rust, this is a thing better learned after learning the normal way to do it, in Javascript.
-
Compiler option to make all panics be undefined behavior?
AFAIK unwinding in WASM is not a thing: https://github.com/rustwasm/book/issues/76
- What's the best way to generate WASM programmatically?
-
Cppreference-like documentation for Rust?
Honorable mentions: 1. Easy Rust for a general overview of the commonly used features 2. Rust/WASM for developing WASM apps in Rust
bash-preexec
-
Atuin replaces your existing shell history with a SQLite database
Or use the excellent bash-preexec plugin that atuin itself relies on to achieve this in a cleaner way: https://github.com/rcaloras/bash-preexec
-
How to log bash commands in some simple way?
Use this: https://github.com/rcaloras/bash-preexec/
- Is it possible to handle a command before it's passed to the bash command parser?
-
Opppppsss you did it again
Funny you say that when the sketchiest part of this submission is the shell script it uses to intercept every command you run: https://github.com/rcaloras/bash-preexec/blob/master/bash-pr...
I don’t know rust, but the rust files in this repo look very straightforward. (Why wouldn’t it? It’s just matching a few hardcoded commands. It’d be easy in any language)
-
Terminal starting on previous PWD position?
# ~/.bashrc: executed by bash(1) for non-login shells. # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) # for examples # We use preexec and precmd hook functions for Bash # If you have anything that's using the Debug Trap or PROMPT_COMMAND # change it to use preexec or precmd # See also https://github.com/rcaloras/bash-preexec # If not running interactively, don't do anything case $- in *i*) ;; *) return;; esac # don't put duplicate lines or lines starting with space in the history. # See bash(1) for more options HISTCONTROL=ignoreboth # append to the history file, don't overwrite it shopt -s histappend # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) HISTSIZE=1000 HISTFILESIZE=2000 # check the window size after each command and, if necessary, # update the values of LINES and COLUMNS. shopt -s checkwinsize # If set, the pattern "**" used in a pathname expansion context will # match all files and zero or more directories and subdirectories. #shopt -s globstar # make less more friendly for non-text input files, see lesspipe(1) [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)" # set variable identifying the chroot you work in (used in the prompt below) if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then debian_chroot=$(cat /etc/debian_chroot) fi # set a fancy prompt (non-color, unless we know we "want" color) case "$TERM" in xterm-color|*-256color) color_prompt=yes;; esac # uncomment for a colored prompt, if the terminal has the capability; turned # off by default to not distract the user: the focus in a terminal window # should be on the output of commands, not on the prompt #force_color_prompt=yes if [ -n "$force_color_prompt" ]; then if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then # We have color support; assume it's compliant with Ecma-48 # (ISO/IEC-6429). (Lack of such support is extremely rare, and such # a case would tend to support setf rather than setaf.) color_prompt=yes else color_prompt= fi fi if [ "$color_prompt" = yes ]; then PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ' else PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ' fi unset color_prompt force_color_prompt # enable color support of ls and also add handy aliases if [ -x /usr/bin/dircolors ]; then test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" alias ls='ls --color=auto' #alias dir='dir --color=auto' #alias vdir='vdir --color=auto' alias grep='grep --color=auto' alias fgrep='fgrep --color=auto' alias egrep='egrep --color=auto' fi # colored GCC warnings and errors #export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01' # some more ls aliases alias ll='ls -alF' alias la='ls -A' alias l='ls -CF' # Add an "alert" alias for long running commands. Use like so: # sleep 10; alert alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"' # Alias definitions. # You may want to put all your additions into a separate file like # ~/.bash_aliases, instead of adding them here directly. # See /usr/share/doc/bash-doc/examples in the bash-doc package. if [ -f ~/.bash_aliases ]; then . ~/.bash_aliases fi # enable programmable completion features (you don't need to enable # this, if it's already enabled in /etc/bash.bashrc and /etc/profile # sources /etc/bash.bashrc). if ! shopt -oq posix; then if [ -f /usr/share/bash-completion/bash_completion ]; then . /usr/share/bash-completion/bash_completion elif [ -f /etc/bash_completion ]; then . /etc/bash_completion fi fi # If this is an xterm set more declarative titles # "dir: last_cmd" and "actual_cmd" during execution # If you want to exclude a cmd from being printed see line 156 case "$TERM" in xterm*|rxvt*) PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\$(print_title)\a\]$PS1" __el_LAST_EXECUTED_COMMAND="" print_title () { __el_FIRSTPART="" __el_SECONDPART="" if [ "$PWD" == "$HOME" ]; then __el_FIRSTPART=$(gettext --domain="pantheon-files" "Home") else if [ "$PWD" == "/" ]; then __el_FIRSTPART="/" else __el_FIRSTPART="${PWD##*/}" fi fi if [[ "$__el_LAST_EXECUTED_COMMAND" == "" ]]; then echo "$__el_FIRSTPART" return fi #trim the command to the first segment and strip sudo if [[ "$__el_LAST_EXECUTED_COMMAND" == sudo* ]]; then __el_SECONDPART="${__el_LAST_EXECUTED_COMMAND:5}" __el_SECONDPART="${__el_SECONDPART%% *}" else __el_SECONDPART="${__el_LAST_EXECUTED_COMMAND%% *}" fi printf "%s: %s" "$__el_FIRSTPART" "$__el_SECONDPART" } put_title() { __el_LAST_EXECUTED_COMMAND="${BASH_COMMAND}" printf "\033]0;%s\007" "$1" } # Show the currently running command in the terminal title: # http://www.davidpashley.com/articles/xterm-titles-with-bash.html update_tab_command() { # catch blacklisted commands and nested escapes case "$BASH_COMMAND" in *\033]0*|update_*|echo*|printf*|clear*|cd*) __el_LAST_EXECUTED_COMMAND="" ;; *) put_title "${BASH_COMMAND}" ;; esac } preexec_functions+=(update_tab_command) ;; *) ;; esac
-
How Warp Works
Thankfully, most shells provide hooks for before the prompt is rendered (zsh calls this precmd) and before a command is executed (preexec). Zsh and Fish have built in support for these hooks. Though bash does not have built in support for these hooks, scripts like bash-preexec exist to mimic the behavior of other shells. Using these hooks, we send a custom DCS (Device Control String) from the running session to Warp. This DCS contains an encoded JSON string that includes metadata about the session that we want to render. Within Warp we can parse the DCS, deserialize the JSON, and create a new block within our data model.
-
What am I running inside my bash? (2014)
It's attached to the preexec hook of https://github.com/rcaloras/bash-preexec, so is run before every command. This means that everything goes into one easily-greppable file, but is still separable by PID/host machine - since my work has me walking around a large facility, often I'll remember where I was when I did something but not exactly when, so can narrow down by machine.
-
post command hooks
This github repo claims to do the same for bash.
What are some alternatives?
wasm-bindgen-rayon - An adapter for enabling Rayon-based concurrency on the Web with WebAssembly.
alacritty - A cross-platform, OpenGL terminal emulator.
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
trash-d - A near drop-in replacement for rm that uses the trash bin. Written in D
trunk - Build, bundle & ship your Rust WASM application to the web.
shellfirm - Intercept any risky patterns (default or defined by you) and prompt you a small challenge for double verification
wasm-bindgen-rayon - An adapter for enabling Rayon-based concurrency on the Web with WebAssembly.
tlog - Terminal I/O logger
zig-wasm-test - A minimal Web Assembly example using Zig's build system.
LLMShellAutoComplete - Use GPT to complete shell command line using atuin shell history database and terminal screen content as prompt
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.