stormasm

use gpui::*;

pub struct ListExample {
    state: ListState,
    my_data: Model<Vec<SharedString>>,
}

impl ListExample {
    /// Creates the list state from our Model. Since we'll need to do this twice (once when the
    /// view is created, and many times afterwards when our source model is updated), it should

stormasm

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

stormasm

ANSI Escape Sequences

Standard escape codes are prefixed with Escape:

• Ctrl-Key: ^[
• Octal: \033
• Unicode: \u001b
• Hexadecimal: \x1B
• Decimal: 27

stormasm

Overview of Python Virtual Environments

This guide is targetted at intermediate or expert users who want low-level control over their Python environments.

When you're working on multiple coding projects, you might want a couple different version of Python and/or modules installed. This helps keep each workflow in its own sandbox instead of trying to juggle multiple projects (each with different dependencies) on your system's version of Python. The guide here covers one way to handle multiple Python versions and Python environments on your own (i.e., without a package manager like conda). See the Using the workflow section to view the end result.

h/t @sharkinsspatial for linking me to the perfect cartoon

stormasm

# notes
# a .mailmap file needs to be in the root of each repo to aggregate users with multiple email addresses
# we could add users if we need to map multiple email addresses to a single user
# and commit the mailmap file to the repo if we wanted to. Format of the mailmap file is at the
# end of the script.
#
# 1. git clone every repo in the list
# 2. setup folder_prefix to match your system
# 3. setup the proper slash by system (TODO make the slash system agnostic)
# 4. setup the output folder to the path you want it in

stormasm

Introducing the bytes and the bits command.

Commands specifically made for finding and manipulating binary data. Since naming is hard, we may end up changing the name. :)

the bytes command

potential crates for bytes

• https://docs.rs/bytes/latest/bytes/
• https://github.com/cronosun/abin/
• https://github.com/Mackirac/binary_byte
• https://github.com/gmantaos/file-utils

stormasm

Tabled

GitHub repo

Examples

basic

┌─────────┬─────────────┬───────────┬─────────┐

stormasm

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

stormasm

# let config = {
#     filesize_metric: $false
#     table_mode: rounded
#     use_ls_colors: $true
# }
let-env HOME = "C:\Users\us991808"
let-env LANG = "en_US.UTF-8"
let-env LESS = "-FRX"
let-env PAGER = "less"

stormasm

message	e-q resolution
command [alias] exists but parameter [equals] is missing in eq	equals is not a parameter in engine-q
command [alias] exists but parameter [rest] is missing in eq	reset renamed to initial_value
command [all?] exists but parameter [condition] is missing in eq	condition renamed to predicate
command [ansi gradient] exists but parameter [rest] is missing in eq	rest renamed to column path (* space in param name)
command [ansi strip] exists but parameter [rest] is missing in eq	rest renamed to column path (* space in p