HOW2 find an app's 'call-name'?

[no.to...@gmail.com]

This is absurd ! Years ago, I selected from the menu
<eyes of gnome>. Then when I had a different installation,
where it was not on the menu, I couldn't know how to
call-it.

Now this installation has masses of *qt* files, which
wastefull search effort has told is <nokia..quick-time ...>.
But I want to test it -- before I delete the files.

Google doesn't answer such a simple question as
<what is qt 'called'>.

`apropos` didn't help.
`locate qt | grep <README, faq, FAQ..>` failed.

`locate qt | <find executable files> `
might find an 'entry point script'

What should I do?

== TAI

[Loki Harfagr]

Mon, 06 Feb 2012 08:21:47 +0000, no.top.post did cat :

try this one, just in case your mystery meat is that bubble gum:
$ man qtoptions

>
> What should I do?

prepare a cup of hemlock?-)

[Chris Davies]

no.to...@gmail.com wrote:
> Years ago, I selected from the menu <eyes of gnome>.

Do you mean "Eye of Gnome"? (On my Gnome-based system this is under
Applications > Debian > Applications > Viewers.)

> Then when I had a different installation, where it was not on the menu,
> I couldn't know how to call-it.

On the original system (assuming you still have access to it), you should
be able to look under System > Preferences > Main Menu, which will allow
you to see the definition of each menu item.

> Google doesn't answer such a simple question as
> <what is qt 'called'>.

Hang on a moment. You talked about Eye(s) of Gnome. Now you're talking
about QT. What's the relevance of EoG to QT, and which do you mean?


> What should I do?

I think you should rephrase your question more clearly. Please.
Chris

[J G Miller]

On Monday, February 6th, 2012, at 08:21:47 +0000, No Top Post explained:

> Years ago, I selected from the menu <eyes of gnome>.
> Then when I had a different installation, where it was not on the menu,
> I couldn't know how to call-it.

By right clicking on the item to get properties and then look at
the executable name in the properties box.

So at the command line you would call it as follows

luser> eog &

> Now this installation has masses of *qt* files

Because you are obviously using a KDE desktop installation
rather than a GNOME desktop installation, and since eog
is not a KDE application, it probably will not be found
in the KDE desktop user application menu.

[no.to...@gmail.com]

That gives me more info on <qt> specifically, but doesn't answer
the GENERAL question: "HOW2 find an app's 'call-name'?"

Take another example: pango.
I could do: `whatis pango` ; `apropos pango` and perhps I'd
get info to know: 1. what it does & 2. how to call it ??

> >
> > What should I do?
>
> prepare a cup of hemlock?-)

===================

>> Then when I had a different installation, where it was not on the menu,
>> I couldn't know how to call-it.

Chris Davies wrote:-

>On the original system (assuming you still have access to it), you should
>be able to look under System > Preferences > Main Menu, which will allow
>you to see the definition of each menu item.

A main reason to need to know the <call name> is when there's
NO menu.

>> Google doesn't answer such a simple question as
>> <what is qt 'called'>.

>Hang on a moment. You talked about Eye(s) of Gnome. Now you're talking
>about QT. What's the relevance of EoG to QT, and which do you mean?

Re-read the SUBJECT, which is a GENERAL question.
<eog> is a specific example of my experience.
<qt> is a specific example of my REPEATING problem,
which still is not answered.
==============

>> I couldn't know how to call-it.

J G Miller wrote:
>By right clicking on the item to get properties and then look at
>the executable name in the properties box.

The problem arises mostly when tere's no menu [to right klik].
Can't you people read the question?

>Because you are obviously using a KDE desktop installation

previously

>rather than a GNOME desktop installation, and since eog
>is not a KDE application, it probably will not be found
>in the KDE desktop user application menu.

I'm mostly using `blackbox`,
but that's irrelevant to the QUESTION.

[Loki Harfagr]

Thu, 09 Feb 2012 06:23:02 +0000, no.top.post did cat :

> In article <4f2fcbed$0$8183$426a...@news.free.fr>, Loki Harfagr
> <l0...@thedarkdesign.free.fr.INVALID> wrote:
>

