[pull] master from rstacruz:master#12
Open
pull[bot] wants to merge 157 commits into
Open
Conversation
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
In date formatting: `rfc2822` should be `rfc2822`
Added Bash Hackers Wiki link to the Introduction section, as this is just as useful as the other two.
* restart policy * Update formatting Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Co-authored-by: Zed <zed@riper.fr>
New shortcut `:q!` added for quit without checking changes in `vim.md` file.
The `actions/cache`acrion uses the deprecated Node 16 runtime. Upgrading actions/cache should fix this.
Fixes missing code highlighting in half of the Python code snippets. The top half of the page had code examples formatted as code blocks with 4 space character indentations and no syntax highlighting as a result. The bottom half on the other hand, used code blocks surrounded by "```py" formatting brackets which hints to many markdown renders that syntax highlighting should be applied. This unifies the code blocks in the top half of the page to use the same formatting syntax used in the bottom half with syntax highlighting. This change was prompted by requests to add the syntax highlighting in comments on the https://devhints.io/python page.
I was looking for notes and then when i was searching svelte i couldn't see the possible search hits.so i turned autocomplete off now it works like charm.
Adding a page per `packs` documentation on https://github.com/rubyatscale/packs `packs` is a system to modualize ruby projects. --------- Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
[GFM](https://loilo.github.io/gfm-preview/) now supports the ability to embed Base64 encoded images in Markdown.
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
This PR adds: - link to the Heredoc refdoc (always handy for not straightforward concepts) - chapter about Herestring - chapter about Process Substitution (I know it is already tackled in the _Redirection_ chapter but I believe it deserves its own one... Congrats for this cheatsheet, by far my most beloved one ever !! --------- Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Add common keywords to js docs cheatsheets
* use `$()` rather than deprecated `` * illustrate shortcut for builtin read of file without `cat` * don't imply this reads lines, it will split into words by default perhaps the cheatsheet should have a section on IFS, but that's off-topic for this patch. Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
## Summary - Added a new Set Theory section to the vim-digraphs cheatsheet - Includes commonly used mathematical symbols for set theory operations - Follows the existing format and style of the cheatsheet ## Changes - Added Set Theory section with symbols for: - ∀ (forall) - `FA` - ∃ (exists) - `TE` - ∈ (element of) - `(-` - ∅ (empty set) - `/0` - ⊆ (subset or equal) - `(_` - ⊇ (superset or equal) - `)_` - ∩ (intersection) - `(U` - ∪ (union) - `)U` - ⊂ (subset) - `(C` - ⊃ (superset) - `)C` - Removed duplicate set theory symbols from Math section - Added descriptive labels for each symbol ## Test plan - [x] Verified all digraph codes work in Vim - [x] Checked formatting consistency with existing sections - [x] Ensured no duplicate symbols across sections 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Greg OmniMind (claude) <gwgithub23+claude@wierzowiecki.pl> Co-authored-by: Claude <noreply@anthropic.com>
## Summary - Add new cheatsheet for Claude Code AI assistant CLI - Include most commonly used commands first for better UX - Cover interactive mode, file operations, git integration, and advanced features - Add comprehensive sections for workflows, troubleshooting, and best practices - Follow repository formatting conventions with proper YAML frontmatter ## Features Covered - ✅ Interactive mode and core commands - ✅ File operations and git integration - ✅ Advanced features (memory, image analysis) - ✅ Slash commands and productivity features - ✅ Common workflows (code review, testing, debugging) - ✅ IDE integrations and configuration - ✅ Troubleshooting and environment variables ## Test plan - [X] Verify YAML frontmatter follows repository conventions - [X] Check markdown formatting and table structure - [X] Ensure most used commands are prioritized at the top - [X] Validate all sections use proper Jekyll formatting classes - [X] Confirm links and references are accurate 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Le Coq Francis <f.lecoq@jacquetmetals.com> Co-authored-by: Claude <noreply@anthropic.com>
Added cheatsheet for Rclone --------- Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Keys `"*y` _/_ `"+y` should be described as `Copy to system clipboard` and not `Paste to system clipboard`
Admittedly, I'm at a junior dev level, but I believe the code as written is syntactically incorrect. I think that the `:` is required for `msg` to be declared as a variable. I don't believe you can just use the assignment operator (`=`) to declare `msg` as a variable by assigning it the value of `"Hello"` in the 'Go!' language like you can in python, dart, et al. Go! does have type inference but it must be done with the walrus operator (`:=`). Line 49 denotes that this is the `Variable Declaration` section so I believe the `:` preceding the `=` is necessary. On deeper checking, I think this line should be deleted because it's syntactically incorrect and the shortcut for variable declaration and assignment using the walrus operator is already covered below.
Updated FFMPEG page by adding following arguments 1. -ss 2. -t 3. -map 4. -pix_fmt 5. -crf --------- Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
For the screen cheatsheet, I added the copy/scrollback mode.
Updates to the `git-extras` cheatsheet. * Remove non-existent command "git impact" * Update repo location (repo location was moved) * Add additional git-extras commands closes #1858
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )