| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
- new bindings for f-req accept/reject (in both notifs and in f-req views)
- check if we are at an f-req before accept/rejecting
- flycheck / docstrings
- fix notifs byline formatting for f-reqs
|
| | |
|
| |
|
|
|
|
|
|
| |
which is a copy of mastodon-tl--insert-status. this makes the 'toot-id of notifications
that of the favoriting/boosting item, rather than the item boosted/favorited.
this ID is needed in order to make loading more older notifications work correctly.
beforehand, the call would be incorrect and the same latest 20 notifications would load.
|
| | |
|
| |
|
|
| |
creates a notifications filter for the 'user' stream, then handles display of notifications, which have their own timeline funs.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Now that we calculate the base toot id, we can ensure that it is unset in notifications that do not represent a toot.
|
| | |
|
| |
|
|
|
|
|
|
| |
Instead of making it search the whole buffer every time to find images to load, give it a range where this work should be done.
We then call this immediately after inserting a single status, notification, ...
There should be no big noticible difference - images might load a tiny bit sooner although I doubt you can see that.
This should be more efficient on large buffers although Alex didn't notice any problems when testing streamed buffers.
We should still do it as it make things easier to understand. I was always worried about these global operations.
|
|
|
- Can now handle notifications (follow reblog favourite and mention)
- Tests for each of the rendering functions are included
- Added keybinding N to mastodon.el for mastodon-notifications-get
- added mastodon-notifications to ert-helper.el
|
