This repo contains the .NET Core runtime, called CoreCLR. It is an execution engine for .NET apps, performing functions such as IL byte code loading, compilation to machine code and garbage collection. The repo contains the complete up-to-date CoreCLR codebase.
If I enable that auto close option, the behavior is identical to when running from CMD window
It doesn't make me feel bad to not be believed even if I have a memory of something that tells me I should be very confident in it, because I know exactly how little that helps from my wife's point of view.
It's just a logistics thing.
Also think I read about a study that claimed that people's sense of confidence in memories was almost completely unreliable when compared to their actual accuracy.
It would be interesting to know the context for that one. It was a long time ago.
If you typed: display_file code.c <Enter>
it displayed the file.
if you typed: display_file code.c <Shift-Enter>
it generated an editable/navigable form that let you interactively fill in the various args and options (for example -line_numbers or -match <sometext> etc etc)
this is what I'm working on, a version of this to see how far I can get with an attempted version for .Net Core
because every command (just apps) used the same parsing API all commands had this behavior, very very slick to work with.
but in this case we can just say: command_name -form <Enter> to get the same behavior, but a Shift-Enter option would have been slick
... that really sounds like it had deliberate OS support, which seems unlikely here. Also, the thing I would be more concerned with, is how these args were discovered. Either the commands would need to have a meta header as part of the compilation, or some sort of function for reporting/parsing the args separate from the invocation. Both would require OS support.
Im planning on getting a solid version running then I can share on GitHub
Also, I'm way less worried about this version of an "argument" than what I was anticipating was happening.
Indeed, you can tab to any arg and press F1 to get help text
They really deserved credit for it, it was superb and made CLI stuff a doddle, I'm just reinventing it but for Windows with .Net, I can do a few more things too because of this
if you typed: command -file xyz.c +line_numbers
then pressed <Shift-Enter> it builds the form and prepopulates the relevant input fields with your already supplied args
It does a hell of a lot of work of course, but I loved it and actually wrote a solid version in Borland C for DOS
but the src is lost sadly
text typed into the file_name is parsed to conform to file name rules, tab lets you hop from option to option
if you dont use +menu it just does what any other command does, matches up the supplied args with what it expects
this is easier to see with better window colors
To just go back to talking about memories, I would see it as a terrible thing if I felt that it was more important for me to convince people that I was right than for me to understand the best version of their point of view and to look for the idea that's the most helpful for both of us. That having-to-be-right stuff is not one bit enjoyable in the long run for me. Frustration on one hand, hollow victories on the other hand. Both broadcasting how much more important I think I am compared to whoever I was just talking to.