| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fix endpoint arg in init-sync
|
| |
|
| |
|
|
|
|
| |
this way we can remove these bindings from mastodon mode map
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the confusion came from the three different types of statuses we often
encounter:
- toot
- boost/fave
- notification (of boost/fave/mention)
in notifications, we can't just use -tl--toot-id. it will return the notif's
id, not the base toot's.
so we do still fetch base-toot JSON (formerly 'parent-toot prop), and get
base-toot-id from there, else from toot JSON.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
because we switched to using boost/fave JSON rather than parent, as
'toot-json, replies to these toots were broken (mentions, etc.)
so now we attach both bits of data and selectively pull from each.
|
| |
|
| |
|
|
|
|
|
|
|
| |
to achieve this, in notifications--format-note, we run
notifications--insert-status on 'note' rather than 'status'
handle mentions/reblogs when following from a notif
|
|
|
|
| |
just feedback for when we call it when not on anything
|
|
|
|
| |
reload foll reqs view on accept/reject
|
| |
|
| |
|
|
|
|
|
|
| |
i received an notification (also in other clients/web interface) attached to
no toot. these checks should allow notifications view to display without
tripping up on any such vacant notifs from the server.
|
| |
|
| |
|
|
|
|
| |
finally we now display all types of notifications! it's about bloody time.
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
which was a copy of mastodon-tl--insert-status.
we revert to having just the latter as main function with optional argument.
mastodon-notifications--insert-status just calls it with the arg ID.
the reason we need the difference is to ensure notifications have their own
ID, and not that of the toot the notif refers to, attached as property
"toot-id". then we have all functionality working on notifications, such as
boosting mentions and so on.
|
|/
|
|
|
|
|
|
|
|
| |
previously we had duplication of functions depending on whether we were in
follow requests view or notificaitons view.
now we just check which kind of f-req we have and act accordingly.
main function being `mastodon-notifications--follow-request-process'.
also updates keybindings for both views. we no longer need them included
separately in profile-mode.
|
| |
|
| |
|
| |
|
|
|
|
| |
strictly, the 27.1 dependency is only for proper-list-p in -http.el.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
<some-symbol> <a-list>)`
This is more readable and actually more efficient (maybe) since it
uses `eq` rather than `equal` as a test.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Basically, in Emacs for each file: select all text and
`indent-region`.
- This also removes one redundant comment, and
- fixes an error with json decoding where the `json-read-from-string`
was actually not within the intended `unless` clause (which explains
the warning about "result of (string-equal "" json-string) will be
ignored" which I never understood.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is mostly reflowing / reworkding docstrings to keep within 80
characters limit and adding autoloads.
There are two warning remaining that I don't understand:
- mastodon-async.el:359:16: Warning: reference to free variable
‘url-http-end-of-headers’
- mastodon-http.el:139:8: Warning: value returned from (string-equal json-string "") is unused
When adding autoloads this sorts them for better readability.
|
|/
|
|
|
|
|
| |
- mastodon-tl--notify-user-posts
- mastodon-tl--no-notify-user-posts
- + some schtick in notifications.el to make sure the notifs display ok.
|
|
|
|
|
|
|
|
|
| |
- use it for eg notifications
- this because i suspect sync is sometimes faster.
- with async init*, i often have to press a key to trigger the request
- perhaps good to have both in the code, and choose which to use when
- cd also poss make this a customize.
|
| |
|
| |
|