You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f102a14
Browse filesBrowse the repository at this point in the historyBrowse files
> Character encoding for input files (default: UTF-8)
58
58
59
-
**--output_encoding**_encoding_
59
+
**-E, --output-encoding**_encoding_
60
60
> Character encoding for output files (default: UTF-8)
61
61
62
+
**--tool**
63
+
> Run in tool mode to convert/process a single data source (.bib) without a .bcf control file
64
+
62
65
**-V, --validate-datamodel**
63
66
> Validate data against the data model
64
67
@@ -68,10 +71,10 @@ Biber reads a **.bcf** (biblatex control file) generated by LaTeX and produces a
68
71
**-q, --quiet**
69
72
> Log only errors; use twice to suppress all output
70
73
71
-
**--trace**
72
-
> Enable low-level tracing for debugging
74
+
**-T, --trace**
75
+
> Enable low-level tracing for debugging (also turns on --debug)
73
76
74
-
**-l, --logfile**_file_
77
+
**--logfile**_file_
75
78
> Write log messages to specified file
76
79
77
80
**--nolog**
@@ -86,8 +89,16 @@ Biber requires a **.bcf** file generated by running LaTeX with biblatex first. T
86
89
87
90
# HISTORY
88
91
89
-
Biber was created by **Philip Kime** and **François Charette**starting in **2009**to address limitations in BibTeX, particularly around Unicode support and advanced sorting. It became the recommended backend for biblatex and is now the standard for modern LaTeX bibliography processing.
92
+
Biber was first written by **Francois Charette**; **Philip Kime**joined the development in **2009**and made it into the full-featured backend it is today. Written in Perl, it addressed limitations in BibTeX, particularly around Unicode support and advanced sorting. It became the recommended backend for biblatex and is now the standard for modern LaTeX bibliography processing.
Copy file name to clipboardExpand all lines: assets/commands/bibtex.md
+49-7Lines changed: 49 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,20 +4,46 @@ Process bibliography references for LaTeX documents
4
4
5
5
# TLDR
6
6
7
-
**Generate**bibliography
7
+
**Process the bibliography**for a document (pass the basename, without the .aux extension)
8
8
9
9
```bibtex [document]```
10
10
11
+
**Process a specific** .aux file
12
+
13
+
```bibtex [document.aux]```
14
+
15
+
**Operate silently**, printing only error messages
16
+
17
+
```bibtex -terse [document]```
18
+
19
+
**Set the minimum** number of cross references for automatic inclusion
20
+
21
+
```bibtex -min-crossrefs=[number] [document]```
22
+
11
23
# SYNOPSIS
12
24
13
-
**bibtex**_aux-file_
25
+
**bibtex**[_options_]_auxname_[.aux]
14
26
15
27
# DESCRIPTION
16
28
17
29
**bibtex** processes bibliography information for LaTeX documents. It reads .aux files produced by LaTeX, looks up citations in .bib bibliography databases, formats them according to a bibliography style (.bst), and generates a .bbl file that LaTeX includes in the final document.
18
30
19
31
The tool is essential for academic writing and managing citations in LaTeX.
20
32
33
+
# PARAMETERS
34
+
35
+
**-terse**
36
+
> Operate silently, printing only error messages.
37
+
38
+
**-min-crossrefs=**_number_
39
+
> Minimum number of cross references required before a crossref base entry is automatically included in the bibliography (default: 2). Set a large value to disable automatic inclusion.
40
+
41
+
**-help**
42
+
> Display help and exit.
43
+
44
+
**-version**
45
+
> Display version information and exit.
46
+
21
47
# WORKFLOW
22
48
23
49
```bash
@@ -52,11 +78,21 @@ pdflatex document.tex
52
78
# BIBLIOGRAPHY STYLE
53
79
54
80
Common styles:
55
-
-**plain** - Numeric citations, alphabetical
56
-
-**alpha** - Alpha-numeric citations
57
-
-**abbrv** - Abbreviated names
58
-
-**unsrt** - Unsorted, citation order
59
-
-**ieeetr** - IEEE Transactions style
81
+
82
+
**plain**
83
+
> Numeric citations, sorted alphabetically.
84
+
85
+
**alpha**
86
+
> Alpha-numeric citation labels.
87
+
88
+
**abbrv**
89
+
> Like plain, but with abbreviated first names, months, and journal names.
90
+
91
+
**unsrt**
92
+
> Like plain, but entries appear in citation order.
93
+
94
+
**ieeetr**
95
+
> IEEE Transactions style.
60
96
61
97
# BIB FORMAT
62
98
@@ -82,3 +118,9 @@ Requires multiple LaTeX/BibTeX runs. Error messages can be cryptic. BibTeX synta
Copy file name to clipboardExpand all lines: assets/commands/biff.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,16 @@ Using **su**(1) can cause permission issues with biff due to terminal ownership
46
46
47
47
# HISTORY
48
48
49
-
The command is named after **Biff**, a dog belonging to one of the developers at the University of California, Berkeley during the development of **BSD 4.0** in the late 1970s. Biff was known for barking at the mail carrier, making the name a fitting choice for a mail notification utility.
49
+
The command appeared in **4.0BSD** (released 1980), written by **John Foderaro** at the University of California, Berkeley. It is named after **Biff**, a dog belonging to fellow Berkeley student Heidi Stettner. The popular story that Biff barked at the mail carrier is disputed by Stettner herself, but the name stuck as a fitting choice for a mail notification utility.
50
+
51
+
On modern systems the notification daemon is part of **GNU inetutils** (as in.comsat), and the biff client typically ships in a dedicated **biff** package on Debian and Ubuntu.
Copy file name to clipboardExpand all lines: assets/commands/bindkey.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,12 @@ To discover a key's escape sequence, press **Ctrl+v** followed by the key at the
70
70
**-p**
71
71
> List bindings for prefix keys
72
72
73
+
**-N**_newkeymap_[_oldkeymap_]
74
+
> Create a new keymap, optionally copying an existing one
75
+
76
+
**-A**_oldkeymap__newkeymap_
77
+
> Create an alias _newkeymap_ that points to _oldkeymap_
78
+
73
79
# CAVEATS
74
80
75
81
Key sequences vary between terminal emulators. Test bindings in your specific terminal environment. Function keys and special keys like Home/End may have different escape sequences depending on the terminal.
@@ -83,3 +89,11 @@ The bindkey command originated in **tcsh** (TENEX C Shell) and was later adopted
Copy file name to clipboardExpand all lines: assets/commands/binwalk.md
+53-18Lines changed: 53 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,13 @@ Analyze and extract firmware images
20
20
21
21
```binwalk -Me [firmware.bin]```
22
22
23
-
**Signature**scan with hex dump
23
+
**Carve**known and unknown contents to disk
24
24
25
-
```binwalk -W [firmware.bin]```
25
+
```binwalk -c [firmware.bin]```
26
+
27
+
**List** supported signatures and extractors
28
+
29
+
```binwalk -L```
26
30
27
31
# SYNOPSIS
28
32
@@ -34,31 +38,54 @@ Analyze and extract firmware images
34
38
35
39
The tool is essential for reverse engineering, security research, and firmware modification.
36
40
41
+
As of version 3 (released 2024), binwalk was completely rewritten in Rust for greatly improved scanning speed, fewer false positives, and more built-in extractors. Several options from the older Python implementation (such as **--dd**, **--hexdump**, **--raw**, and **--disasm**) were removed or replaced.
42
+
37
43
# PARAMETERS
38
44
39
45
**-e**, **--extract**
40
-
> Extract identified files
46
+
> Automatically extract known file types
41
47
42
48
**-M**, **--matryoshka**
43
49
> Recursively scan extracted files
44
50
51
+
**-c**, **--carve**
52
+
> Carve both known and unknown file contents to disk
53
+
45
54
**-E**, **--entropy**
46
-
> Calculate entropy analysis
55
+
> Generate an entropy graph (rendered with Plotly)
56
+
57
+
**-p**, **--png**
58
+
> Save the entropy graph as a PNG file
59
+
60
+
**-a**, **--search-all**
61
+
> Search for all signatures at all offsets
62
+
63
+
**-d**, **--directory**_path_
64
+
> Extract files and folders to a custom directory
47
65
48
-
**-W**, **--hexdump**
49
-
> Show hex dump with results
66
+
**-t**, **--threads**_count_
67
+
> Manually specify the number of threads to use
50
68
51
-
**-D**, **--dd**_type:ext_
52
-
> Extract and rename by type
69
+
**-y**, **--include**_signatures_
70
+
> Only scan for the given signatures
53
71
54
-
**-r**, **--raw**_string_
55
-
> Search for custom string
72
+
**-x**, **--exclude**_signatures_
73
+
> Do not scan for the given signatures
56
74
57
-
**-y**, **--disasm**
58
-
> Disassemble executable code
75
+
**-l**, **--log**_file_
76
+
> Log JSON results to a file ('-' for stdout)
59
77
60
-
**--signature**
61
-
> Custom signature file
78
+
**-L**, **--list**
79
+
> List supported signatures and extractors
80
+
81
+
**-s**, **--stdin**
82
+
> Read data from standard input
83
+
84
+
**-q**, **--quiet**
85
+
> Suppress normal stdout output
86
+
87
+
**-v**, **--verbose**
88
+
> During recursive extraction, display all results
@@ -103,8 +130,16 @@ Extraction may not work for custom formats. Encrypted sections appear as high en
103
130
104
131
# HISTORY
105
132
106
-
**binwalk** was created by Craig Heffner around **2010** for reverse engineering and analyzing firmware images from embedded devices.
133
+
**binwalk** was created by Craig Heffner around **2010** for reverse engineering and analyzing firmware images from embedded devices. It is now maintained by ReFirmLabs. Version 3, a full rewrite in Rust, debuted in 2024.
Copy file name to clipboardExpand all lines: assets/commands/biome.md
+32-7Lines changed: 32 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,11 +57,26 @@ Fast code formatter and linter for JavaScript, TypeScript, and CSS
57
57
**ci**
58
58
> Check for CI environments (stricter mode).
59
59
60
-
**migrate**
61
-
> Migrate from other tools (ESLint, Prettier).
60
+
**migrate eslint** | **migrate prettier**
61
+
> Read an existing ESLint or Prettier config and port its settings into biome.json. Add **--write** to apply.
62
62
63
63
**--write**
64
-
> Apply fixes and formatting to files.
64
+
> Apply safe fixes and formatting to files (formerly **--apply**).
65
+
66
+
**--fix**
67
+
> Alias of **--write**; apply safe fixes.
68
+
69
+
**--unsafe**
70
+
> Also apply fixes marked unsafe (use with **--write**).
71
+
72
+
**--only**_rule_
73
+
> Run only the given lint rule or group.
74
+
75
+
**--skip**_rule_
76
+
> Skip the given lint rule or group.
77
+
78
+
**--error-on-warnings**
79
+
> Exit with an error code when warnings are emitted.
65
80
66
81
**--reporter**_format_
67
82
> Output format: summary, json, github, gitlab.
@@ -80,7 +95,7 @@ Fast code formatter and linter for JavaScript, TypeScript, and CSS
80
95
81
96
# DESCRIPTION
82
97
83
-
**Biome** is a fast code formatter, linter, and more for JavaScript, TypeScript, JSON, and CSS. It is designed as a unified toolchain to replace ESLint, Prettier, and other tools with a single, faster alternative.
98
+
**Biome** is a fast code formatter, linter, and more for JavaScript, TypeScript, JSX, JSON, CSS, GraphQL, and (in newer releases) HTML. It is designed as a unified toolchain to replace ESLint, Prettier, and other tools with a single, faster alternative.
84
99
85
100
Written in Rust, Biome provides exceptional performance - often 10-100x faster than JavaScript-based alternatives. It requires minimal configuration, with sensible defaults out of the box while remaining highly customizable through **biome.json**.
86
101
@@ -93,12 +108,22 @@ The tool integrates formatting and linting into a single pass, reducing overhead
93
108
94
109
# CAVEATS
95
110
96
-
Biome is relatively new and may not support all ESLint rules or Prettier options. Plugin systems are limited compared to ESLint. Some projects with unusual configurations may require adjustments during migration. CSS support is newer and less mature than JS/TS support.
111
+
Biome may not support all ESLint rules or Prettier options, and some projects with unusual configurations require adjustments during migration. Biome 2.0 (2025) added a plugin system and type-aware linting, but the plugin ecosystem is still much smaller than ESLint's. CSS, GraphQL, and HTML support are newer than the mature JS/TS support.
97
112
98
113
# HISTORY
99
114
100
-
Biome emerged from **Rome Tools**, a project started by **Sebastian McKenzie** (creator of Babel) in **2020**. When Rome Tools Inc. ceased operations in **2023**, the community forked the project as Biome under a new governance model. The fork quickly gained traction, maintaining the performance-focused Rust implementation while accelerating development under community stewardship.
115
+
Biome emerged from **Rome Tools**, a project started by **Sebastian McKenzie** (creator of Babel) in **2020**. When Rome Tools Inc. ceased operations in **2023**, the community forked the project as Biome under a new governance model. The fork quickly gained traction, maintaining the performance-focused Rust implementation while accelerating development under community stewardship. Biome 2.0, released in 2025, introduced a plugin system and type-aware linting.
0 commit comments