jyn

`bit rebase --squash` sounds good to me :)

I am still seeing this error on master (`bit version v0.6.1`).

I have this in my .inputrc in case it makes a difference: ``` ## enable Alt-arrows "\e[1;3D": backward-word ### Alt left "\e[1;3C": forward-word ### Alt right ```

Another way to trim this down: don't show remote branches with the same name as local branches (maybe make the old behavior opt-in).

@bors try @rust-timer queue

Having environment variables differ for proc_macros between std::env and tracked_env seems ... pretty bad. Is there any way we can make this consistent? I worry this is going to lead...

> Having environment variables differ for proc_macros between std::env and tracked_env seems ... pretty bad Hmm, what I would really love is for *all* accesses to env variables to be...

> Rust-analyzer can't depend on this, so having an unstable hook to override env vars for specific threads is not really an option. I don't follow, sorry - the hook...

I mean, that's true and gets everything working in the short term (if you don't count the breakage it causes before people update their macros). But it means proc macros...

IMO the fix for that is for rustc_sesssion to stop using thread locals ... Isn't there already some solution for this when parallel_compiler is enabled?