asymmetric

I agree with sticking to `nix shell`, it makes the most sense. > the name nix shell is confusing since there are also development shells (created by nix develop), which...

That’s true. On the other hand, the cost reduces over time, as more and more results mentioning the new command gain precedence. Or are you suggesting we rename twice, using...

Right, I understand your point. I still think we could reasonably make the choice to go for `nix shell`, since search engines tend to favor newer pages (and official ones)....

@AndersonTorres Done. Should OfBorg be triggered again?

Unfortunately I don’t have time to investigate these puzzling downstream errors, so closing.

Here's a minimal repro case: ``` { description = "foo"; inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-22.05"; poetry2nix = { url = "github:nix-community/poetry2nix?ref=33db1f30d0a4bffdba969f731dc71e67e69038b4"; inputs.nixpkgs.follows = "nixpkgs"; }; }; outputs = {...

pyproject.toml ``` [tool.black] line-length = 100 [tool.poetry] name = "foo" version = "1.0.0" description = "foo" authors = ["foo"] [tool.poetry.dependencies] python = ">=3.9.2,=1.2.0"] build-backend = "poetry.core.masonry.api" ``` poetry.lock ``` [[package]]...

@thiagorp pinning your flake input to 1.31.0 @cpcloud Unfortunately, the problem is still there as of d62ba59f1e28c382665c57203a4b9ad11fd7f449.

@thiagorp I have only tried this with 22.05, not sure what newer versions would work.

Same here: the `SCHEDULED` field is added **above** the `PROPERTIES` drawer, which then renders the item unsyncable. It does seem like an inconsistency in org-mode that the `SCHEDULED` item is...