Between top-posting, bottom-posting, in-line responses, and reading too
fast, I got lost.
As others have mentioned, if you simply want to run 'find' and by-pass any
alias or functions, you can specify the full path (e.g. /usr/bin/find) or
prefix the command with a backslash.
If you want to know w
I think you're misunderstanding the message. He wasn't saying "avoid using
the backslash" - he was saying "avoid issues with aliases by using a
backslash".
English can be pretty vague sometimes (ok, all the time).
-wes
On Fri, Oct 5, 2018 at 6:55 AM Johnathan Mantey wrote:
> What are your reas
What are your reasons for the recommendation?
The case against alias, as shown by this thread, shows one pain point to
compare against the benefit.
What is the issue with the '\' prefix, which I did not know existed.
On Thu, Oct 4, 2018 at 4:49 PM Robert Citek wrote:
> Avoid aliases and function
Avoid aliases and functions with a backslash. For example:
$ \find /etc/ | head
Regards,
- Robert
On Thu, Oct 4, 2018 at 4:38 PM wrote:
> 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 e
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,
"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 wrote:
> what does: which find
> returns?
>
> On Thu, 2018-10-04 at 13:06 -0700, Rich Sh
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, issue
On Thu, 4 Oct 2018, Paul Heinlein wrote:
What does "type find" return?
find is hashed (/usr/bin/find)
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On Thu, 4 Oct 2018, Rich Shepard wrote:
With no alias in ~/.bashrc and a system reboot after upgrading the BIOS
firmware I would be surprised if find still thought there was an alias for
it.
Okay, I was wrong on this because I su'd to root after the reboot and the
alias was still active. Ex
On Thu, 4 Oct 2018, 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 res
I've recently discovered some distros automatically source .bash_aliases if
the file exists. You should probably double check .bash_profiel as well.
Also what does *alias* return?
On Thu, Oct 4, 2018 at 1:08 PM Rich Shepard
wrote:
> On Thu, 4 Oct 2018, wes wrote:
>
> > I feel like the most like
On 10/04/2018 01:07 PM, Rich Shepard wrote:
On Thu, 4 Oct 2018, wes wrote:
I feel like the most likely case in this situation is that the alias is
still in effect, even though you believe you have removed it. Trying the
tests Johnathan and I mentioned will help verify whether this is the case
o
On Thu, 4 Oct 2018, wes wrote:
I feel like the most likely case in this situation is that the alias is
still in effect, even though you believe you have removed it. Trying the
tests Johnathan and I mentioned will help verify whether this is the case
or not.
Wes,
With no alias in ~/.bashrc a
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
On Thu, Oct 4, 2018 at 12:46 PM Rich Shepard
wrote:
> On Thu, 4 Oct 2018, wes wrote:
>
> > For whatever reason, only now did this trigger the memory: didn't you
> talk
> > about making an alias for find to add some parameter by default?
> >
> > Yes, here we are:
>
>True, but I removed the ali
On Thu, 4 Oct 2018, wes wrote:
For whatever reason, only now did this trigger the memory: didn't you talk
about making an alias for find to add some parameter by default?
Yes, here we are:
True, but I removed the alias since it really doesn't matter whether /proc
is examined.
No alias fo
Have you tried
/usr/bin/find / -name foo
?
On Thu, Oct 4, 2018 at 12:41 PM Rich Shepard
wrote:
> On Thu, 4 Oct 2018, Johnathan Mantey wrote:
>
> > Perhaps you have an alias or some such in the way?
>
> Johnathan,
>
>No alias for fimd.
>
> Thanks,
>
> Rich
> __
On Thu, 4 Oct 2018, Johnathan Mantey wrote:
Perhaps you have an alias or some such in the way?
Johnathan,
No alias for fimd.
Thanks,
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
Wow try to find this line inside 'man find'
command [-pVv] command [arg ...]
Run command with args suppressing the normal shell function lookup.
On Thu, Oct 4, 2018 at 12:34 PM Johnathan Mantey wrote:
> BASH provides *command* as an override to specifically bypass redirects
> such as an ali
BASH provides *command* as an override to specifically bypass redirects
such as an alias. If you don't know *find* is really */usr/bin/find* you
can use *command* to tell BASH you don't want it to consider aliases.
On Thu, Oct 4, 2018 at 12:31 PM wes wrote:
> I'm not sure what *command does (as
I'm not sure what *command does (aside from employing Buzz Lightyear), one
can skip alias checking by using a backslash as the first character. ie:
\find / -name stripes.png
-wes
On Thu, Oct 4, 2018 at 12:26 PM Johnathan Mantey wrote:
> Perhaps you have an alias or some such in the way?
>
> Tr
Perhaps you have an alias or some such in the way?
Try *command find ~ -name .bashrc*
On Thu, Oct 4, 2018 at 11:52 AM Rich Shepard
wrote:
> On Thu, 4 Oct 2018, David wrote:
>
> > Try this:
> >
> > find / -name 'stripes.png'
>
> > Not sure it will do anything different,
>
> David,
>
>No
On Thu, Oct 4, 2018 at 11:23 AM Rich Shepard
wrote:
> On Thu, 4 Oct 2018, wes wrote:
>
> > Hopefully someone recognizes this error and can help, it's not one I've
> > seen before. Would you please provide a real-world example, and its
> > complete output? And also the output of find --version?
>
On Thu, 4 Oct 2018, David wrote:
Try this:
find / -name 'stripes.png'
Not sure it will do anything different,
David,
Nope. No difference. and it's a forward slash for searches starting at /
and a dot if starting at the pwd.
echo $SHELL
`echo $SHELL` --version
Same dist
On 10/04/2018 11:20 AM, Rich Shepard wrote:
On Thu, 4 Oct 2018, wes wrote:
Hopefully someone recognizes this error and can help, it's not one I've
seen before. Would you please provide a real-world example, and its
complete output? And also the output of find --version?
wes,
On the new de
On Thu, 4 Oct 2018, wes wrote:
Hopefully someone recognizes this error and can help, it's not one I've
seen before. Would you please provide a real-world example, and its
complete output? And also the output of find --version?
wes,
On the new desktop:
[root@baetis ~]# find / -name stripes.
What is the exact error message?
On Thu, Oct 4, 2018, 11:01 Rich Shepard wrote:
>When I run the command 'find' on the new desktop it fails with the
> message
> that a path needs to preceed the supplied path.
>
>Examples:
>
>As a user I'll type 'find . -name something' and find tells
On Thu, Oct 4, 2018 at 10:57 AM Rich Shepard
wrote:
>When I run the command 'find' on the new desktop it fails with the
> message
> that a path needs to preceed the supplied path.
>
>Examples:
>
>As a user I'll type 'find . -name something' and find tells me a path
> must
> preceed th
When I run the command 'find' on the new desktop it fails with the message
that a path needs to preceed the supplied path.
Examples:
As a user I'll type 'find . -name something' and find tells me a path must
preceed the ., then gives the usage summary.
As root I'll type 'find / -name so
29 matches
Mail list logo
