Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think the issue is how whiptail parses its command line options and posting the entire script would not add anything to the thread. While you can increase the size of the window to accommodate more text I don't know how to create a multi line option.
There isn't enough information to know either way.
We see a virtual terminal window and a Ubuntu desktop.
The OP mentions raspi-config which is a raspbian configuration script and does run Ubuntu but I don't think it is installed on the Pi.
While the posted PDF in the original post is a Ubuntu desktop I can't tell if it is running on the Pi. In fact the OP could be using ssh to connect to the Pi from a Ubuntu computer.
Sorry , I was asleep at the wheel - the success percentage is OPPOSITE! Very next post is in the 80% category! Why do people who have no intention to help waste their time editorializing ? NO you cannot see 5000 plus lines under construction code !
I did ask Cisco company to see if they can add "horizontal scroll " control.
The whiptail "control" has vertical scroll bar when needed.
I did posted a non working code ,an example of the usage. I had a hard time putting backslash n in as a text.
I just broke my OS and cannot try adding \\n on '\n' at this point.
Are you trying to modify the existing raspi-config script or create a new script using its code as a model?
YES I am making a new , debug type , script using its code as a model.
Why do you need two lines for the description? I have posted that you can enlarge the window.
From my (short) experience with whiptail - I call it "temperamental" mainly for unpredictable display which depends on overall dimensions.
As an example - setting numbers of vertical lines makes --menu option text disappear.
I was actually trying to figure out how to add "tooltip" or "F1" type of help access.
Yes, I do agree there are many ways "to skin a cat" and I was concentrating on common "scroll bar control" - in horizontal way. Changing overall "window" dimensions is doable indeed.
And reason for multi line - some of the "commands" I use - first parameter - are pretty long , hence I run out of displayable text in description parameter.
From my (short) experience with whiptail - I call it "temperamental" mainly for unpredictable display which depends on overall dimensions. As an example - setting numbers of vertical lines makes --menu option text disappear.
It also depends on the size of the virtual terminal window. whiptail is only a bash command which is defined by its options. The only way I see adding help access would be to add the option and use a msgbox.
It also depends on the size of the virtual terminal window. whiptail is only a bash command which is defined by its options. The only way I see adding help access would be to add the option and use a msgbox.
I just checked "yad" and it is not available in Raspian. It would probably be overkill anyway. I need to keep focus on the script purpose - to make RPi debugging easier, not a fancy GUI.
I have another project running in parallel with this debugging script project and I am NOT is favour to change OS.
which is why I suggested it. I get not wanting to delve into a whole new application to create dialog boxes but instead focus on the bash script itself. However, in my personal experience, after struggling with whiptail and other applications for creating bash dialog boxes, I found yad to be pretty easy to pick up and the most flexible of the bunch. It all depends on your use case and priorities which only you can judge.
And reason for multi line - some of the "commands" I use - first parameter - are pretty long , hence I run out of displayable text in description parameter.
Could you shorten the first param?
Code:
"1" "Change password for the current user"
I guess I don't see why the repeated text...I'm tinkering, but haven't got it to work yet...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.