xrandr-tui

So, you want to change your screen resolution?
Have added a new LCD to your laptop and want to switch the displays?

Depends on: (xorg -)xrandr, bash and TUI (0.9.4-5 or later) (Website, Download, Install)

Have a look at xrandr-tui, if you do not want to type in those commands:

More functions are planned for the future, but first some optimizations for what currently is have to be applied.

It is meant for the use with WMs (Awesome, I3,dwm, etc) as it lets you set a base config, which will be used for:

xrandr-tui --switch
xrandr-tui --reset
xrandr-tui --mirror

Keep in mind, calling xrandr-tui by itself, will let you customize the task every time.
Whereas the quickaccess (arguments) will rely on the configuration file.
The screenshots you see here, are from xrandr-tui called without arguments.

You can even add and remove new/old resolutons:

Links

• Website: https://github.com/sri-arjuna/xrandr-tui
• Install/Readme: https://github.com/sri-arjuna/xrandr-tui/blob/master/docs/README.md
• Download: https://github.com/sri-arjuna/xrandr-tui/archive/master.zip
• Script: https://raw.githubusercontent.com/sri-arjuna/xrandr-tui/master/bin/xrandr-tui

GNU rejected TUI, for the moment

Hello everyone

As TUI can show its true power only when it is already installed on your system, so one could simply share the scripts that  rely on TUI, just like one shares any bash or other shell script, I wanted to become part of GNU.

That is no easy task, specialy if you come from a 4 year old project that hasnt had this goal from start.
So, for the past 10 months, its been in the GNU Evaluation queue and just until a day ago it look very promising.

However, it got rejected for the moment, as more user feedback is wanted for them to evaluate the need/profit of making TUI part of the GNU family.

With one of the arguments beeing that we would need some user feedback for further evaluation.

That is, because TUI has a new approach to the terminal...
An approach mainwhile quite the same, but also quite different.

In the beginning, I wanted the 'ultimate' dir/menu browser for (a single specific) directory based script project/s.
In the end I extracted those functions as I wanted to have the scripts provided in named directories to look/match the containing 'ultimate' menu, so I made them individual commands.

Due to this change, one can also create great (single file) wizzards or wrappers around other cli/clu applications or make tools that act (but dont look like) 'ip' or 'iw' commands, just for your custom directory-tree structure.

It comes with many commands/functions for often used tasks, such as tui-yesno, tui-select, tui-read, as well as nice optical commands such as tui-header and tui-title.

As it is a command and line-based-output framework, it might look weird if you just try a single command.
To get started - once installed, you might want to check:

tuirc samples
tuirc provides

To get the manual, please check either:

info tui
tuirc info
tuirc html  # Only if you used "make install all"

I'm asking here for this required feedback:

• Which OS/Distro?
• Does Installer work?
• Does running 'tuirc' raise any, and if - what kind of - error messages? (Besides initial creating of user configuration)
• Any other errors/bugs/unexpected behaviour you came along?

Additionally according to your skill, time and preferences:

• What are our thoughts about the 'tuirc samples'  and info page?
• Did you find any security bugs? - have any advice how to fix them?

Get it from: https://savannah.nongnu.org/projects/tui/

Issue is, all i can say for sure is that it runs well on my system.
I'd very much like to have confirmed reports on which OS or Distro it installs and runs well or not.
That is also required to get it working for that OS/Distro, eventhough most of them work alike, there are differences i might not be aware to catch and handle (properly) without reports and hints how its done on your OS.

Thank you in advance for sharing your thoughts about TUI.

Almost there...

Oh yeah, i'm happy already, allthough it has not yet passed evaluation.

What i'm talking about?
I'm talking about TUI - Text User Interface for scripts, which has reached 0.8.9-GNU-RC16 yesterday evening, and if everything works out as expected, it will reach "GNU TUI 0.9.0" this week.

I've been using TUI already for about 3 years for my own 'production', but by now, it has achieved a state that deserves the label 'stable'!

The feedback, so far, has been good and promising.

What to expect when it passes the evaluation?
I plan to move the project home to: http://www.gnu.org/software/tui to share the texinfo manual and to be the first and primary point of announcements regarding it.

Obviously i'll post here about it too, but more in a human-speaking way, and less technical as there.

Oh im so excited, that i just cant hide it...
*dance dance*

Funny error message

Been trying to write a task manager for a script, with the recent changes for GNU TUI evalutation, this is an error i've recieved while working on VHS (Video Handler Script, using ffmpeg)...
Wondering if my security concerns were too much... 

The german words means: "Line 224: .. Syntax  Error: Operator expected. (Error causing character is \033[....)"




So basicly, aborting failed because the aborting text string for the user contained a smiley ';)'
While mainwhile the the printing fails due to an unprintable character, escape string.
But the aborting, after all, aborts successfull.