>> Mon, 06 Feb 2012 08:21:47 +0000, no.top.post did cat :

>>
>> > This is absurd ! Years ago, I selected from the menu <eyes of gnome>.
>> > Then when I had a different installation, where it was not on the
>> > menu, I couldn't know how to call-it.
>> >
>> > Now this installation has masses of *qt* files, which wastefull
>> > search effort has told is <nokia..quick-time ...>. But I want to test
>> > it -- before I delete the files.
>> >
>> > Google doesn't answer such a simple question as <what is qt
>> > 'called'>.
>> >
>> > `apropos` didn't help.
>> > `locate qt | grep <README, faq, FAQ..>` failed.
>> >
>> > `locate qt | <find executable files> `
>> > might find an 'entry point script'
>>
>> try this one, just in case your mystery meat is that bubble gum: $ man
>> qtoptions
>>
> That gives me more info on <qt> specifically,

exact, which was the correct answer to your question relative to the
example you gave.

> but doesn't answer the
> GENERAL question: "HOW2 find an app's 'call-name'?"

exact, that's because the "GENERAL question" is a misconceived idea
about questions, as for instance your next example about that "GENERAL Q"
shows clearly:

> Take another example: pango.
> I could do: `whatis pango` ; `apropos pango` and perhps I'd get info to
> know: 1. what it does & 2. how to call it ??

the answer to Q1 is to be read in the docs
(start with /usr/doc/pango-${versionnumber}/README)
after reading some variable length of that doc you'll then be
able to decide that the answer to Q2 is that you wouldn't "call" it.

>> > What should I do?
>>
>> prepare a cup of hemlock?-)

it's a pity that you ignored that part of the "GENERAL answer"
as it gave a good hint on why your hows were where and when.

> ===================
>>> Then when I had a different installation, where it was not on the
>>> menu, I couldn't know how to call-it.
>
> Chris Davies wrote:-
>>On the original system (assuming you still have access to it), you
>>should be able to look under System > Preferences > Main Menu, which
>>will allow you to see the definition of each menu item.
>
> A main reason to need to know the <call name> is when there's NO menu.

that's right but given the idea that:
1. you don't know what you want to "call"
2. you don't know how/where to "call" it
you seem a little bit lost in the middle of neverwhere, maybe
it is time to know what you want and ask questions not too "GENERAL"?

>>> Google doesn't answer such a simple question as <what is qt 'called'>.
>
>>Hang on a moment. You talked about Eye(s) of Gnome. Now you're talking
>>about QT. What's the relevance of EoG to QT, and which do you mean?
>
> Re-read the SUBJECT, which is a GENERAL question. <eog> is a specific
> example of my experience. <qt> is a specific example of my REPEATING
> problem, which still is not answered.

exact, and as now you know that there is no specific answer to
the "GENERAL question" you may concentrate on your functional aims
and formulate questions that might bring some practical answers to you.

> ==============
>
>>> I couldn't know how to call-it.
>
> J G Miller wrote:
>>By right clicking on the item to get properties and then look at the
>>executable name in the properties box.
>
> The problem arises mostly when tere's no menu [to right klik]. Can't you
> people read the question?
>
>>Because you are obviously using a KDE desktop installation
> previously
>>rather than a GNOME desktop installation, and since eog is not a KDE
>>application, it probably will not be found in the KDE desktop user
>>application menu.
>
> I'm mostly using `blackbox`,
> but that's irrelevant to the QUESTION.

not so true but not quite false in a way as you'd also say that
everything is irrelevant to the "QUESTION".
In that issue -- that you're believing you're having now -- JGMiller
remark is quite correct as your problem description could be read in
the way that you were trying to find where to right-click on EoG while
on a desktop that hadn't it in its menu for a system that didn't
have any EoG in its installation.

Now, if you really want EoG and wish to know where/how you call or
click it your best start will be to install EoG, if your question still is
where/how you can click/run whatever anytime anyhow the GENERAL answer
is, as always, simply 'it depends'.

