Active Topics

 



Notices


Reply
Thread Tools
Posts: 1,522 | Thanked: 392 times | Joined on Jul 2010 @ São Paulo, Brazil
#11
There isn't one single answer, for each program you need to find what the executable file is called and where it is located (this second part is not always necessary, some executables are placed in specific folders that the system is set to look into from anywhere so you don't need to specify the folder)
 

The Following User Says Thank You to TiagoTiago For This Useful Post:
shallimus's Avatar
Posts: 568 | Thanked: 969 times | Joined on Dec 2009 @ Toronto
#12
Originally Posted by JohnLF View Post
/path/to/paperthrow

Not sure where it is? Try which paperthrow or if all else fails

find / -name paperthrow -print

Probably not the best way, but I've been doing that for 25 years and it works for me
Also see echo $PATH for a list of directories that the shell will search in for commands (that's not an exhaustive list as there are some built-in commands, but...)

And with find, you may want to add wildcards, like:
Code:
find / -name '*leafpad*'
...just in case it's leafpad-something or what-have-you.

Originally Posted by demolition View Post
Also, be careful about shutting the terminal you used to initiate the launch because you'll close both at once - unless that's what you want. Not sure if you can spawn the new programme so it's uneffected by whatever goes on in the terminal.
True about closing the xterm. To get around that, use nohup so the child process won't allow itself to be killed (nohup == no hangup == process will ignore a HANGUP signal telling it to kill itself) and an ampersand (&) so it launches in the background and returns control of the terminal to you:
Code:
nohup ./some-text-editor myfile.txt &
__________________
tinfoilhat.dll: Trojan horse detected
Sailfish want list: calendar bugfixes, glanceable agenda, Swype or similar
Evolution continues (but we're still pre-Cambrian)


Last edited by shallimus; 2011-10-05 at 01:07. Reason: Merging two similar posts
 

The Following 2 Users Say Thank You to shallimus For This Useful Post:
Posts: 36 | Thanked: 4 times | Joined on Oct 2011
#13
Originally Posted by TiagoTiago View Post
There isn't one single answer, for each program you need to find what the executable file is called and where it is located (this second part is not always necessary, some executables are placed in specific folders that the system is set to look into from anywhere so you don't need to specify the folder)
ok do you know where or how can I find the correct name of the executable file?
thanks Tiago
 
Posts: 1,522 | Thanked: 392 times | Joined on Jul 2010 @ São Paulo, Brazil
#14
Check the contents of the shortcut files, they got .desktop extensions, i forgot where they are located, but should be easy to find on the forum or the wiki.
 

The Following User Says Thank You to TiagoTiago For This Useful Post:
Posts: 502 | Thanked: 366 times | Joined on Jun 2010 @ /dev/null
#15
Programs reside under various areas and usually is controlled by the package manager which is probably equivalent to windows' add/remove programs.

The default package manager for maemo 5 (fremantle) is dpkg and its command line based only.

Unfortunately there's no easy way to go about finding out the correct name of the executable (and without using find which just thrashes I/O) what you could do is something like:
Code:
dpkg -l foo
That will list package name with foo or starts with foo. If you cannot find the package name you may want to try piping it into grep:
Code:
dpkg -l| grep foo
This will not only output package names that contains the word foo but also the description of the package. If lets say you found the package and you want to find out the executable within the provided package. You do:
Code:
dpkg -L foobar
That will list all the files belonging to foobar including directories that the files are to be placed in starting from rootfs which is /. Although unlike windows where executables are named with extensions such as .exe or .com under linux executables aren't distinguished by that but with a program called file (which you may have to install by hand from fremantle/tools). You then do something like this:
Code:
for i in `dpkg -L foobar`; do file $i; done
That will then print out what each of the line means, like if the file on the list is a directory it will say its a directory. If its an executable it will say something like LSB 32bit executable.
__________________
 

The Following 3 Users Say Thank You to tuxsavvy For This Useful Post:
mece's Avatar
Posts: 1,111 | Thanked: 1,985 times | Joined on Aug 2009 @ Åbo, Finland
#16
the .desktop files are in
/usr/share/applications/hildon/
Code:
ls /usr/share/applications/hildon/
lists what is there. you can use grep to try to find something specific, for example
Code:
ls /usr/share/applications/hildon | grep paper
lists all with the word paper in it. I assume papertoss is one of them. once you have the filename you can do
Code:
cat /usr/share/applications/hildon/papertoss.desktop
that will show the contents of the file. There is a line starting with Exec=
and there is the command you use. Note that if the command points to something in /usr/bin you can just start that app with the last word in the command. For example the calendar.desktop file points to /usr/bin/Calendar so just typing Calendar from your home dir would start the calendar app.

When I want to launch an app from command line I usually try with just typing the beginning of the app name first and pressing tab to see if that command exists. Before going trough the trouble of looking at .desktop files.
__________________
Class .. : Meddler, Thread watcher, Developer, Helper
Humor .. : [********--] Alignment: Pacifist
Patience : [*****-----] Weapon(s): N900, N950, Metal music
Agro ... : [----------] Relic(s) : N95, NGage, Tamyia Wild One

Try Tweed Suit for your hardcore twittering needs
http://twitter.com/mece66
I like my coffee black, like my metal.
 

The Following 3 Users Say Thank You to mece For This Useful Post:
Posts: 306 | Thanked: 566 times | Joined on Jan 2010 @ Romania
#17
Originally Posted by demolition View Post
For all xterm commands press Ctrl + Tab twice.

There isn't room for the whole list and I haven't worked out how to pipe this list to a file because you're not actually typing a command. Anybody know?

Edit: @ CaptWheeto - Thanks very handy info.

http://talk.maemo.org/showpost.php?p=857534&postcount=2
you can narrow the list by [ first letter of app ] then double tab
 

The Following 3 Users Say Thank You to blue_led For This Useful Post:
Posts: 1,523 | Thanked: 1,997 times | Joined on Jul 2011 @ not your mom's FOSS basement
#18
...and don't forget 'apropos' and 'locate' as well (which are not installed by default).
 

The Following User Says Thank You to don_falcone For This Useful Post:
Posts: 36 | Thanked: 4 times | Joined on Oct 2011
#19
@tuxsavvy

thanksss a lot ...these comands helped me a lot...I didn't know them before..

thanks tuxsavvy!!
 
Posts: 36 | Thanked: 4 times | Joined on Oct 2011
#20
@mece

Superb information.... these commands worked with me and helped me open several applications from the x terminal ....yet sometimes it gives me :not found....but that's not a big deal...

mece when I have and application that is written with 2 or more words.. for example "pocket calc" ---(notice that there is a space between the 2 words).... then in this case would the command be

ls /usr/share/applications/hildon | grep pocket calc

or

ls /usr/share/applications/hildon | grep pocketcalc
i.e written in one word

what command would I enter in this case the 1st or the 2nd?

Last edited by common; 2011-10-06 at 18:47.
 
Reply


 
Forum Jump


All times are GMT. The time now is 09:54.