>
> no joy - locate does not tell me anything at all - I got no errors, just
> no output
Either you have a typo (case sensivity?) or your locate database has simply
not been generated. Never mind:
Consult the package management, it should knwo what files it installed
(package management is one of the great advantages of linux over MS
Windows):
> rpm -qa|grep -i “emacs”
This lists you all packages that deal with firefox. Then:
> rpm -ql “emacs-x11”
This is the list of all files installed by that package. Can you spot it ?
Otherwise:
> rpm -ql “emacs-x11”|grep bin
On 2012-07-14 01:26, coasterad wrote:
>
> no joy - locate does not tell me anything at all - I got no errors, just
> no output
You have to install locate first, the package is named “findutils-locate”.
But to find applications “which” is faster (because it only finds
applications, locate finds any file).
cer@Telcontar:~> which emacs
/usr/bin/emacs
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On Fri, 13 Jul 2012 23:43:07 +0000, Carlos E. R. wrote:
> You have to install locate first, the package is named
> “findutils-locate”.
> But to find applications “which” is faster (because it only finds
> applications, locate finds any file).
which only finds what’s in the path by default.
And if he got no error message, then locate clearly is installed,
otherwise he’d have gotten an error saying the command was invalid (or if
cnf was installed, it would’ve suggested a correction).
On 2012-07-14 01:56, Jim Henderson wrote:
> On Fri, 13 Jul 2012 23:43:07 +0000, Carlos E. R. wrote:
>> But to find applications “which” is faster (because it only finds
>> applications, locate finds any file).
>
> which only finds what’s in the path by default.
and that’s the case with any system installed application
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 07/13/2012 03:43 PM, Carlos E. R. wrote:
> On 2012-07-14 01:26, coasterad wrote:
>>
>> no joy - locate does not tell me anything at all - I got no errors, just
>> no output
>
> You have to install locate first, the package is named “findutils-locate”.
> But to find applications “which” is faster (because it only finds
> applications, locate finds any file).
>
>
> cer@Telcontar:~> which emacs
> /usr/bin/emacs
>
FWIW, almost all userland programs are in /usr/bin/. There are
exceptions, but I generally find what I’m looking for there…
On Sat, 14 Jul 2012 00:23:06 +0000, Carlos E. R. wrote:
> On 2012-07-14 01:56, Jim Henderson wrote:
>> On Fri, 13 Jul 2012 23:43:07 +0000, Carlos E. R. wrote:
>
>>> But to find applications “which” is faster (because it only finds
>>> applications, locate finds any file).
>>
>> which only finds what’s in the path by default.
>
> and that’s the case with any system installed application
On Sat, 14 Jul 2012 11:48:06 +0000, Carlos E. R. wrote:
> On 2012-07-14 07:46, Jim Henderson wrote:
>> On Sat, 14 Jul 2012 00:23:06 +0000, Carlos E. R. wrote:
>
>> Locate will find it if it’s not in the path.
>
> True, but it will also find data files of the same name. Look:
>
>
> cer@Telcontar:~> locate emacs | wc -l 5086
>
> How do you find the correct path in those five thousand lines? I know
> how to do it, but he might not
On Sat, 14 Jul 2012 18:18:06 +0000, Carlos E. R. wrote:
> On 2012-07-14 19:51, Jim Henderson wrote:
>> On Sat, 14 Jul 2012 11:48:06 +0000, Carlos E. R. wrote:
>
>
>>> How do you find the correct path in those five thousand lines? I know
>>> how to do it, but he might not
>>
>> locate emacs | grep bin
>>
>> Job done.
>
> Closer
>
>
>
> It matches on things like “/usr/share/emacs/23.2/lisp/bindings.el”. I
> would use “bin/”, but by that time “which emacs” is more accurate and
> faster
Only if it actually ends up in the user’s path (which might not happen if
the user has modified their path to exclude where emacs ends up, or has
installed from source to a non-standard and non-pathed location).
Otherwise, which doesn’t find it, which is what my point was. Why you
want to argue that, I’ve no idea. I simply was pointing out a way to
find the executable that didn’t depend on the path being set correctly.
On 2012-07-14 23:58, Jim Henderson wrote:
> On Sat, 14 Jul 2012 18:18:06 +0000, Carlos E. R. wrote:
>
>> On 2012-07-14 19:51, Jim Henderson wrote:
>>> On Sat, 14 Jul 2012 11:48:06 +0000, Carlos E. R. wrote:
>>
>>
>>>> How do you find the correct path in those five thousand lines? I know
>>>> how to do it, but he might not
>>>
>>> locate emacs | grep bin
>>>
>>> Job done.
>>
>> Closer
>>
>>
>>
>> It matches on things like “/usr/share/emacs/23.2/lisp/bindings.el”. I
>> would use “bin/”, but by that time “which emacs” is more accurate and
>> faster
>
> Only if it actually ends up in the user’s path (which might not happen if
> the user has modified their path to exclude where emacs ends up, or has
> installed from source to a non-standard and non-pathed location).
> Otherwise, which doesn’t find it, which is what my point was. Why you
> want to argue that, I’ve no idea. I simply was pointing out a way to
> find the executable that didn’t depend on the path being set correctly.
Well, I also do not understand why you argue that way.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)