On Thu, Aug 21, 2025 at 11:49:04PM -0700 I heard the voice of Greg A. Woods, and lo! it spake thus: > > Oh, and the last sentence in the '-f filename' description in the manual > page omits [...] > > The internal config is only used if [...] > > Also '--dumpcfg' as you said only dumps the default internal config, and > it does do whether that config would be used or not [...]
Yeah, the manual could probably use a little work in these kinda areas. A lot of it hasn't really been adjusted or restructured since the mostly-mechanical conversion from roff into asciidoc. And it probably should be. Insofar as we can put a "re" in front of the "structured" with a straight face... I think I added --dumpcfg _mostly_ as just a dev tool, but it does also have a use for the case "I've been running with the builtin config, but now I want to tweak one thing about it". Gives you a quick way to get a [presumptively] basically working config to start customizing from. It could be neat if it could also be able to dump out "What I think my current total running config looks like" as a debug tool or something, but that's a loooot of work to do and maintain, I suspect. It's a little unsettling when you start thinking about how much of the config is implicitly order-sensitive, etc... > Also does it really make sense to support the "no workspaces are defined > case"? Pretty sure we had some situation years ago where there was a bug that triggered if you didn't have workspaces set. Wouldn't be too surprising if there were more hiding. Seems like we at least asked a question back then about whether faking up a single workspace shoulda been done. I think there might be a few weird edge cases there that would make it not _quite_ as straightforward as it sounds on the surface, but... -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
