There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

A strange "terminal emulator" idea I got, tho I bet this exists

I know that GUI does not cover most of functionalities, for good reasons - being specialized to task (like files app), it provides more fine-grained experience.

Yet, I find that there are common commands which is terminal-only, or not faithfully implemented. for instance,

  • Commands like apt update/apt upgrade might be needed, as GUI may not allow enough interactions with it.
  • I heard some immutable distros require running commands for rollbacks.

These could cause some annoyance for those who want to avoid terminal unless necessary (including me). Hence, I bet there are terminal emulators which restricts what commands you could run, and above all, present them as buttons. This will make you recall the commonly used commands, and run them accordingly. Is there projects similar to what I describe? Thanks!

brianorca ,

This actually exists, but for a different operating system. The AS400 (aka iSeries) had a command line where programs had a standard way to specify parameters, so that pressing a prompt key (F4) would allow you to build the proper command line by filling a form. I do miss that, pity it doesn’t exist for Linux.

palordrolap ,

Coming back to this with thoughts. What you're describing sounds a lot like a menu tree.

"Press 1 to do this, 2 to do that, 3 to go to submenu A, 4 for B," etc. 1

"You have pressed 1. Do you want to turn on option ABC? [Y / n]" Y

"Do you want option QWERTY47? [Y/n]" N

"Are you sure you want to run notthebees --abc --no-qwerty47? [Y/n]" N

"Aborted."

It sounds like a standards problem waiting to happen because no two menus will be alike, but hey, things like this can and do exist, and setting one up isn't that hard, only time consuming.

Telorand ,

This was my thought exactly. And I also had the same assessment that having various arguments be context aware would be challenging, since some have sub-arguments of their own (with further sub-arguments of their own, etc.) but can sometimes be strung together all on the same line. How do you determine if someone wants an ascendant argument or a descendant argument when you’re three layers deep into the tree?

You would have to make opinionated decisions, which was the whole reason to avoid scripts in the first place. Seems like it would be better to just make executable scripts (which is what Fedora Atomics basically do with the just command) or gamify learning how to work in the terminal.

Static_Rocket ,
@Static_Rocket@lemmy.world avatar

Something like this can kind of be achieved programmatically by unraveling bash completion arguments and loosely parsing terminal help strings.

They aren’t all formatted uniformly though, so you’ll need to come up with a filtering mechanism to prevent returning garbage. You’ll also always be a little out of date…

Daeraxa ,

What about something like navi - github.com/denisidoro/navi. Basically an interactive cheat sheet that has commands pre-loaded (or that you can make yourself).

someacnt_ OP ,

Woah this is rad! Thahk you!!

gerbercj ,

You could create a list of commands in a text file, and then pipe that into fzf. With a light wrapper that would allow you to type a portion of the command to select and execute it.

boredsquirrel ,
@boredsquirrel@slrpnk.net avatar

I think you could get really happy with fish or at least bash history autocompletion.

A flexible command runner, easy to add new buttons, spawning a terminal window to show the results, would also be useful.

I agree on the issue

therealjcdenton ,

Sounds like YaST

someacnt_ OP ,

Oh, this looks great, thanks!

nmtake ,

Long ago I made such restricted shell with filtering the shell command history file then disabling command history logging. With some shell scripting, I think you can get more sophisticated version. What shell are you using? (Bash, Fish, Zsh, etc.)

someacnt_ OP ,

I am using bash, which is indeed part of the problem. What emulator would you suggest, and how did you achieve it?

nmtake ,

Bash should be fine. On typical Bash installation I think this will work (please try to understand each command line before you actually try):


<span style="color:#323232;">$ cp ~/.bashrc ~/.bashrc.bak
</span><span style="color:#323232;">$ cp ~/.bash_history ~/.bash_history.bak
</span><span style="color:#323232;">$ printf 'set +o history' >> ~/.bashrc
</span><span style="color:#323232;">$ printf "sudo apt updatensudo apt upgraden" > .bash_history
</span><span style="color:#323232;">$ (Press Ctrl+D to logout)
</span>

