Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add post: bash tricks #326

Merged
merged 3 commits into from
Feb 19, 2025
Merged

Add post: bash tricks #326

merged 3 commits into from
Feb 19, 2025

Conversation

64J0
Copy link
Owner

@64J0 64J0 commented Feb 19, 2025

Summary by CodeRabbit

  • Documentation
    • Introduced a new guide titled "Bash Tricks" offering keyboard shortcuts and tips to enhance productivity in the bash terminal.
    • The guide covers terminal tab management, command history navigation, and presents shortcuts in both standard and alternative notations, along with an external reference for further reading.

@64J0 64J0 added the post Post idea label Feb 19, 2025
@64J0 64J0 self-assigned this Feb 19, 2025
Copy link

vercel bot commented Feb 19, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
blog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 19, 2025 0:12am

Copy link
Contributor

coderabbitai bot commented Feb 19, 2025

Warning

Rate limit exceeded

@64J0 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 1 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between aa7463a and 42d5858.

📒 Files selected for processing (1)
  • posts/2025-02-18-bash-tricks.md (1 hunks)

Walkthrough

The pull request introduces a new markdown file titled "Bash tricks" dated February 18, 2025. The file provides a collection of keyboard shortcuts and tips for working in the Bash terminal environment, including guidance on creating new terminal tabs, switching between tabs, searching command history, and closing terminal tabs. It presents shortcuts in both standard and Emacs notation and includes an external reference link.

Changes

File(s) Change Summary
posts/.../2025-02-18-bash-tricks.md New markdown file added with sections detailing Bash terminal shortcuts and tips, including external references.

Poem

I hopped along the code lane, swift and neat,
Found bash tricks that make my days complete.
Tabs and shortcuts in a clever, rhythmic beat,
A rabbit’s joy in every line so sweet!
May these changes bring magic to every script I meet. 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

title: "Bash tricks"
date: "2025-02-18"
show: true
tags: ["shell", "bash", "linux"]

Check notice

Code scanning / Remark-lint (reported by Codacy)

Warn when references to undefined definitions are found. Note

[no-undefined-references] Found reference to undefined definition
title: "Bash tricks"
date: "2025-02-18"
show: true
tags: ["shell", "bash", "linux"]

Check notice

Code scanning / Remark-lint (reported by Codacy)

Warn when shortcut reference links are used. Note

[no-shortcut-reference-link] Use the trailing [] on reference links
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
posts/2025-02-18-bash-tricks.md (5)

8-9: Improve Article Usage in Introduction
The sentence “Notes on bash tricks that could help you become more productive by leveraging keyboard instead of using the mouse.” would be clearer with an article before "keyboard".
Proposed change:

-Notes on bash tricks that could help you become more productive by leveraging
-keyboard instead of using the mouse.
+Notes on bash tricks that could help you become more productive by leveraging the keyboard instead of using the mouse.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~8-~8: Possible missing article found.
Context: ...ou become more productive by leveraging keyboard instead of using the mouse. ## Creatin...

(AI_HYDRA_LEO_MISSING_THE)


13-14: Insert Missing Comma for Clarity
The sentence “In order to create a new bash terminal tab using the keyboard one can use the following keys:” would read better with a comma after “keyboard”.
Proposed change:

-In order to create a new bash terminal tab using the keyboard one can use the
+In order to create a new bash terminal tab using the keyboard, one can use the
🧰 Tools
🪛 LanguageTool

[uncategorized] ~13-~13: A comma might be missing here.
Context: ...reate a new bash terminal tab using the keyboard one can use the following keys: - `C...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


21-21: Add Comma for Readability
Consider adding a comma in “And to switch between different terminal tabs one can use:” for improved readability.
Proposed change:

-And to switch between different terminal tabs one can use:
+And to switch between different terminal tabs, one can use:
🧰 Tools
🪛 LanguageTool

[uncategorized] ~21-~21: Possible missing comma found.
Context: ...nd to switch between different terminal tabs one can use: - Alt + tab_number ...

(AI_HYDRA_LEO_MISSING_COMMA)


26-26: Rephrase Section Heading for Clarity
The header “## Searching at the history” sounds a bit awkward. Consider rephrasing it to “## Searching the history” for improved clarity.
Proposed change:

-## Searching at the history
+## Searching the history

31-35: Clarify the “Kill a Tab” Instruction
The instruction “Finally, to kill the terminal you are currently in, the exit command must be enough.” can be rephrased for clarity and conciseness. Consider using a formulation such as “Finally, to close the current terminal tab, simply execute the exit command.”
Proposed change:

-Finally, to kill the terminal you are currently in, the `exit` command must be
-enough.
+Finally, to close the current terminal tab, simply execute the `exit` command.
🧰 Tools
🪛 LanguageTool

[typographical] ~33-~33: It seems that a comma is missing.
Context: ...y. ## Kill a tab Finally, to kill the terminal you are currently in, the exit comman...

(IN_ORDER_TO_VB_COMMA)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 012eb0a and aa7463a.

📒 Files selected for processing (1)
  • posts/2025-02-18-bash-tricks.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
posts/2025-02-18-bash-tricks.md

[uncategorized] ~8-~8: Possible missing article found.
Context: ...ou become more productive by leveraging keyboard instead of using the mouse. ## Creatin...

(AI_HYDRA_LEO_MISSING_THE)


[style] ~12-~12: Consider a shorter alternative to avoid wordiness.
Context: ... mouse. ## Creating new terminal tabs In order to create a new bash terminal tab using th...

(IN_ORDER_TO_PREMIUM)


[uncategorized] ~13-~13: A comma might be missing here.
Context: ...reate a new bash terminal tab using the keyboard one can use the following keys: - `C...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~21-~21: Possible missing comma found.
Context: ...nd to switch between different terminal tabs one can use: - Alt + tab_number ...

(AI_HYDRA_LEO_MISSING_COMMA)


[typographical] ~33-~33: It seems that a comma is missing.
Context: ...y. ## Kill a tab Finally, to kill the terminal you are currently in, the exit comman...

(IN_ORDER_TO_VB_COMMA)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Codacy Security Scan
🔇 Additional comments (2)
posts/2025-02-18-bash-tricks.md (2)

1-6: Front Matter Looks Good
The YAML front matter is well structured and provides the necessary metadata for the post.


36-39: References Section is Clear
The references section is well formatted and the external link is clearly presented.

@64J0 64J0 merged commit b7e413b into master Feb 19, 2025
5 checks passed
@64J0 64J0 deleted the post-bash-tricks branch February 19, 2025 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
post Post idea
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant