true - the alias usage was already answered by 'type find' However - if you reorder PATH variable than one could be picking up find from ~/bin for example .... which whould also be reported by 'type find' ... so you are right <== which is redundand here ...
-T On Thu, 2018-10-04 at 15:38 -0700, wes wrote: > "which" won't tell us whether there's an alias in the way or not. it > will > only tell us where an executable file matching the given name exists > in the > user's defined PATH. > > -wes > > On Thu, Oct 4, 2018 at 3:37 PM <tomas.kuchta.li...@gmail.com> wrote: > > > what does: which find > > returns? > > > > On Thu, 2018-10-04 at 13:06 -0700, Rich Shepard wrote: > > > On Thu, 4 Oct 2018, Johnathan Mantey wrote: > > > > > > > Have you tried > > > > /usr/bin/find / -name foo > > > > > > Now that's interesting. Explicitly providing the path works. > > > > > > I'm having other, more serious, issues with this new desktop > > > and I > > > expect > > > that getting the others resolved will fix these, too. > > > > > > Thanks, > > > > > > Rich > > > _______________________________________________ > > > PLUG mailing list > > > PLUG@pdxlinux.org > > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > > _______________________________________________ > > PLUG mailing list > > PLUG@pdxlinux.org > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