For the next bash session you can refer only the two commands from the history with Up/Down/C-p/C-n.

1984 , (edited )
@1984@lemmy.today avatar

I think it would be very awkward, because then you need to look for the right button, move your mouse to it, click it, and then start looking for the next button, click it and so on.

For simple scenarios where you just need to click install, the gui can be great, but I think it’s not good enough for most commands with flags and options.

someacnt_ OP ,

Hmmm, good point. Maybe it is impossible to do this correctly.

Nibodhika ,

The thing is that there is no middle ground, the terminal you described would either have the problems of a GUI (limited interactivity) or the problems of a CLI (unintuitive).

If you do a button to do things you’ve removed option to do different things, if you ask them for text you’ve removed the intuitivity of a button. If you present less options you might not cover all cases, if you present more options it’s a regular terminal.

It seems that the issue you have is that you need a way to quickly redo commands you’ve done before and you need a good way to know what options you have. I have 2 CLI solutions for you.

  1. If you press Ctrl+R and start typing a command it will auto-complete to the latest command you ran that matches
  2. If you install zsh and grml-zsh-config and switch to zsh you will have a very powerful auto-complete that will allow you to press tab to auto-complete most parameters of most common operations.
someacnt_ OP ,

Yeah, I understand that this is difficult. But I am suggesting this considering lack of polish (ime) in commands.

On the recalling, remembering entire commands is not the problematic one for me. Rather, I want a quick way to go with which apps do which.

Also, terminals (that is, how most of the commands run) honestly do not look and feel good. I do think polished TUI could be a good solution, but they are not widespread.

atzanteol ,

Just create GUI application for the things you want. There’s already lots of them.

Otherwise there’s always “–help”.

someacnt_ OP ,

I mean, there are already tons of applications that lets you e.g. update, like apt update/upgrade does.

One issue with it is that it fails time to time, and error messages the GUI usually conveys are subpar. That’s why I think you cannot avoid terminals. I just want some middle ground for that.

Also, ik this is nitpicking but… while apt is good on this front… what about the CLIs whose --help gives hundreds of lines?

atzanteol ,

I mean, there are already tons of applications that lets you e.g. update, like apt update/upgrade does.

Bingo.

while apt is good on this front… what about the CLIs whose --help gives hundreds of lines?

Read them. There’s a reason some programs have many options. Avoiding the CLI isn’t the solution.

someacnt_ OP ,

The apps just fail and crash randomly, any linux users cannot entirely rely on them. Well, I guess linux is destined for 2% of desktop users, who can use terminal on a daily basis, and current rise is just a fluke.

atzanteol ,

Yes, that’s fine. If you didn’t like Linux you’re welcome to not use it.

You see the console as a flaw. Some of us see it as an advantage.

Telorand ,

Well, I guess linux is destined for 2% of desktop users, who can use terminal on a daily basis, and current rise is just a fluke.

Dunno what you’re talking about. Most people I’ve seen who have made the switch just go learn how to use the terminal. You’ll have to eventually, since many people have use cases that fall outside the sane defaults of whatever distro you chose, and there’s tons of videos, online communities, and written tutorials to help.

The rest know somebody who can help or just want a system that can do whatever defaults it’s been set up to do out of the box (e.g. open pictures, use a web browser, play Steam games, etc.).

ReveredOxygen ,
@ReveredOxygen@sh.itjust.works avatar

kde’s discover and gnome software have both worked fine for me, for the most part

tunetardis ,

This reminds me of something from my ancient past. Back in the early-ish days of Apple, there was a development system called MPW (Macintosh Programmer’s Workshop) which included its own little kludgy shell.

The weird thing about it though was while you could enter commands on the command line like in any shell, you could prefix them with the word commando (presumably a portmanteau of “command” and “window”) and this window would pop up showing various buttons, checkboxes, etc. correponding to command line options. When you ok’d the window, it would generate the command line for you.

