@dev1ls@texto-plano.xyz claro que la vi, estuvo buena, has visto la pelicula interactiva?
Is there a way to auto-insert a time stamp on 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 ...
vi Complete Key Binding List https://hea-www.harvard.edu/~fine/Tech/vi.html
gg=G and to va", ci", di{... in vim the other day 😆 Life will never be the same, I can feel it. ref
@aelaraji@aelaraji.com Always nice to see another person learning the power of vis “language as a user interface” paradigm. :waves: Hello from a happy Kakoune user!
vim "+normal $", how cool! :-) Thanks @quark!
@lyse@lyse.isobeef.org welcome! :-) I am doing my best to get more acquaintance with vi/vim. I think nano has spoiled me too much. LOL.
There are also a bunch of log messages scrolling by. I’ve never seen this much activity in the log:
Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (149.71.56.69) "GET /external?nick=lovetocode999&uri=https://pagez.co.uk/services/your-own-100-fully-owned-online-vi>
Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (162.211.155.2) "GET /twt/112135496802692324 HTTP/1.1" 400 12 826.65µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (51.222.253.14) "GET /conv/muttriq HTTP/1.1" 200 36881 20.448309ms
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/112730114943543514 HTTP/1.1" 400 12 663.493µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (27.75.213.253) "GET /external?nick=lovetocode999&uri=http%3A%2F%2Falfarah.jo%2FHome%2FChangeCulture%3FlangCode%3Den>
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=error msg="http://bynet.com.br/log_envio.asp?cod=335&email=%21%2AEMAIL%2A%21&url=https%3A%2F%2Fwww.almanacar.c>
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/111674756400660911 HTTP/1.1" 400 12 545.106µs
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=warning msg="feed FetchFeedRequest: @<lovetocode999 http://alfarah.jo/Home/ChangeCulture?langCode=en&returnUrl>
Jul 25 01:37:41 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:41 (162.211.155.2) "GET /twt/112507964696096567 HTTP/1.1" 400 12 838.946µs
Something really weird is going on?
@al4xs@vaporhole.xyz, o modelo você escolhe lá na lista de modelos do ollama, não sei se tem o do chatgpt, mas a lista é gigante, vi que tem até modelo especializado em cálculo matemático
What’s all of this about? one may ask…
Well I’ve been itching to toy around with a BSD on actual hardware and away from the comfort of VMs. NetBSD, FreeBSD, OpenBSD… It doesn’t matter. I just want to “Make it feel… Make it feel alive AGAIN!”
@bender@twtxt.net Yeah I’ve been having this problem for quite sometime now. It boils down to Vi/Vim/NeoVim inserting those line breaks automatically when editing an .eml file (if I can remember the file extension correctly) … I think Jenny makes use of those. I had to delete them manually until I was told that the problem was fixed after I added the charset utf-8; to my nginx config file. I’ll try and fix this next…
@afmnobre@vaporhole.xyz, bem-vindo. Só vi três tweets seus por aqui, era isso mesmo?
@bender@twtxt.net I’m using both machines in English.
Checked my locale and it spits out:
LANG=en_US.UTF-8
LC_CTYPE=“en_US.UTF-8”
LC_NUMERIC=“en_US.UTF-8”
LC_TIME=“en_US.UTF-8”
LC_COLLATE=“en_US.UTF-8”
LC_MONETARY=“en_US.UTF-8”
LC_MESSAGES=“en_US.UTF-8”
LC_PAPER=“en_US.UTF-8”
LC_NAME=“en_US.UTF-8”
LC_ADDRESS=“en_US.UTF-8”
LC_TELEPHONE=“en_US.UTF-8”
LC_MEASUREMENT=“en_US.UTF-8”
LC_IDENTIFICATION=“en_US.UTF-8”
LC_ALL=
🤷🏽 … and that only happens when vi, vim or nvim are launched by Jenny to compose a twt.
OK time to put this to the test, I ended up setting my $VISUAL env
{-here-} variable, so that jenny can launch neovim instead of plain old vi like
{-here-} it is instructed in the code. But as you can see, I still get these
{-here-} wired new lines every ~70th character (marked them with {-here-})
… or is it vi? 🤔
Quiero mantener una sesión por largo plazo (para no tener que estar poniendo el Password todo el tiempo).
Debido a que esta herramienta de twtxt tiene la intención de que cualquier persona pueda auto-hospedar su propio twtxt.txt, ví que lo más ‘fácil’ y universal es tener un servidor con PHP 7.3+, como un Shared Hosting.
Despliegues con Python, Go, etc. podrían requerir más configuración.
Quiero mantener una sesión por largo plazo (para no tener que estar poniendo el Password todo el tiempo).
Debido a que esta herramienta de twtxt tiene la intención de que cualquier persona pueda auto-hospedar su propio twtxt.txt, ví que lo más ‘fácil’ y universal es tener un servidor con PHP 7.3+, como un Shared Hosting.
Despliegues con Python, Go, etc. podrían requerir más configuración.
[R.I.P] Balto, te vi morir atropellado pero no pude hacer nada, buen perro 😢.
@movq@www.uninformativ.de
Aha! Cool! Not just deleting, but proceeding as if the twt is going to be send. If I :q! on vi it will add an empty line. If, instead, I go :x like I normally do, it works as you said—and as I wanted it. Thanks!
@movq@www.uninformativ.de OK, I am on request/question asking mode today. 😋 How do you cancel a twt, or a reply to a twt? Say I hit my reply, and then I change my mind? Right now, even exiting vi is creating an empty line on my twtxt.txt. Is there an obvious way to cancel a twt, reply, or fork that I am missing?
@movq@www.uninformativ.de Ah, I see. I mean, it is not biggie, as normally I just reply to people, so that part works beautifully. A vi/vim script would work, but it is not universal. What if I use joe, or Emacs, or nano? Meh, jenny is awesome as is, thank you for it! ☺️