Python tooling improvements #34
bvisness
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
setx).orcarootand load tooling from therescripts) or yell at the user that they have done a weird and should remove the source checkout from their PATHIs non-Windows by choice here or because of technical difficulties? Shelling to setx and asking the user to reopen the terminal would be a smoother experience than 13 clicks it takes now.
Oh, I didn't realize you could do that. I'll automate it for all platforms then.
Ok, Windows part done. Doing this for other platforms is actually pretty annoying but hopefully less destructive. The big issue is that I'm not sure where to actually write all the
export PATH="$PATH:foobar"lines to.In Bash it seems that I need to detect one of
.bash_profile,.bash_login, or.profilein order to make sure I'm editing the file that actually gets sourced by the user's shell. For zshell it thankfully seems I can just edit.zshenv.I don't think we need to support any other shells...? The only ones that really matter are the default shells on current platforms. Anyone using a non-default shell knows how to add stuff to their PATH (and also we will never be able to understand their configs).
Could/Should we add this to simplify building apps?
orca build-flags [clang|msvc]that outputs the correct set of flags to build an orca compatible wasm module? (maybe also with-cand '-l' options for people who want to compile and link separately)I'm not sure about that, mainly because I expect we'll want to write more documentation and give more context around those flags. To me it seems like a job for traditional documentation.
Sure we'll want to document that, so for instance I wouldn't want a magical
orca-clangororca-msvccommand. On the other hand it seems convenient to have something that prints the correct include paths and flags, so you don't have to remember them/do it by hand for each platform. Not super important or high priority though!