Chapter 14:
Epilogue:
# I am the Watcher. I am your guide through this vast new twtiverse. # # Usage: # https://watcher.sour.is/api/plain/users View list of users and latest twt date. # https://watcher.sour.is/api/plain/twt View all twts. # https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri. # https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject. # # Options: # uri Filter to show a specific users twts. # offset Start index for quey. # limit Count of items to return (going back in time). # # twt range = 1 194772 # self = https://watcher.sour.is?offset=186674 # next = https://watcher.sour.is?offset=186774 # prev = https://watcher.sour.is?offset=186574
h
autocmd BufNewFile * call s:InsertTimestamp()
inoremap <CR> <Esc>:r!date +"\%F \%T"<CR>A
function! s:InsertTimestamp()
call setline(1, strftime('%Y-%m-%d %H:%M:%S '))
normal! G$
endfunction
Ctrl+Left
to jump a word left, I get 1;5D
in my tt2 message text. My TERM
is set to rxvt-unicode-256color
. In tt
, it works just fine. When I change to TERM=xterm-256color
, it also works in tt2
. I have to read up on that. Maybe even try to capture these sequences and rewrite them.
tt
. But one after the other. The mentions are now automatically filled in. \o/
a
as in answering. What's missing is automatically adding mentions in the message text template. That's gonna be a bit more tricky, though.
inoremap <CR> <Esc>:r!date +"\%F \%T"<CR>A
inoremap <CR> <Esc>:r!date +"\%F \%T"<CR>A
vi
or vim
at the beginning of each line? Like, upon opening like so:
2025-03-20 15:04:03 Blah blah blah blah
2025-03-20 15:04:15 Bleh bleh bleh bleh
2025-03-20 15:04:22 ...
tt
.) Well, it kinda worked. At least appending to the file. But my cache database got screwed up. I do not yet support replies, so the subject and and root hash columns have not been set at all, resulting in a message that is just not shown at all. I gotta do something about that next. The good thing is, though, after simply fixing the two columns the message appeared on screen.
tt
.) Now, this is the second attempt in tt2
.yarnc
. I neither used nor looked at it, though.
read()
. Iâm not quite sure yet if displaying this as I/O wait (or âPSI some ioâ) is intentional or not â but it sure is confusing.read()
. Iâm not quite sure yet if displaying this as I/O wait (or âPSI some ioâ) is intentional or not â but it sure is confusing.