Just a basic programmer living in California
- JumpDeleted
Permanently Deleted
- JumpDeleted
Permanently Deleted
Yes, I believe this was made for MacOS users. I don't need to see your
.DS_Storefiles! I'm taking some stabs in the dark here. I think that
mkShellgives you gcc automatically, wrapped with configuration for C header lookup paths. I think it does the same setup aspkgs.stdenv. Including gcc explicitly might be shadowing that configured gcc? Try removing gcc from your buildInputs.Another thing to maybe try: I don't see
wlrootsin a package search, but I do see packages with version suffixes, likewlroots_0_19. So maybe try changingwlrootstowlroots_0_19orwlroots_0_19.devThat's almost what I do with my work journal too. Daily logs with an index. A page for deferred tasks. A page here or there for tracking things that need to be done for a given project. I find the index helpful even if I only occasionally put an entry there.
For my personal journal daily logs are the core feature for sure. But I also get a lot of value from a future log, and a page for the current month with a list of events, and scheduled tasks.
I use bullet journals, and I have one for work. It's not exactly the same - instead of my thought process it's mostly what tasks I'm working on each day, and meeting notes. It helps me to organize what I what to get done so I don't have to keep thinking about what I want to get done. It also helps me to get an idea of where my time went, and is a good place to write down anything I want to refer back to. Like when a coworker trained me on a deploy procedure I took notes, and added a line for that page number to my index.
Capitalism is where there is a class of people whose role is to own things. Or put another way, it's where substantial portions of industry are owned by private interests that the public has little oversight over. Money and markets don't necessarily require capitalism. Free markets can exist without capitalism with systems like these:
- All businesses are employee-owned, such as through cooperatives, or employee stock ownership plans where employees own effectively all the stock.
- Businesses are publicly owned via a democratic government, but those businesses are expected to operate in a largely self-sufficient way, and are allowed to compete with each other.
- Public ownership like above, but by industrial unions
Those are forms of "market socialism". A real system is likely to have a mixed economy, such as cooperatives, with some state-controlled or union-controlled industries for cases where trade-offs don't favor market competition.
- JumpDeleted
Permanently Deleted
The Linux kernel development workflow, the purpose for which git was invented, makes use of emailed patches https://docs.kernel.org/process/submitting-patches.html
For Debian on desktop it's common to run Debian Testing, or Unstable. In that case it's a rolling release that is always ahead of Ubuntu.
"We Boyles aren't swimmers. We're burrowers!"
Pretty sure that's my favorite Boyle line.
Yeah, I agree this is reasonable. But there's a difference between creating an alt account for experimentation vs throwing games to get to or to maintain a lower rank. My feeling is that "smurf" typically implies the latter.
When I've done this it's generally done with JWTs where each micro service is configured with a trusted public key that is used to authenticate the JWT. The JWT can be sent to the client when they log in, and used to authenticate all API requests (forwarding the JWT as necessary for service-to-service requests). It's also possible to have a gateway mint JWTs after using some other means to authenticate client requests.
Sometimes service-to-service requests don't have a client request in context to pull a JWT from. In those cases you need another authentication mechanism, like a different signed token, or a shared secret.
It's a gang. The white house has been making up stories that people they arrest are dangerous gang members, notably including Kilmar Ábrego García.
I'm not informed on all the details, but a key difference between the
async_traitmacro and a native async keyword is thatasync_traitgives you that boxed, trait object type. IIUC the thinking is native support should not automatically box futures, which implies it shouldn't usedyneither. UsingBoxanddynis an easy way to make sure the code works no matter what type of future a method returns. But the trade-off is some runtime overhead from heap allocation (due toBox), and dynamic dispatch (due todyn).According to areweasyncyet.rs:
async fn in trait method not stabilized yet
- Workaround is available as an attribute macro: async-trait
With callPackage you need to specify an argument set to the package expression, like this:
nix
callPackage ../brei/package.nix {}Without the curly braces what you have is a function instead of a derivation, which is why the error message says it's an invalid type.
The argument set lets you override inputs to the package set, or pass in arguments that aren't provided by nixpkgs. But if you want all package inputs to be automatically pulled from nixpkgs then you provide an empty set.
There's a pretty thorough write-up here: https://www.reddit.com/r/HobbyDrama/comments/150bkal/comic_strips_so_i_think_it_makes_no_sense/
And remember that every Trek series since TOS has seen a reaction claiming, "This ruins the franchise!" It takes time to make the mental journey from, "this is not what I wanted", to appreciating a new work on its own merits.
That's not an unreasonable answer. But I find this thread a little frustrating. As I see it, it's gone like this:
- phpinjected: Why don't I have a tool to do these non-hierarchical things?
- frongt: You already have a tool that does those specific things.
- hallettj: What could change to make that tool better suited for those non-hierarchical / tagging things?
- frongt: Don't use that tool to do tagging things. It's the wrong tool.
Why bring up hard links if people shouldn't use them for the requested use case? I mean, I do think your original reply was interesting and relevant as a starting point to get to what I think OP has in mind. But that line of thinking does require getting into how to use hard links for a non-hierarchical workflow.
I feel like OP was trying to start a discussion about what might be, if things were different. I tried to reply in the same spirit. I feel like I'm asking, "What if things were different?", and I'm being told "It doesn't work that way." Which doesn't feel like an especially helpful response to me.
We have hard links, but is there any good UI out there for them? I only know of using the
lncommand directly. Or put another way, do you know of anyone who actually uses hard links in a way similar to how a tagging filesystem would be used? What are the obstacles that prevent this use case from being easy or discoverable enough to be in common use?With a tagging system you can remove tags without fear of losing file data. But with hard links you could easily delete the last link without realizing that it's the last link, and then the file is gone.
That relates to another issue: in a tagging system you can look at file metadata to see all of the file's tags. Is there a convenient way to do that with hard links? I see there is
find . -samefile /path/to/one/link, but requiring a filesystem scan is not optimal.Whoops! Guess I was wrong. After some experimenting it looks like the flake system parses, but does not evaluate
flake.nixto read inputs. I also experimented with string concatenation, and that failed with the same error:nix
nixpkgs.url = "github:nixos/nixpkgs" ++ "/nixos-25.05"; # error: expected a string or path, but got a thunkA "thunk" is an expression whose evaluation has been delayed. It's a key piece of lazy evaluation. Remember that every expression in Nix is lazily evaluated.
It looks only literal attribute set, string, and path expressions will work in
inputs. I think that means it is not possible to split inputs over multiple files.Good point! But I think
lib.mkMergeonly merges options in a module system like the ones used in NixOS, Home Manager, and flake-parts configs. In this situation I think the function to use would be lib.attrsets.recursiveUpdate
Global gitignore is for idiosyncrasies of your computer, not for repo-specific stuff. For example if you use an editor that writes in-place backup or swap files (like
.swpfiles with Vim's default settings), or you're on a Mac which writes.DS_Storefiles into every directory, you're going to want those ignored for every repo. That way you can comfortably work with other people's repos, even if they're not configured for your particular setup.The global ignore combines with gitignore files in each repo. So if it's an ignore pattern that everyone working with that repo should have, put it in the repo.