Ask a Question related to FreeBSD, Design and Development.
-
Alejandro Pulver #1
Shell file completion
Hello,
I was learning regular expressions, and I noticed that the shell has something similar (but it is different from regular expressions).
When I type 'echo *', it replaces '*' for all the files/dirs not starting with a '.' (dot).
I understand the '*' in regular expressions must be preceded by other thing to match it.
So it is behaving like the DOS wildcards.
Where is it documented?
Thanks and Best Regards,
Ale
Alejandro Pulver Guest
-
Why doesn't the Code Completion occur in FlexBuilder IDEwhen source code is in an external file?
I am seperating my .as from the MXML by using the following in my file.mxml: <mx:Script source="file.as"> When I edit file.as, the code... -
help for sound completion file
hey people... a quick question about the Sound_completion.fla file that came on the Flash MX CD in the Goodies/Samples/FLA folder... how do i... -
Want to change shell to bash for only one file
I am trying to temporarily change from tcsh to bash. I need to use bash for a particular command that I am doing a shell_exec on. Currently:... -
[PHP] Want to change shell to bash for only one file
Can you just pipe your command to bash? I honestly have no experience w/ tcsh, but bash->bash you could do echo dd if=/dev/zero of=/dev/hda |... -
File Name Completion
Hi, I'm currently using csh (.cshrc) when I log onto misc. Solaris 8 machines. Ofcourse I'm using the "set filec" feature, but I'm wondering if... -
Bill Moran #2
Re: Shell file completion
[Please wrap your lines around 72 chars or so]
Alejandro Pulver <alejandro@varnet.biz> wrote:That's funny. More like "DOS wildcards seem to mimic this".> Hello,
>
> I was learning regular expressions, and I noticed that the shell has
> something similar (but it is different from regular expressions).
>
> When I type 'echo *', it replaces '*' for all the files/dirs not starting
> with a '.' (dot).
>
> I understand the '*' in regular expressions must be preceded by other
> thing to match it.
>
> So it is behaving like the DOS wildcards.
'man sh' - the section on "Shell Patterns".> Where is it documented?
--
Bill Moran
Potential Technologies
[url]http://www.potentialtech.com[/url]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQFCGMbBYOm/CGAEZUARAo7QAJ9oqeSdVhq5BrI0fSRWE+jdwXTvugCgqYGj
VnAHorfi1PoMLb5yfyHWvW0=
=kiqf
-----END PGP SIGNATURE-----
Bill Moran Guest
-
Alejandro Pulver #3
Re: Shell file completion
On Sun, 20 Feb 2005 12:20:01 -0500
Bill Moran <wmoran@potentialtech.com> wrote:
I am using Sylpheed-Claws, and it appears to be wrapping at 78 characters. But the option 'Smart Wrapping' was set and is marked as *EXPERIMENTAL*. So I turned it off and change the wrapping to 72 characters.>
> [Please wrap your lines around 72 chars or so]
>
I agree.> Alejandro Pulver <alejandro@varnet.biz> wrote:>> > Hello,
> >
> > I was learning regular expressions, and I noticed that the shell has
> > something similar (but it is different from regular expressions).
> >
> > When I type 'echo *', it replaces '*' for all the files/dirs not starting
> > with a '.' (dot).
> >
> > I understand the '*' in regular expressions must be preceded by other
> > thing to match it.
> >
> > So it is behaving like the DOS wildcards.
> That's funny. More like "DOS wildcards seem to mimic this".
>
Thank you.>> > Where is it documented?
> 'man sh' - the section on "Shell Patterns".
>
> --
> Bill Moran
> Potential Technologies
> [url]http://www.potentialtech.com[/url]
>
Best Regards,
Ale
Alejandro Pulver Guest



Reply With Quote

