| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \
| | |
| | | |
Fix history timestamp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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)
|
| | | |
|
|/ / |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Regards https://github.com/profanity-im/profanity/issues/1597#issuecomment-930540261
|
| |
| |
| |
| |
| |
| |
| | |
See
https://github.com/profanity-im/profanity/commit/fd9ccec8dc604902bbb1d444dba4223ccee0a092
and
https://github.com/profanity-im/profanity/issues/1597#issuecomment-930426764.
|
|\ \
| | |
| | | |
Improve plugins user experience
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`/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.
|
| | |
| | |
| | |
| | |
| | |
| | | |
There most likely won't ever be Ruby plugins.
Regards https://github.com/profanity-im/profanity/issues/779
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Packagers can package https://github.com/profanity-im/profanity-plugins
or another collection of plugins to `/usr/local/share/profanity/plugins`
(python) and `/usr/local/lib64/profanity` (c).
`/plugins` will list these globally available plugins now along with the
ones thare are installed (`~/.local/share/profanity/plugins`) and loaded.
Regards https://github.com/profanity-im/profanity/issues/945
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | | |
See 3b3a6b7a756e0f162d212249750524b7ce045cea for sourcepath removal.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
Fix https://github.com/profanity-im/profanity/issues/1597
Thanks @debacle.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Set PREF_NOTIFY_MENTION_WHOLE_WORD to true.
If I'm not mistaken the _mucwin_print_mention() / get_mentions()
functions only work correctly since
6bc440c6f7e8c2c40d2d45f5c0decc15821abc8b.
This changed the behaviour for users.
They got notified when their nick was `kaffee` and in the message the
string `kaffeekanne` occured.
Setting `/notify room mention word_whole` corrected this.
So my idea is that only now the mention function work correctly. And to
have a good default behaviour we should set the `word_whole` on by
default.
Regards https://github.com/profanity-im/profanity/issues/1578
|
| | |
|
| |
| |
| |
| |
| |
| | |
alt+f is the default readline shortcut for forward one word.
Regards https://github.com/profanity-im/profanity/issues/1580
|
|\ \
| | |
| | | |
Minor cleanup
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
File obtained from:
https://www.gnu.org/licenses/gpl-3.0.txt
|
|/ / |
|
|\ \
| |/
|/| |
Fix OMEMO devicelist access model by reconfiguring it
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1584
|
|\
| |
| | |
Fix memory leak in chatwin when load history (#1585)
|
|/
|
|
|
|
|
|
| |
_chatwin_history() reassigns msg->plain without freeing previous
string. This leads to memory leak. As a temporary solution, free
replaced string.
Fixes #1585.
|
|
|
|
|
|
|
| |
We use `curl_url()` since e9d587578 which according to
https://curl.se/libcurl/c/curl_url.html is only available in libcurl >= 7.62.0 .
Related to https://github.com/profanity-im/profanity/issues/1581
|
| |
|
|\
| |
| | |
Fix memory leak in accounts_get_login_status()
|
| | |
|
| | |
|