From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: Include
Date: Wed, 08 Dec 2021 23:28:08 -0500 [thread overview]
Message-ID: <20211108232808.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
By request, and something folks had talked about before, .ebrc now has an include directive.
include = /home/mylogin/.ebsys/plugins
Include another file, like #include in C, or include() in m4.
This can be used to modularize your edbrowse settings:
mail accounts and filters in one file, plugins in another,
functions in another etc.
However, edbrowse -c only brings up the base config file, and would not provide direct access to these other files.
So it is a matter of tastewhether you like this approach.
I'm trying it out for a while, mostly to make sure the software works,
but I may go back to one .ebrc file.
Also that file is backed up every week so I can recover if I screw up;
if I keep settings in multiple files I have to upgrade my backup procedure.
But some people have a lot of functions, and keeping certain groups of functions in certain files could help keep track of things.
Well, enjoy.
Karl Dahlke
reply other threads:[~2021-12-09 4:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211108232808.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
--subject='Re: Include' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).