Re: [Autogen-users] Autogen-users post from dedeco.balaco@yahoo.com requires approval

[Bruce K. <bk...@us...>]

On Wed, Aug 29, 2018 at 7:36 AM
<aut...@li...> wrote:
>
> As list administrator, your authorization is requested for the
> following mailing list posting:
>
>     List:    Aut...@li...
>     From:    ded...@ya...
>     Subject: No documentation in one page HTML? Good option for parts of bashrc?
>     Reason:  Post by non-member to a members-only list

I am temporarily locked out of the admin interface. Should be fixed shortly.

> and located here
>
> https://www.gnu.org/software/autogen/manual/html_node/Quick-Start.html#Quick-Start
>
> I want all these (currently) 6 pages in a single HTML page - an option I
> have seen in many other GNU projects' documentation.

The correct link seems to have atrophied:
https://www.gnu.org/software/autogen/manual/

> =======================
>
> Now, the second part of this message.
>
> Is autoopts a good choice for parts of bashrc? I like Bash very much,

I am unclear about what you are wanting. The autoopts project is designed
for facilitating the processing of options for your own program. BASH
parses its own "Run Command" files. So, yes, it will process initialization/
run command files *for your program*, but not for BASH.

> ... but most of what I have in Bash
> are options of subsets of a complex and hard to find documentation big
> set (like things we may use in PS1). I have similar bashrcs in different
> computers, but without known or controlled differences or adjustments.

Typically, you don't put the kitchen sink into one "bashrc" file.
Instead, you have a directory of shell function libraries which you
source from your bashrc file. You might also consider a shared library,
but that is pretty hard core and likely not worth the effort.

> Is autoopts a good option for having a base bashrc for all of them?
No.
> "base bashrc" that I would keep as the central part of all bashrcs I
> have around - and potentially will be the best and updated starting
> point for a new bashrc, for a new computer I start using. And may also
> be an easier path to safely update all my bashrcs with something new I
> just created in one computer, but makes sense to have it in all the
> Bashrcs (or, at least, most of them).

Set up your base machine and develop a way of distributing your
shell libraries to the other machines. Personally, I NFS export the
library from one machine and import it from others.

Good luck.
Regards, Bruce