StevenDoesStuffs

Well... yes IItemHandler should handle those things, but currently it can't. The only insert method IItemHandler has takes only one itemstack and requires a slot to be specified. I should...

Also, > B checks if it will be able to fit all 2 stacks in its inventory, by expanding slots or whatever as necessary But you specified a slot, which...

For those reading this discussion after-the-fact, we've moved to discord ([link](https://canary.discord.com/channels/313125603924639766/852298000042164244/1008852589368070385))

The gist of how bash does things is that `bashrc` is for interactive shells, and the profile stuff is for login shells. The point of the diagram was to show...

Currently, login.nu is sourced after config and env. https://www.nushell.sh/book/configuration.html#configuration-with-login-nu > The file login.nu is sourced after env.nu and config.nu, so that you can overwrite those configurations if you need. Just...

Seems like the whole point was this: https://github.com/nushell/nushell/pull/5714#issuecomment-1146805495 > At the moment the login.nu will be sourced after config/env.nu, since I assumed it should be possible to change some of...

I'm sure you've already gotten plenty of ideas about tilde expansion, but I'll give one more in case this idea hasn't been brought up yet. Expand `~` by default everywhere...

If the maintainers can reach consensus on whether this is a good idea, I'd be happy to look into implementing it.

> Sorry, I'm afraid it's conflict with following issue: https://github.com/nushell/nushell/issues/7673 https://github.com/nushell/nushell/issues/4205 https://github.com/nushell/nushell/issues/6993 I don't think this conflicts with any of those, since non-interpolated quoted strings would not ~ expand. For...

Oh one more pathology: ``` let x = '~' ls $x ``` will expand `~`, so currently variables aren't even a way of opting out of tilde expansion anyways.