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

a fix for #2261 #2289

Merged
merged 2 commits into from
Feb 19, 2025
Merged

a fix for #2261 #2289

merged 2 commits into from
Feb 19, 2025

Conversation

seefood
Copy link
Contributor

@seefood seefood commented Feb 11, 2025

this should fix #2261 without breaking any existing value of $LESS

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • If my change requires a change to the documentation, I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
  • I have added tests to cover my changes, and all the new and existing tests pass.

this should fix #2261 without breaking any existing value of $LESS
@seefood
Copy link
Contributor Author

seefood commented Feb 16, 2025

@bmjsmith can you test if this fixes you up?

@seefood
Copy link
Contributor Author

seefood commented Feb 19, 2025

@akinomyoga anything missed here?

Copy link
Contributor

@akinomyoga akinomyoga left a comment

Choose a reason for hiding this comment

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

I'm not sure if the design of setting those environment variables globally would make sense in the first place because it would affect the normal call of less and other applications internally using less to show information (such as git). One can consider setting these environment variables only for man using env as the corresponding ohmyzsh plugin (ohmyzsh/colored-man-pages) does. Or one can consider setting the environment variables locally in a shell function that calls man as the corresponding oh-my-bash plugin does.

That said, that's not this PR's business. I think the fix in this PR is just fine after addressing the following one point. This should be merged after that.

@seefood seefood merged commit 43285e7 into master Feb 19, 2025
13 checks passed
@seefood seefood deleted the ira/fix-2261 branch February 19, 2025 12:45
@bmjsmith
Copy link

@bmjsmith can you test if this fixes you up?

Thank you, yes this works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: man plugin can break less if you already have LESS set in your env
3 participants