I’m rather hazy about how all this worked, but I think there was some sort of template language to define the window layout if you wanted to add commando support for your own tool? And presumeably, as you say, you could restrict what’s possible with the window interface as you deemed fit?

someacnt_ OP ,

Seems like what I was roughly thinking of. I guess it fell into obscurity for good reasons, but I do think this kind of tool would be great for some edge-cases - that is, you cannot yet avoid terminal.

tunetardis ,

The thing about the MPW Shell is it was sort of the only game in town if you actually wanted a command line with the classic Mac OS. (There’s an awesome little emulator called SheepShaver if you ever want to explore it btw.) Well, I suppose there was A/UX. I thought it was a miracle when that came out. You have to realize in those early days a good chunk of the operating system itself was actually baked in to ROM. (You had to do desperate things to squeeze a GUI out of such limited resources as existed back then!) So to this day I have no idea how they managed to spin off a 'nix despite that.

Anyways. I wonder, if you made some sort of template format today, to what extent you could write some sort of conversion tool that would scrape a man page or whatever to rough it in and then you could tweak it to get what you want? man pages aren’t super standardized in their format I guess, so it’s probably more trouble than it’s worth. I like to use Python’s argparse when rolling out scripts myself, and its –help format is pretty rigid given that it’s algorithmically generated. Might be more plausible with something like that? I had a quick look just now to see if you can drill down into the argparse.ArgumentParser class itself to pull out the info more directly, but it seems a rather opaque thing that doesn’t expose public APIs for that. Oh well…

IHeartBadCode ,

Are you perhaps looking for something like this? Or something else.

That said, learning the terminal commands is a much better path. You'll develop a richer understanding of the various tools with repetition.

someacnt_ OP ,

I already am quite familiar with terminal, and am aware of how to handle it. I do have issues that I am using plain old bash, but it’s not unfamiliarity that is my problem.

It’s more that there are common commands that I am dealing with, I (somehow) don’t like entering it in terminal format.

About warp, that seems roughly what I want, but the AI part irks me. I dunno, I gotta look more dseply.

gomp ,

I bet that doesn’t exist: nobody would put work in a program that lets just restricts what you can do with zero usability advantages (ok someone might)

If you fear you might run unsafe commands just save whatever you are comfortable running in scripts and restrict yourself to run those instead of manually typing commands you don’t fully remember/understand.

BTW: topgrade will detect what needs updating in your system (your distro’s package manager, flatpak, python stuff, … whatever) and update all the things

BTW: “terminal emulator” is the program that shows you text in a window, the program that runs inside it and validates/interprets your commands is a “shell” (the one you are using is most probably bash)

someacnt_ OP ,

Calling it “terminal emulator” was a poor word usage on my end, yeah. I do not fear myself running command line though. I just want to avoid CLI.

oo1 ,

something like raspi-config ( i know that’s console based GUI, but it’s gui to me), or even the endevourOS launcher screen?

someacnt_ OP ,

Yeah, these kinds of stuffs would fit my bill. TUI would work just as well.

pivot_root ,

I understand the desire to want to avoid the command line, but you’re severely restricting your ability to troubleshoot by doing so. Every operating system has a terminal and command line, and there’s going to be cases where you’ll want to drop into a shell to do something that has no GUI equivalent.

someacnt_ OP ,

Yeah I am not suggesting an entire terminal replacement, which is unreasonable.

Telorand ,

You should see if there’s a Windows equivalent (since it has the most market share by a country mile). If it does, use that for ideas, and improve upon it. If not, it may not be feasible or reasonable based on your goals.

WbrJr ,

I dont think you should habe to learn to usw the terminal in order to debug your operating system. If i would switch my mom to Linux, i dont want her to have to use the terminal. So making life easier for those people would grealty improve the appeal of Linux to tech noobs. By arguing we need the terminal for Linux, we gatekeep people from trying and using Linux, if they are afraid of technology

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •