| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| | |
this is to prevent pinned toots appearing as such when this function is used elsewhere
than for a profile. e.g. the tag search.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
also: profile--relationships-get no longer interactive.
and docstrings for fields insert.
indent "pinned" for pinned toots display
|
| |
| |
| |
| |
| | |
setting this to window-width minus 1 makes text flow work properly for me with
proportional fonts enabled.
|
| |
| |
| |
| | |
clean up fields mastodon-profile--fields-format
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
- view profile (using make-profile-buffer-for).
- user confirm to delete toot.
- better follow/mute/block/profile prompts
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, `mastodon-auth--access-token` unconditionally returns the
value of the `:access_token` key from the response of
`(mastodon-auth--get-token)`. This causes problems when there was an
error getting the token, for example, if you enter the wrong
password. If a token couldn’t be retrieved, the JSON looks like:
(:error "invalid_grant"
:error_description "The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.")
Since there is no `:access_token` key, `mastodon-auth--access-token`
returns `nil`, which results in a broken header in the next request:
Authorization: Bearer
Which causes the whole thing to freeze Emacs until you mash `C-g`.
This commit rewrites the function to handle that case; to explicitly
signal an error for *any* response that isn’t expected; to use
`if-let`, which allows the temporary `token` variable to be
eliminated; uses `pcase` to determine what kind of response was
received; and adds ERT tests for all these cases.
|
| | |
|
| | |
|
| |
| |
| |
| | |
This prevents mastodon.el from locking Emacs and spinning forever.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
- this way you can favorite posts when viewing a profile
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Set a HTTP timeout.
|
| | | |
|
| |/
| |
| |
| | |
This prevents mastodon.el from locking Emacs and spinning forever.
|
|\ \
| | |
| | | |
Rewrite `mastodon-auth--access-token` so it handles errors.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, `mastodon-auth--access-token` unconditionally returns the
value of the `:access_token` key from the response of
`(mastodon-auth--get-token)`. This causes problems when there was an
error getting the token, for example, if you enter the wrong
password. If a token couldn’t be retrieved, the JSON looks like:
(:error "invalid_grant"
:error_description "The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.")
Since there is no `:access_token` key, `mastodon-auth--access-token`
returns `nil`, which results in a broken header in the next request:
Authorization: Bearer
Which causes the whole thing to freeze Emacs until you mash `C-g`.
This commit rewrites the function to handle that case; to explicitly
signal an error for *any* response that isn’t expected; to use
`if-let`, which allows the temporary `token` variable to be
eliminated; uses `pcase` to determine what kind of response was
received; and adds ERT tests for all these cases.
|
|/
|
|
| |
See issue #218 — we mistakenly modified the global value and `mastodon-toot--update-status-fields` makes no sense outside the toot compose buffer.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The package-lint logic is too daft to cope with this (you cannot even mention it in a comment).
We now move the discover functionality into its own package and just mention in the README file how to make use of it.
|
|
|
|
|
|
| |
As pointed out in issue #211 the compiler actually warned the user about `json-array-type` etc. being unused lexical vars.
Let's hope that this fixes the errors reported with reading json.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Visual feedback in the buffer of:
- Number of characters
- Content warning flag
- Posting visibility
- Can't post an empty toot.
- Changing visibility to something other than "public".
Still missing:
- Attaching media
- Enabling the NSWF-flag toggling.
|
|
|
|
| |
* Use the email address of the current user as default
|
| |
|