All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Levinson <nick_levinson@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: suggest allowing listing CLI commands parallel to GUI menu programs
Date: Thu, 19 Feb 2009 18:54:23 -0800 (PST)	[thread overview]
Message-ID: <491130.39708.qm@web33503.mail.mud.yahoo.com> (raw)

Problem: When I'm used to running a GUI desktop but I can't use the GUI to solve a problem involving a program and need to use a console, I'd like to know what console command would get me started with that program.

Proposal: That the kernel install with an empty or nearly-empty commentable text file with a publicized name and a format standard, the format to be stated in a comment and the file to be loose in one of the directories that is standard with most kernels and distros.

Then a GUI designer, such as one responsible for deciding what goes into a panel menu and what menu commands will be named, could write into that file the console equivalents of the menu commands for that GUI. A console equivalent could be the path and name of an executable associated with a given menu command, or could be a detailed ReadMe text file.

Entries in the file would be by GUI; for each GUI, each menu would be named; for each menu, each command would be named; for each command, the path and filename for the relevant executable (or more than one) would be listed; if typing the executable into a console would not be adequate because the console would need another name to gain access to the relevant capabilities, the relevant other name would be listed; comments could be written for any entry, such as if certain parameters are recommended.

The user with a problem would use a console to read the file and figure out what to do next.

This could have helped me one day when the screen was operating by one resolution but the panels didn't agree, and refused to display the Main Menu. I wanted to know what console command would give me access to the res. (I eventually solved the res problem another way.)

Thanks.

-- 
Nick


      

                 reply	other threads:[~2009-02-20  3:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=491130.39708.qm@web33503.mail.mud.yahoo.com \
    --to=nick_levinson@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.