Eliot Moss moss at cs.umass.edu writes:
On 9/24/2014 6:19 PM, Paul.Domaskis wrote:
Andrey Repin anrdaemon at yandex.ru writes:
Paul.Domaskis wrote:
Can anyone suggest how the bash-completion man page is acccessed, and
what M-/ means?
M is for meta, as in the meta escape key functionality in
On 9/25/2014 4:36 PM, Paul.Domaskis wrote:
Eliot Moss moss at cs.umass.edu writes:
On 9/24/2014 6:19 PM, Paul.Domaskis wrote:
Andrey Repin anrdaemon at yandex.ru writes:
Paul.Domaskis wrote:
Can anyone suggest how the bash-completion man page is acccessed, and
what M-/ means?
From
Andrey Repin anrdaemon at yandex.ru writes:
Paul.Domaskis wrote:
I think I will need to deepen my knowledge into the bowels of unix.
This thread is the first I've heard that completion depended on the
command being typed. Thanks, all.
That's the reason for bash-completion package. If you
On 9/24/2014 6:19 PM, Paul.Domaskis wrote:
Andrey Repin anrdaemon at yandex.ru writes:
Paul.Domaskis wrote:
Can anyone suggest how the bash-completion man page is acccessed, and
what M-/ means?
M is for meta, as in the meta escape key functionality in Emacs.
This will work according to the
Gary Johnson garyjohn at spocom.com writes:
David is right: find does accept a file name as the path argument.
I didn't know that. (Obviously.) The man page doesn't really say,
but all references to the path argument suggest that it contains a
directory or list of directories.
Greetings, Paul.Domaskis!
David is right: find does accept a file name as the path argument.
I didn't know that. (Obviously.) The man page doesn't really say,
but all references to the path argument suggest that it contains a
directory or list of directories.
Nevertheless, the completion
The path argument to find must be a directory.
Sorry, but I can't let this go by. The statement above is incorrect,
as a simple test like find /etc/passwd -print would show.
David
On Wed, Sep 17, 2014 at 5:02 PM, Gary Johnson garyj...@spocom.com wrote:
On 2014-09-17, Paul.Domaskis wrote:
On 9/18/2014 11:42 AM, David Boyce wrote:
The path argument to find must be a directory.
Sorry, but I can't let this go by. The statement above is incorrect,
as a simple test like find /etc/passwd -print would show.
Or just find /etc/passwd. (-print has been the default for decades...
The
Andrew DeFaria Andrew at DeFaria.com writes:
On 9/18/2014 11:42 AM, David Boyce wrote:
The path argument to find must be a directory.
Sorry, but I can't let this go by. The statement above is
incorrect, as a simple test like find /etc/passwd -print would
show.
Or just find /etc/passwd.
On 2014-09-18, Paul.Domaskis wrote:
Andrew DeFaria Andrew at DeFaria.com writes:
On 9/18/2014 11:42 AM, David Boyce wrote:
The path argument to find must be a directory.
Sorry, but I can't let this go by. The statement above is
incorrect, as a simple test like find /etc/passwd -print
I'm using the following 64-bit packages:
cygwin 1.7.28-2
bash-completion 1.3-1
If I am in a folder that contains file _vimrc and directory _vimfiles,
filename completion doesn't respond. I type ls _ or ls _v and
press tab -- nothing happens. I can't really do anything about it
because it
Paul.Domaskis writes:
I'm using the following 64-bit packages:
cygwin 1.7.28-2 bash-completion 1.3-1
If I am in a folder that contains file _vimrc and directory
_vimfiles, filename completion doesn't respond. I type ls _ or
ls _v and press tab -- nothing happens. I can't really do
Paul.Domaskis writes:
Paul.Domaskis writes:
I'm using the following 64-bit packages:
cygwin 1.7.28-2 bash-completion 1.3-1
If I am in a folder that contains file _vimrc and directory
_vimfiles, filename completion doesn't respond. I type ls _ or
ls _v and press tab -- nothing happens.
On 2014-09-17, Paul.Domaskis wrote:
Paul.Domaskis writes:
Paul.Domaskis writes:
I'm using the following 64-bit packages:
cygwin 1.7.28-2 bash-completion 1.3-1
If I am in a folder that contains file _vimrc and directory
_vimfiles, filename completion doesn't respond. I type ls _
14 matches
Mail list logo
