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

Use XDG_DATA_HOME on *nix if no ~/.pkgx #1104

Merged
merged 1 commit into from
Jan 30, 2025
Merged

Use XDG_DATA_HOME on *nix if no ~/.pkgx #1104

merged 1 commit into from
Jan 30, 2025

Conversation

mxcl
Copy link
Member

@mxcl mxcl commented Jan 29, 2025

Fixes #1103

Ok(path)
}
} else {
let home = dirs_next::home_dir();
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd love to just move the unwrapping here, since, if this fails, life is pretty much broken. But the map() calls below aren't wrong.

Copy link
Member Author

Choose a reason for hiding this comment

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

I figure if for some reason HOME is unset but XDG_BLAH are we shouldn't fail here. We will fail later though.

@mxcl
Copy link
Member Author

mxcl commented Jan 29, 2025

Error: docs/faq.md:228:1 MD007/ul-indent Unordered list indentation [Expected: 0; Actual: 2]

This markdown linter is fucking junk. This is the third time it has reported completely fine markdown as invalid.

@jhheider
Copy link
Contributor

https://github.com/DavidAnson/markdownlint/blob/main/doc/md007.md

according to https://github.com/DavidAnson/markdownlint/blob/main/README.md#tags, it's in the bullet tag. maybe you want more limited tag application? but it purports to report violations of the CommonMark and Github Markdown specs (note that markdown as implemented is very forgiving, so lints should be considered generally warnings).

@mxcl
Copy link
Member Author

mxcl commented Jan 30, 2025

This is why I have no love for the markdown linting CI steps. I see almost no value, but it adds 2-4 minutes here and there because “reasons” that seem arbituary.

* Fixes #1103
* Ordering is backwards compatible
* Not allowing relative PKGX_DIR which is more sensible and same as pkgx^1
@mxcl mxcl merged commit e9e06fc into main Jan 30, 2025
15 checks passed
@mxcl mxcl deleted the xdg branch January 30, 2025 12:47
@jhheider
Copy link
Contributor

it adds 2-4 minutes here and there because “reasons” that seem arbituary.

i think the two possible solutions are:

  • install the markdownlint plugin for VSCode, so you don't have to wait on CI
  • remove the CI

either should work just fine. i use the first.

@mxcl
Copy link
Member Author

mxcl commented Jan 30, 2025

I’ll install the VSCode plugin

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.

XDG Compliance
2 participants