According to @eli-schwartz review
https://github.com/profanity-im/profanity/pull/1619#discussion_r760421795:
```
"notifications" is a feature object. When configured with
-Dnotifications=disabled it logs:
Dependency libnotify skipped: feature notifications disabled
[...]
notifications : disabled
and builds without support.
pgp is a boolean option, which IMHO it shouldn't be. When configured
with -Dpgp=false it logs:
Run-time dependency gpgme found: YES 1.16.0
[...]
pgp : false
which is contradictory and misleading, because it was available
and detected, just not required. So it tries to build with PGP
support.
BUILD_PGP is the Makefile.am define, not the C define. This
should set HAVE_LIBGPGME.
Later, in core_sources_c, check if pgp_dep.found() and add
'src/pgp/gpg.c' as an additional source.
```
Fixes https://github.com/profanity-im/profanity/issues/1423
Oldest stanza is fetched like before but now the timestamp is generated by creating date_time_from_iso8601 and then to_local, instead of trusting that the timestamp is in utc.
The procedure previously was stamp = time_val_from_iso8601() then date_time = date_time_from_utc(stamp) then local_date_time = to_local(date_time)
`/plugins install` installs a plugin to
`.local/share/profanity/plugins`.
And also loads it.
When a plugin is loaded it will automatically be added to the `profrc`
file like this:
```
[plugins]
load=my.py;
```
On the next start Profanity will try to load this plugin again unless
`/plugin unload my.py` is called.
If `~/dir` exists profanity exits for me.
Whole code for updating plugins from a dir isn't even implemented. Even
though some messgages suggest otherwise.
Remove this and only allow updating of one file.
Two options to install plugins.
Mention the whole path:
`/plugins install ~/src/profanity-plugins/my.py`
Mention only the plugin name:
`/plugins install my.py`
The latter will look in `/usr/local/share/profanity/plugins/` for the
file and copy it over to `~/.local/share/profanity/plugins`.
At first I was thinking about loading the plugins from the global
location. But users most likely don't want to have all plugins activated
that an admin installs on a system.
Regards https://github.com/profanity-im/profanity/issues/945
I feel like this mostly is confusing people.
Also don't see much value for it.
To me it looks like a regular workflow is like:
```
/plugin install ~/src/profanity-plugins/my.py
```
The whole thing with sourcepath, install (which also loads without
having that described anywhere), load etc is confusing.
Also each plugin file that is present in
`.local/share/profanity/plugins` will then be auto loaded. Which means
after installation.
