Delete This Post

This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?

No
Yes
Block This Actor

This action will block this actor and hide all of their past and future posts. Are you certain you want to block this actor?

No
Yes
Block This Object

This action will block this object. Are you certain you want to block this object?

No
Yes
Delete OAuth Client

Are you sure you want to delete the OAuth client [Client Name]? This action cannot be undone and will revoke all access tokens for this client.

No
Yes
Revoke OAuth Token

Are you sure you want to revoke the OAuth token [Token ID]? This action cannot be undone and will immediately revoke access for this token.

No
Yes

#textadept 1 hashtag

wink
wink posted Jan 8, 2026

What happens if you don't read the manual properly?

So I've been using TextAdept as sort of "not as an IDE/Code Editor per se, but a good Text Editor that can also do code" for years (because it's excellent) but I've always been missing VS Code's "Open folder".

So of course I started looking into implementing that but I really couldn't be bothered to dig into the C/C++ code and maybe keep my own fork.

But there's a `~/.textadept/init.lua` and I knew could do a few nice things with its Lua API.

So what I ended up having working:

Run `fd $(dirname current_buffer) | rofi -dmenu -sort -sorting-method fzf && open that file`, but partially in Lua.

But then I discovered "Projects" and also "Quick Open" which kinda does the same, so I now just have a couple lines of code for a function that does `dirname(current buffer's file), provide that editable in a popup dialog (so I can go up), and on submit opens the Quick Open (which has fuzzy search) with that dir as an argument.

And then a shell script to wrap my `fd $1 | rofi ... | xargs textadept` thing for out-of-editor use.

And 90% of it was in the manual. Doh.

#textadept #editors #nih