Usualy errors are just annoying, but this one i found rather funny.

BTW, these 3 bugs are fixed now.

Learn about TUI
Learn about VHS

Download them at github.

Incoming update for VHS

Not yet done, but i'm excited about the latest achievement.

Playing multiple audio files works now, and updated its playback quite a bit, but see for yourself:

The progressbar beeing on multiple lines, was caused by pressing enter, so you see the 'progress ' too.

Enjoy

TUI update 0.8.1-4

• Changed:   tui-new-*, had some invalid references left
• Changed:   tui-new-*, added some default values to settings.conf, like which templatefile to use if no arguments are passed
• Changed:   tui-filemgr, got forgotten when changed to list files

Get it at https://github.com/sri-arjuna/tui/releases/tag/v0.8.1-4
Or update it like:

su
cd /path/to/tui-git-repositry
git pull
echo y n | ./install.sh

 

Taming the beast, TUI back to stable

Now after the big excitement of the successfull changes to use an invidiual rc file for all its used variables, basic usage seems to be back to normal again.

-> Taming the beast, back to stable! <-

It is causing a rush to figure one successfully installs the bash completition, accidently to a wrong and non-working path.

But this massive change also helped me to figure out which internal variables to share and which not, so i've added the function 'provides' to figure that out.

tui provides

Will print a hughe and long list with all the variables used internaly and which you may use as well.

If you

source  tui

you'll have all of those variables available, but sourcing just the rc file, and the wanted file providing the variables you want can increase usage speed.

source ~/.tui_rc || . tui
source $TUI_FILE_{APPS,SETTINGS}

Also several small hotfixes, of which i was sure i have had applied already 6 months ago....

Hope you like it, enjoy! :)

TUI 0.8.0-2, The RC File release

Get it here:
https://github.com/sri-arjuna/tui/releases/tag/v0.8.0-2

Read about it here:
http://www.unix.com/shell-programming-and-scripting/253496-tui-text-user-interface-framework-scripts.html

Also the installation script has changed:

Hope you like the changes.
Enjoy! :)

Get the extension of a filename

Every now and then, one needs to decide upon a file its extension what to do.

This is what i've added as tui-str-extension:

out=""
FN=$( echo "$1" | sed s," ","",g)    # Remove any spaces and make it a single string
for chance in $(echo "$FN"|sed s,"\."," ",g)    # Use dots as string seperators
do    out="$chance"
done
if [ "$out" = "$FN" ]
then    echo ""
else     echo "${out%\ /}"     # Remove any tailing or single space
fi

Hope you like it :)

Building FFMPEG

Been on in all easter days, it pulls in so many different applications, codecs, drivers and whatnot.
Just imagine, the temporary build path contains more than 500mb of data, compared to the final binary of ffmpeg, which is not even 500kb in size when done.

Yesterday evening i was finaly able to build the (my) first ffmpeg.
Today when i wanted to redo it, starting with 0, figured many of the build steps got accidently optimized for rerunning, which means, some of the parameters for the first 'contact' got removed and have to be readded.

Eventhouth its a smaller script, about 700 lines of code, not beeing familiar with the building process of that many applications is not a small challenge.

But i just encoded my first x265 video last night, and i have to say, the quality is great, eveb more when comparing to the filesize.

That was a good motivator, to keep me going for the still missing (failing) things, such as, but not limited to:

• vorbis
• webp
• v4l
• ass
• srt
• rtmp
• speex
• wav
• dc1394

Once it does what i want, this script will be part of VHS, as its a handler for ffmpeg it makes sense to let it build the tools it depends on.

I'll keep you posted :)

tui-printf: aligment is good

While having multiple terminal windows open, i've just figured the good math of reasons to split up...

Plain:











With indicators:

TUI - Themes, colors per user, and root is special

Heya, isnt that cool?!?

I've finaly applied a theme-mechanic so one can easily change among colors and borders used with TUI.
Root uses even another one, changeable only by root obviously.

But since my default linux is Fedora, the default theme is 'blue'.
And since the user root can do more damange, and Fedora is based upon Red Hat, the default root color theme is 'red'.

Here is a preview with the upcoming 'dev-scripts':

Above was called as regular user,
below was called as root user.

Readded 2-Pass encoding for VHS

1.0.7
- Reducded -Q dvd from v768 to v640
- Readded 2pass encoding: -2
- Fixed small typos

Isnt that just nice, after several weeks of asking for feedback, one actualy replied AFTER i decided it to be stable.
Oh well, at least i know now that the 2 pass encoding was working, for others at least, so i have readded this with this new update of my "Video Handler Script".

Hope you like it

ds prj list

Just done a little nice feature to keep track of the modules used with a project:

ds prj list