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

alacritty: upstream is migrating from yaml to toml #4415

Closed
colemickens opened this issue Sep 7, 2023 · 2 comments
Closed

alacritty: upstream is migrating from yaml to toml #4415

colemickens opened this issue Sep 7, 2023 · 2 comments

Comments

@colemickens
Copy link
Member

I've started building tip of alacritty, due to wayland incompatibility issues on newer sway.

It seems that the next release will move from YAML to TOML.

This is just a heads-up. I'll probably hack my HM fork to render TOML, but it might be best for HM to choose yaml/toml based on version.

Copy link

stale bot commented Dec 7, 2023

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

  • If this is resolved, please consider closing it so that the maintainers know not to focus on this.
  • If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

  • If you are also experiencing this issue, please add details of your situation to help with the debugging process.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

@stale stale bot added the status: stale label Dec 7, 2023
@ncfavier
Copy link
Member

ncfavier commented Jan 4, 2024

Duplicate of #3696

@ncfavier ncfavier marked this as a duplicate of #3696 Jan 4, 2024
@ncfavier ncfavier closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants