What a coincidence, I just discovered this tool yesterday. It made me really happy how a tool so simple makes such a huge difference in terms of how smooth it is to solve a problem, compared eg with using bluetoothctl.
It also occurred to me that there's a real value to tuis vs guis which is that since they're simpler to build with the same developer effort you can build more tools. I remember the dwarf fortress guys saying this in their interview, that they had at some point a similar game to DF but in 3d, but at some point they realized that by not wasting effort building the graphics part of the game they saved time to focus on what mattered.
If I have one tiny criticism about bluetui is the annoying fonts. I understand what they're trying to do: with more glyphs you can increase the density of information. But the thing is it's not really necessary in this case. Like someone else commented, there's plenty of white space. I know to some people it feels like eye candy, but to me the emojis sprinkled in the text are an eye sore.
bluetui author here.
> It made me really happy how a tool so simple makes such a huge difference in terms of how smooth it is to solve a problem,
Happy to hear that :)
> if I have one tiny criticism about bluetui is the annoying fonts
You suggest to get rid of the icons ? what if they can be disabled in the config, will that fix the issue for you ?
> there's plenty of white space You can set the window width from the config file (width = positive integer) if you don't want the TUI to be responsive.
I think the icons are cool.
Emoji in text is annoying, but this isn't a page of text, it's a UI element, and that can make something clear especially if you're connecting a device whose name is unknown, but you know it's a speaker, or whatever.
So having the option to enable / disable is better than taking away the icons, in my opinion.
Absolutely this. Particularly when there might be a few unnamed devices, but you know your devices is a particular device class, you can guesstimate the correct device based on its class, and the icon is extremely useful for this!
Hi bluetui author. I just discovered your app last week, just wanted to say it is great.
I truly like this new generation of command line utils (I have bat, eza, etc aliased to things like cat and ls) and TUIs like yours. TUIs in particular: having grown up with DOS apps, then graduating to using Pine for email on a shell account, they are nostalgic, but also just super fast and practical. And I like having an option in between the command line and config files and a full-blown GUI app (which, on Linux, might look like any old random thing anyway).
> what if they can be disabled in the config, will that fix the issue for you ?
I mean if you're offering, I would love that.
And thank you for releasing under GPL. <3
sure, feel free to open a github issue and I will do my best to implement it asap :)
Of all the Rust stuff that I've seen on HN, this is the first one that makes me go "maybe I should learn Rust". Not for the performance aspect, but because it seems so neat to be able to compile to a binary. I went to the releases page, I downloaded bluetui-x86_64-linux-gnu, and it works.
From your comment, I'm assuming you're mostly familiar with interpreted languages. Chances are that you know JS/TS. If that's the case, I suggest that you give Go a go. The learning curve is way softer than Rust's and it's not too uncomfortable to someone who already knows TypeScript. And the advantage of Go over Rust is that the compile time is much, much shorter.
I went from Bash to Go as a system admin, and eventually built something with Rust too, so I can definitely confirm that the Go learning curve is softer than Rust.
I still think it's better to learn Rust
I only watch the go part, and I'll say that in 3 years working with I might have had at most 3 times nil pointer crashes in prod, in which took about 30 min between getting fixed and deployed.
There are linter which helps prevent most of if not all crashes (just keep in mind to run linting and compile the binary it would still be ages faster than anything rust I have ever compiled). His argument is weak, and not simple.
I'll give that type system in golang is too simplistic sometimes, and a more complex could help to express better some use cases.
Still go for a person coming from a interpreted language is a solid choice by being MUCH MUCH simpler.
Agree. I immediately remembered k9s[1], a TUI to manage Kubernetes workloads.
It is written in Go as well.
Why not C, C++, Go or any other compiled language? What made you want ot learn rust?
There's also a program in Go which does almost the same: https://github.com/bluetuith-org/bluetuith
I don't usually comment on these things. But this is phenomenal. I really like that the person that did this thought about a simple space for connect and enter for disconnect. I use rofi based tool whenever I don't feel like using my mouse and frequently disconnect because I toggled something that was already connecting.
The same happens when connecting or disconnecting from VPN using the nm applet. This is a simple but extremely useful way of separating two states.
Bluetui author here Happy to hear that :)
Have you considered a network manager? Weirdly enough I have no trouble connecting to a Bluetooth device via bluetoothctl, I can never remember how to disable wifi, or set a static ip though
> Have you considered a network manager?
I've used "nmtui" on Linux for many years to do this. "nm" = "Network Manager".
Nice work. Ive also build a TUI over blueutil (https://github.com/toy/blueutil) for MacOs:
https://github.com/Zaloog/blueutil-tui
Its written in python using the textual framework and displays the connections inline in your Terminal.
What is with this wave of Text User Interface applications everywhere; and why does dev go through this type of cycle so often? Is it just new gen type behavior, so around 2030 we'll see a new wave of whatever and whatever?
I refuse to be old man who yells at clouds, but I think just like the new gen can't help what comes, neither can I. I just feel so old sometimes because most of the "new ideas" aren't really at all; they just have a different language to describe the same thing.
Lots of language have pretty good tools for making TUIs.
There's a good ratio between the time it takes to implement a TUI and its usefulness.
Writing a GUI with equivalent functionality would typically be a lot more work, with no gains at all. Er, except maybe touchscreen and touch-gesture support, none of which would add any value for this kind of tool.
No one ever said TUIs are a new thing. It's been there since the beginning, when programs explicitly ran on terminals before WWW took off. It's the bloated web which ruined a lot of things
Much better than bluetuith which has weirdly bad UI/keybindings.
I wonder why omarchy isn't using this yet.
Same. First thing I did was replace the action of the bluetooth icon in Waybar with bluetui.
I found out: it used to be a lot less intuitive
omarchy is a shitshow. Please stay away from it. It's a disaster waiting to happen. It's the most bloated install script I have ever seen. DHH is fucking liar and taking up all the credit for himself by ripping off of bunch of well established open source projects
I was at a TUI Blue vacation resort a while back, thought for a minute this was related to that!
Used this the other day when for whatever reason Gnome's built-in bluetooth GUI refused to connect to my headphones. Very nice and easy to use.
I have tried to install it and got absolutely nowhere.
1. sudo apt install cargo on latest ubuntu and on attempt to "cargo install bluetui" it will say something about edition 2024 error. Because ubuntu is installing rust from 2023 and nobody bothered to update it?
2. Installing from https://rust-lang.org/tools/install/ will install rust only after removing existing version from 2023 (Why you won't just rewrite it?). Now I don't have cargo at all.
3. On attempt to use rustup it will tell me that path was not found. I need separate installation?
I am sorry but WTF is this garbage? Seems like whole rust ecosystem is broken...
This kind of thing is what drives advanced users from debian based distros to things like Arch and Nixos. With niche tools like this that don't have official packages, having a easy way for users to share build scripts, and have them managed by the package manager is a life saver.
Just grab the latest build https://github.com/pythops/bluetui/releases
Apt packages are managed by the OS so its normal they don't get overwritten by tools you download of the internet directly as that could break other apps installed with apt. As a general rule, don't use coding tools from apt as they are normally out of date, install them from other sources
I had similar with just (a make replacement) and debian 12. It seems requiring the latest of everything is the latest trend of rust ecosystem.
For the compiler in particular, it's pretty common practice to depend on a recent version. The backward compatibility situation is generally excellent, so the only real challenge is getting the compiler installed. That's generally straightforward with rustup, and Debian/Ubuntu also package several versions (under different package names) that are more recent than the distro's default.
How long have you been using ubuntu? From my past unpleasant experience of using it, one thing I learned is never rely on apt for package updates. Most will just keep rotting and hardly get any updates. It's the same with debian. Either use install scripts from packages or switch to a much more serious distro like Arch, where packages are always updated
You could use docker to build and then run the resulting binary without.
Heh, my sympathies.
Have you tried mise[1]? The last thing you probably want is to add another abstraction on top of this mess, but I've had good experiences with it, and it manages Rust, Go, Python, etc. environments very well.
IME getting any modern toolchain setup on different distros can be problematic, especially if you mix in the often outdated distro packages. So using isolated environments with a tool specifically built for that works better.
This looks very nice!
Is there a non-interactive CLI as well?
I currently use `bluetoothctl` with a wrapper script and `expect` so that I can quickly fire off `bluetooth.sh <device name substring>`, and it does the tedium of ensuring that the connection is established regardless of my audio settings. I do still use `bluetoothctl` for manually scanning and pairing, but once a device is paired, I don't run it directly. So it would be great if I could solve both things with the same tool.
I would only really need an interactive TUI for scanning and pairing. Maybe not even for that. E.g. if I run `bt pair <some device name>` then the tool could scan available devices and try to pair with one that fuzzily matches the provided name. And `scan` could work in a similar way. E.g. `bt scan --duration 10s` could show found devices within a specific time.
I'm not a big fan of interactive UIs if the same can be accomplished non-interactively. This allows the tool to be scripted, and can be much quicker to do what you want.
Does such a tool exist for Bluetooth? I'm tempted to whip something up myself, though I really have enough side projects as it is...
Yet another impressive rust/ratatui tool! I am really a fan of those projects (kudos to Orhun). At Copper Robotics we use it for our monitoring console, it is so easy to just ssh on a robot and get all your monitoring state in super snappy TUI screens instead of web stuff.
bluetui author here,
Thanks, glad you like it. And yes Big kudos to Orhun !
does TUI stand for terminal user interface ?
My understanding is T for text-based [1], the term is used about e.g. DOS programs too where the text interface is not historically called a terminal.
[1]: https://en.wikipedia.org/wiki/Text-based_user_interface
Yes. The term has been around for at least a few decades, but only became somewhat more widely used in the past decade. Only really known by people who spend a lot of time on the command line.
Not to be confused with CLI, which is literally for people who spend a lot of time on the Command Line :)
Why not show the device address? There's plenty of room for it and it's important when you have multiple devices with the same name. Or has the abominable trend of excess whitespace infected TUIs too?
There's probably nicer ways to express that criticism
I've absolutely had it with shit "designer" UIs hiding useful information and leaving a sea of useless space instead. There's nothing "nicer" about making users go through more effort.
That has nothing to do with this author and everything to do with you.
It's open source, you can fork it :)
Have you thought that you may want the window for this to be super small and that whitespace you see no longer exists?
bluetui author there
You can set a window with in the config file (with = positive integer) and TUI will be displayed with this width even in a large screen.
https://github.com/pythops/bluetui?tab=readme-ov-file#custom...
It's a plague under TUI go software too made with Bubbletea. Also, with some mesh related interfaces written in Python. Both slow and with a shitty interface not properly working under an 80x24 terminal with 16 colours.
I remember some hipster fauxretro player with just some playlist made of m3u links, written in Go. The visualization animations made it unusable under my n270 CPU based netbook. Meanwhile, the playlist URL's from the code played perfectly well under mocp with a really low CPU usage. Oh, you want bells and whistles? I think the Cava terminal visualizer can work with MPD and plug any CLI/TUI client you like.
Hardcoding any color than base16 is usually a poor choice. It should be up to the user to use any other color.
And colors should be semantic. If you don’t have any theming ability, just use reverse video to indicate selected state.
My current pet peeve is cli tools using ansi codes for progress bar. And with very poor detection of terminals.
For curseradio under OpenBSD, I just replaced bold for reverse in the Python code for the selected and/or highlighted radio station. It works much better this way.
The whole ecosystem of charm tools are well made. But most of them are extremely bloated and requires tons of dependencies to build a TUI