[Tauno Voipio]

On 9.2.12 8:23 , no.to...@gmail.com wrote:
> In article<4f2fcbed$0$8183$426a...@news.free.fr>, Loki Harfagr<l0...@thedarkdesign.free.fr.INVALID> wrote:
>
> That gives me more info on<qt> specifically, but doesn't answer
> the GENERAL question: "HOW2 find an app's 'call-name'?"
>
> Take another example: pango.
> I could do: `whatis pango` ; `apropos pango` and perhps I'd

> get info to know: 1. what it does& 2. how to call it ??


Did you ever Google for 'pango?

I got over 4 million hits, at least the first page is very relevant.

Stop whining and grow up!

--

Tauno Voipio

[Keith Keller]

On 2012-02-09, Tauno Voipio <tauno....@notused.fi.invalid> wrote:
> On 9.2.12 8:23 , no.to...@gmail.com wrote:

[snip]

> Stop whining and grow up!

That seems unlikely; this OP has been doing this sort of thing for many
years. Best to simply killfile or ignore him and move on.

--keith

--
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[Chick Tower]

Is it possible that what you're looking for is not an executable (i.e.,
not a program)? On my Slackware 13.0 system, qt is a directory in
/usr/lib.

IIRC, I see you post on alt.os.linux.slackware. You can grep through
the files in /var/log/packages to find out what package installed a
particular file, and what other files (e.g., programs) were installed by
the same package. If you're using another distro, the package manager
usually has an option to tell you what package installed a particular
file.
--
Chick Tower

For e-mail: colm DOT sent DOT towerboy AT xoxy DOT net

[no.to...@gmail.com]

In article <4f3387a6$0$8212$426a...@news.free.fr>, Loki Harfagr <l0...@thedarkdesign.free.fr.INVALID> wrote:

> Thu, 09 Feb 2012 06:23:02 +0000, no.top.post did cat:
>

> if your question still is
> where/how you can click/run whatever anytime anyhow the GENERAL answer
> is, as always, simply 'it depends'.
>

OK, so there's no proper method.
This looks like a task for the UNO-like-Debian-committee.
---------
> > That gives me more info on<qt> specifically, but doesn't answer

> > the GENERAL question: "HOW2 find an app's 'call-name'?"
> >

> > Take another example: pango.
> > I could do: `whatis pango` ; `apropos pango` and perhps I'd

> > get info to know: 1. what it does& 2. how to call it ??
>
---------> Tauno Voipio wrote:-

> Did you ever Google for 'pango?
>

I'm going to a isolated location with no access to google, and want
to have a professional rather than ad-hoc/monkey method.
Of course asking on USEnet is the ultimate ad-hoc method,
after all else fails.
> ---------
Keith Keller wrote:-

> Is it possible that what you're looking for is not an executable (i.e.,
> not a program)? On my Slackware 13.0 system, qt is a directory in
> /usr/lib.
>

Yes I gradually got that impression. But I was asking myself "what is this
BIG thing, and how can I test it?" But it's not about Qt only. It's obvious
that all apps must be callable, other than by kliking a menu.

>
> IIRC, I see you post on alt.os.linux.slackware. You can grep through
> the files in /var/log/packages to find out what package installed a
> particular file, and what other files (e.g., programs) were installed by
> the same package. If you're using another distro, the package manager
> usually has an option to tell you what package installed a particular
> file.
> --

Ok, that would be an elaborate way of of finding out why/what all
the <qt> files are for. But imagine 'you met some one on the bus, who
said "if you've got the full XYZ installation, you should try app: dog."
But when you get to your machine you can't find how to execute dog!

Now I'm satisfied that there are no simple solutions to this.
The debian commitee will fix it?

Thanks,

== Chris Glur.

[Dan Espen]

no.to...@gmail.com writes:

