3 ms·
I like stuffing everything which might be important to the context window in there, personally. Saving 50ms on the prompt load sure beats a false negative when
by hiAndrewQuinn 1y ago
I like stuffing everything which might be important to the context window in there, personally. Saving 50ms on the prompt load sure beats a false negative when something goes wrong because I don't even think to ask whether I have the wrong Node version installed or something.
- bayindirh 1y agoWhen starting to work on something, I generally do a sanity check to see that the fundamentals are there and correct versions, then throw that part of the context out of mind, knowing that I stand on firm ground. I found out that with this verify-and-forget step, I work much more efficiently. As a result, my workflow becomes independent of the machine I work on, because I become the tool, not my setup. After that point, only having a "$" at the beginning of the line is enough. Of course everyone have their own choices, and YMMV.
- bredren 1y agoYes. I show the python or node version of currently active venv and venv name. Also, I somehow worked in special characters for Python and other things that get screwed up if I don’t have the right nerd font installed on the system.
- JimDabell 1y agoHow often are you switching these things that you need their values in sight at all times though? Even for cases where I need to use old versions, I don’t need a reminder of that every time I run a command.
- bredren 1y agoAll of the time. Often I'm working with 3-4 different project contexts simultaneously. It isn't that useful but I do glance it when I'm working on dependencies and to ensure the context between a terminal session and pycharm's interpreter match. The information doesn't cloud the prompt for me though, as it is right justified and I don't really think about time to load, as the machines are relatively recent Apple Silicon.