| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| | |
just boilerplate copying fave/boost funs for now, better than nothing.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
fixes #264, where if you fave a toot then enter its thread, fave status is lost.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
this user feedback prevents hitting 'n' running tl--more again before toots
have been appended, when what the user wanted was only to naviagate to the
next too after they'd been appended.
running tl--more before toots are appended causes a bug of appending the same
set of toots twice.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
do not use the time stamp of the boosting/faving.
in other views, mastodon-tl--field already handles this by fetching from
'reblog if present, but in notifs, there's no reblog section, and instead
there's a status section. so we fetch from status if present, else fallback to
using --field.
this became necessary when we started attaching the boost/fave json to such
notifs, rather than the json of the boosed/faved toot.
|
|
|
|
|
|
|
|
| |
we just modify the if test to not run in accounts buffers, which means we end
up using the next-toot solution, as was originally the case.
hopefully a profile view will always have a toot or user or sth. else we cd
find a better solution
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
this is more needed now that we have some other buffers like follow
suggestions and follow requests, which want to be able to use these functions.
previously, if any of them were called in these buffers when not on the
correct item, the buffer would reload and duplicate.
ultimately this was probably due to tl--property calls failing, which causes
goto-next-toot to be called, which when it also fails calls tl--more.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- profile statuses: leave as is
- profile followers/following: we extract handle direct from toot-json without
running mastodon-profile--extract-users-handles on the toot, as with user
views there is no toot
|
|
|
|
|
|
|
|
| |
- remove call to goto-next-item from view filters and view foll suggests
tweak init-sync goto-first-item behaviour
remove call to goto-next-toot on profile load
|
|
|
|
| |
cleanup indents
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- they get keymaps that inherit and so override the main masto keymap, which
allows them to still have the basic timeline/view nav functions.
- but we give them next-item rather than next toot so that they never try to
e.g. load for toots into the buffer, which wouldn't work.
- also remove the reference to foll requests view in tl--init as it is not
longer needed.
binding for follow suggestions
remove tab from foll suggests keymap
makes tab work as default, which means you can n/p to next/prev user, while
still being able to tab to user next handle, to visit profile
squashed commit: remove foll suggestions keymap
|
|
|
|
| |
and enable it in "favourites" buffer
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- revert profile--extract-users-handles
- rewrite search--insert-users-propertized to handle raw account JSON, and to
call search--get-user-info itself, so we can add full acct JSON to each user
displayed and use it for follow-user etc.
- and to choose how we want to follow users, we edit
tl--interactive-user-handles-get to work differently depending on context:
- poss contexts are "follow suggestions" view, search results, and profiles
displaying a user's followers/followed users.
|
| |
|
|
|
|
| |
This reverts commit 787f18dcff2ee7a4c5a5cbf331f4e2d26997e1cc.
|
|
|
|
| |
This reverts commit 48a89e518d0a84d4b81c223c9e8cf151df619b1f.
|
| |
|
|
|
|
| |
suggestions fix fun names(!)
|
|
|
|
|
|
|
|
|
| |
this means that we only do the propertizing when we are actually doing an
author byline,
docstring for add-author-bylines
it also needs renaming
|
| |
|
|
|
|
| |
fix remnant call to goto-next-filter
|
|
|
|
| |
rather than using goto-next-toot, which loops when we have no items in buffer
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- separate goto-next/prev-filter commands
- we use properties toot-id and byline so the navigation works, calqued on
- goto-prev/next-toot
- error handle no word or context supplied
- reload filters view on create or delete
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|