Re: What?

I have some NNTP issues (I can see much more articles on the public read-only
server I use than on the other one I use to post) ; I almost never post nowadays
and Usenet is really extremely niche now, so I do not want to invest time on
fixing...

I will still answer very quickly to this even if I vaguely feel a trollish tone:

Fine. But what is a "framework prompt" (or a "(shell, not LLM)
prompt framework" if you prefer that)? Since you're suggesting
something (in context of something as simple as a shell prompt)
that is obviously not commonly known, do you mind to explain?
Preferably with a rationale or statement why it shall be used
(as opposed to just defining prompt the usual and simple way).

I'm not interested in bike-shedding on words, we can call them prompt tools or
whatever, I don't care.

"not commonly known" might be true in this newsgroup, but if we look at the
"Github stars" for all the projects I quoted (yes, I know, this metric is not
perfect and can be criticized), they sum up to about 235000, so these projects
clearly have users.

If you have a quick look at the tools (why would the whole "evidence" be on my
side?), what they have in common is:
- they provide much more pieces of info you can choose to display (see right
  column on https://starship.rs/config/) and, importantly, to not display if they
  are not relevant to you
- this info is dynamic and comes from many sources unknown from the shell itself
- they are contextual: the display depends on the current directory and its
  content
- they can be configured in much details and you do not need to fiddle with ANSI
  codes to add colors, for example.


I will stop here on this whole topic, if people hate external prompt tools, they
are free to not use them.

--
DW