> In article <4f3387a6$0$8212$426a...@news.free.fr>, Loki Harfagr <l0...@thedarkdesign.free.fr.INVALID> wrote:
>
>> Thu, 09 Feb 2012 06:23:02 +0000, no.top.post did cat:
>>
>> if your question still is
>> where/how you can click/run whatever anytime anyhow the GENERAL answer
>> is, as always, simply 'it depends'.
>>
> OK, so there's no proper method.
> This looks like a task for the UNO-like-Debian-committee.
> ---------
>> > That gives me more info on<qt> specifically, but doesn't answer
>> > the GENERAL question: "HOW2 find an app's 'call-name'?"
>> >
>> > Take another example: pango.
>> > I could do: `whatis pango` ; `apropos pango` and perhps I'd
>> > get info to know: 1. what it does& 2. how to call it ??

I have a pretty good idea what pango does and it mostly operates
under the covers.

But if I type pango on the command line and press tab,
I find I have 2 executables start start with the string pango.
One has a man page. The other is self explanatory if you run it.

So then I did:

locate pango

and I found /usr/share/doc/pango-1.29.4/README

which pretty much tells all.

> ---------> Tauno Voipio wrote:-
>> Did you ever Google for 'pango?
>>
> I'm going to a isolated location with no access to google, and want
> to have a professional rather than ad-hoc/monkey method.
> Of course asking on USEnet is the ultimate ad-hoc method,
> after all else fails.

Google is a monkey method. Someone tell the chimps.
Really you can use Usenet but not Google?

Nice trick.

> Keith Keller wrote:-
>> Is it possible that what you're looking for is not an executable (i.e.,
>> not a program)? On my Slackware 13.0 system, qt is a directory in
>> /usr/lib.
>>
> Yes I gradually got that impression. But I was asking myself "what is this
> BIG thing, and how can I test it?" But it's not about Qt only. It's obvious
> that all apps must be callable, other than by kliking a menu.

Well, we just covered Pango.
As far as qt, well it looks like I have a huge amount of qt stuff
in /usr/share/doc/qt. But for a real low-down install the qt demo package.

>> IIRC, I see you post on alt.os.linux.slackware. You can grep through
>> the files in /var/log/packages to find out what package installed a
>> particular file, and what other files (e.g., programs) were installed by
>> the same package. If you're using another distro, the package manager
>> usually has an option to tell you what package installed a particular
>> file.
>> --
> Ok, that would be an elaborate way of of finding out why/what all
> the <qt> files are for. But imagine 'you met some one on the bus, who
> said "if you've got the full XYZ installation, you should try app: dog."
> But when you get to your machine you can't find how to execute dog!

Assuming I can't find dog in a menu,
I'd open a terminal and type dog, then a tab.

> Now I'm satisfied that there are no simple solutions to this.
> The debian commitee will fix it?

Ahh, beg to differ. Simple solutions come with persistence.

--
Dan Espen

[Chick Tower]

On 2012-02-11, no.to...@gmail.com <no.to...@gmail.com> wrote:
> Keith Keller wrote:-
>> Is it possible that what you're looking for is not an executable (i.e.,
>> not a program)? On my Slackware 13.0 system, qt is a directory in
>> /usr/lib.
>>
> Yes I gradually got that impression. But I was asking myself "what is this
> BIG thing, and how can I test it?" But it's not about Qt only. It's obvious
> that all apps must be callable, other than by kliking a menu.
>>
>> IIRC, I see you post on alt.os.linux.slackware. You can grep through
>> the files in /var/log/packages to find out what package installed a
>> particular file, and what other files (e.g., programs) were installed by
>> the same package. If you're using another distro, the package manager
>> usually has an option to tell you what package installed a particular
>> file.
>> --
> Ok, that would be an elaborate way of of finding out why/what all
> the <qt> files are for. But imagine 'you met some one on the bus, who
> said "if you've got the full XYZ installation, you should try app: dog."
> But when you get to your machine you can't find how to execute dog!
>
> Now I'm satisfied that there are no simple solutions to this.
> The debian commitee will fix it?
>
> Thanks,
>
>== Chris Glur.
>

I wrote those sentences, not Keith.

I wonder how come nobody else seems to have run into this problem. I
don't mean the attribution of quotes.