5.1.22621.4249 vs "Month of Lunches 4th Edition"

[Query-01]

@Olaf – My first post can be viewed here.

I will annotate and trim some of the excess text (below) …

@Olaf

The screenshot you shared is from a “Windows Terminal” - not from a “PowerShell Console”. That’s why the context menu looks different.

In “Windows Terminal” the properties menu appears with the small down arrow next to the plus for a new tab …

(The screenshot is in German but I think you’ll get the idea. )

Thank you, prior to your reply I did click into and briefly browse around where your image indicates. However I was literally looking for the word ‘Properties’, as stated within the “Month Of Lunche’s” book’s. The word ‘Properties’ is replaced with “Settings”. I expected to see a drop-down menu, your image opens up a pocket sized dictionary of settings; I was not prepared for.

@Olaf

@Query-01

The outstanding question is, how is PSprompt> $Profile seeing, finding or, otherwise pointing to a nonexistent path and/or file, without an error?

If the file exists it will be loaded. If it does not exist it will not be loaded. That’s all.
The file is not a necessary precondition. As I already said - PowerShell will work with its default settings just fine.

I guess you’re overthinking this a lot.

I’ve always been told I over-think things but in this case, it seems like common-sense. I am working within Win-11\Home; with the default PS 5.1. While I have read\skimmed over text about PS running within or on top of ‘Terminal’, I truly did not fully understand what that meant. I would select PowerShell from the ‘Terminal’ menu, then would continue as if --the GUI linked to --and opened up a PowerShell GUI and environment.

As you probably know, when you try to follow a non-existing path or open a non-existing file, Windows will throw an error. Which is what I was expecting, but does not seem to be the case with PSprompt> $Profile; lesson learned. I now have to watch-out for what other instances that may not result in expected output --the way the OS does.

This is just another reason confirming the use of this URL, to learn the PS help-system for the “Win-11\PS 5.1” install. From that URL, I could not grasp some of the basic get-help syntax usage, --which kind-of resulted in similar output behavior, I.E. if the get-help syntax had nothing to output, it would return a blank PSprompt. I then came to this forum, followed the suggestion to acquire “Month Of Lunches” and now, it appears I’m hitting similar speed-bumps understanding basic things; like the non-existing path issue above.

@Olaf

@Query-01

@Olaf – That is exactly what I want to do. Specifically, to customize the PSprompt>.

So what issues do you have? Are you not able to create the folder? Or do you have issues creating the file?
BTW: You should make sure to create the file with the correct name and extension. It is Microsoft.PowerShell_profile.ps1 - not file.pa1 or file.psi

@Olaf – The exact issue I still do not understand is, if the complete path\to\file does not exist, where is PSprompt> $Profile getting populated from? I.E. the output of PSprompt> $Profile is to a non-existing path, which has me looking for something that does not exist.

@Olaf

@Query-01

I have read where it says to create the file.pa1 if it doesn’t exist but, in this case, not only does the file.psinot exist, but its parent directory, also does not exist.

Just out of curiousity: May I ask what background/where you’re comming from?

I have no tenure with scripting or coding. I find scripts that come close to do what I need, research the the respective help-file, tweak until I understand and get the desired results; cmd.exe, “Visual Basic” MS Office. I learn and use as needed.

@Olaf

Why do you want to learn PowerShell? Are you doing an apprenticeship? Do you want to improve your job skills? What’s the goal?

@Olaf @grey0ut – I’m trying to learn the “PowerShell help-system” as it relates to the “Window-11\PS 5.1” default install. From that point I should be able to figure out what other item’s I need to learn and understand as a replacement for cmd.exe. I do not want to focus on a particular script-task,

Respectfully