| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This caused some nicks and bots to be colored as offline if the option
weechat.look.color_nick_offline was enabled because not all nicks and
bots are included in the nicklist. Revert this for now, and see if we
can bring it back later.
This reverts commit 7310fe88d6fbf94d1bda7c10f24fa9e396d80311.
|
|
|
|
|
| |
This option wasn't accounted for when the message rendering was changed
to using blocks in commit 74da303.
|
| |
|
|
|
|
| |
Fixes #550 properly.
|
|
|
|
|
|
|
| |
When a Slack message is linked and unfurled (previewed) the footer
previously contained the channel name for the message, but now it just
says "Slack Conversation" or "Thread in Slack Conversation" instead.
This brings back display of the channel name.
|
|
|
|
|
|
|
|
| |
The commit 74da303 introduced a regression with messages not being shown
as deleted anymore because deleting only changed the text field, and
that's not being used anymore with that commit.
Fixes #897
|
|
|
|
| |
I missed this file in commit 6202a7c.
|
| |
|
|
|
|
|
| |
For some reason these errors were not reported by flake8 before version
6.1.0.
|
|
|
|
|
| |
It can be difficult to find a specific channel if there are thousands
of them in your slack workspace. This enhancement allows you to
filter the channels based on a regular expression.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of just using the text field of a message, use the rich_text
blocks to format the message.
The main reason for doing this was that messages that include images
suddenly started just having "This message contains interactive
elements." in the text field.
There are some other benefits as well:
- It fixes some bugs with multiple formatting styles not being applied
correctly.
- It fixes links in code blocks not being rendered verbatim (but with
text and url, like outside code blocks).
- It fixes code blocks sometimes having newlines after/before ``` and
sometimes not, depending on how the message was sent.
It looks like messages with images are now back to having the proper
text in the text field (for new messages), so this change isn't
necessary to fix that after all (except for for messages in the history
sent in the last couple of days), but since it fixes other issues as
well, it's best to keep it.
There is one bug left when inline code blocks contains links. Then there
will be ` characters before and after the link, which shouldn't be
there, but I'll leave fixing this for later.
Fixes #354, fixes #550, fixes #893
|
|
|
|
| |
Not sure if this ever occurs, but better safe than sorry.
|
|
|
|
|
| |
This line was wrongly indented after the merge conflict resolution in
commit e86e05e.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This flag overrides detction and uses the specified profile path. This
helps when a non-default profile is used for Slack. It also helps if
autodetection fails; accordingly, recommend use of the flag in that
case.
Signed-off-by: Robbie Harwood <rharwood@redhat.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
webappsstore.sqlite seems to be deprecated, and firefox is migrating to
per-page locations. The values inside the database can be
snappy-compressed, so handle decoding with a new dependency on
python-snappy. Suggested by Trygve Aaberge.
Signed-off-by: Robbie Harwood <rharwood@redhat.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Firefox's default profile can have several different name suffixes,
including ".default-release", the legacy ".default", and others for
different release channels. Rather than guessing, just parse
profiles.ini to determine the default path. Suggested by Trygve
Aaberge.
Link: https://support.mozilla.org/gl/questions/1264072
Link: https://support.mozilla.org/en-US/kb/understanding-depth-profile-installation
Signed-off-by: Robbie Harwood <rharwood@redhat.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This makes the code much easier to read in my opinion. It also fixes
some errors about potentially unbound variables.
|
| |
| |
| |
| |
| |
| |
| | |
Although this file exists in the Chromium profile directory, it's empty.
I would assume Chrome/Chromium always uses the LevelDB file, so there's
no point in checking the webappsstore.sqlite file. Doing this allows us
to refactor some code in the next commit.
|
| |
| |
| |
| |
| |
| | |
Chromium encrypted values start with v10, while Chrome values start with
v11. I don't see any reason to check that the prefix is either of these
really, just remove it unconditionally.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
I see no value of having this option, and it's just confusing since the
script is meant for extracting the token.
|
| |
| |
| |
| | |
The script didn't work anymore for firefox after commit c7868cc.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
The script prints usage if you run it with --help, so I don't see a need
for these examples. The examples are likely to get outdated when the
script options are changed, so I rather not have them there.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Add support for cookies decryption for Chrome/beta
* Add support for firefox-snap, and multiple default/custom profiles
paths
* If no token can be found, like no key localConfig_v2 in
webappsstore2, try the best to fetch it from leveldb (or online copy
of it, if locked by running browser). When no luck even with that,
suggest the user to fetch it manually from dev console, and pass it
as an extra argument. This way it still saves some extra cycles for
the script users by fetching d/d-s values, and formatting the
ultimate registration command string.
Not tested on Darwin, leaving this as an exercise for you
Adding Chromium support should be straightforward and can be done in
follow-ups.
Signed-off-by: Bohdan Dobrelia <bdobreli@redhat.com>
Co-authored-by: Bogdan Dobrelya <bogdando@mail.ru>
|
| |
| |
| |
| | |
Fixes #888
|
| |
| |
| |
| | |
Fixes #889
|
| |
| |
| |
| |
| | |
WeeChat in Debian switched to Python 3 in bullseye (currently
oldstable), so the Python 2 instructions shouldn't be necessary anymore.
|
| |
| |
| |
| |
| |
| | |
If I understand https://docs.brew.sh/Homebrew-and-Python correctly,
Homebrew Python installs python3 so you can use pip as described for
"Other".
|
| |
| |
| |
| |
| | |
Pip recommends using `python3 -m pip` instead of just `pip` (and Python
recommends using `python3` rather than just `python`).
|
| | |
|