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

[Sweep Rules] Update doc/hurl.nvim.txt with new tips #95

Closed
wants to merge 1 commit into from

Conversation

sweep-ai[bot]
Copy link
Contributor

@sweep-ai sweep-ai bot commented Mar 1, 2024

PR Feedback (click)

  • 👍 Sweep Did Well
  • 👎 Sweep Needs Improvement

I created this PR to address this rule:

"All docstrings and comments should be up to date."

Description

This PR updates the doc/hurl.nvim.txt file with new tips for the hurl.nvim plugin. The following changes have been made:

  • Added a tip to enable debug mode with debug = true for detailed logs. Logs are saved at ~/.local/state/nvim/hurl.nvim.log on macOS.
  • Added a tip about using edgy.nvim to manage layout when using split mode.
  • Added a tip for setting the filetype to sh or bash for .hurl files to enable syntax highlighting in stable versions of Neovim.

Summary of Changes

  • Added the following lines after line 40:
    -- Enable debug mode for detailed logs
    debug = true,
  • Added the following lines after line 45:
    -- Split mode with Edgy
    -- `edgy.nvim` can be used to manage layout when using split mode
  • Added the following lines after line 50:
    -- Syntax Highlighting in Stable Neovim
    -- If using a stable version of Neovim that doesn't support Hurl syntax highlighting,
    -- set the filetype to `sh` or `bash` for `.hurl` files

Copy link
Contributor Author

sweep-ai bot commented Mar 1, 2024

Rollback Files For Sweep

  • Rollback changes to doc/hurl.nvim.txt
  • Rollback changes to doc/hurl.nvim.txt

@sweep-ai sweep-ai bot added the sweep label Mar 1, 2024
Copy link

changeset-bot bot commented Mar 1, 2024

⚠️ No Changeset found

Latest commit: 213a80f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@jellydn jellydn closed this Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant