You are not logged in.
The last few days I've been playing with a wrapper script for sudoedit to make it a bit more friendly for our users.
Triggered from this discussion under "Editing text files as root".
There's a new script sudoedit.wrapper
By default it will use whatever text editor the user has set as bl-text-editor, unless the environment variable SUDO_EDITOR has been set, in which case it will use that instead.
A complication is that most modern GUI text editors return the prompt immediately, which fools sudoedit into thinking that the editing has been done. Lucklily, most of them have an option that can be passed to block this, so the prompt isn't returned until the editor window has been closed. The bad news is that each editor has a different option for this, so the script has to check what editor is actually being used before running it.
As a fallback - or if it has actually been set as bl-text-editor - there is bl-cli-editor which opens a terminal and runs whatever CLI editor has been set as the "editor" alternative. That script also needed some attention to make sure the terminal didn't return the prompt early either.
I tried to make the code readable, and cover corner cases, but there's likely still room for improvement. Suggestions welcome!
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Another, pkexec.wrapper, was added a few days ago so I think we might be OK for pkexec on Wayland or Xorg. (And will probably be able to drop our custom polkit configs.)
The upcoming release of bunsen-configs is going to have a lot of changes, and hopefully get us close to being able to build the first Carbon alpha iso.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Nice work @johnraff
I'm sure many are looking forward to alpha for testing, self included.
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
With so many changes under the hood coming for Trixie/Carbon it'll be a great thing to be able to soon kick the tires so any bugs/glitches can be found and reported. With Trixie's imminent release good to be able to soon release Carbon once all bugs have been squashed
Real Men Use Linux
Offline