Andrey Repin yandex.ru> writes:
> I like bash, but it's no damned explorer, and can't be the one.
> Simple for lack of visualization. My regular "shell" is
> http://farmanager.com/
I would have said that bash is not a damned explorer -- rather, it's
a darn good shell, which can often times be muc
Keith Christian wrote:
> This function echoes the present directory to the clipboard, so that
> I don't have to enter the path manually.
>
> I use this function in a script that sources when a bash shell is
> started. Also echoes the path to the terminal for verification.
> Handy for pasting dire
On 2014-10-01, Paul.Domaskis wrote:
> cygpath -aw foo | tr -d '\n' > /dev/clipboard
Gary Johnson wrote:
> Define a function in your ~/.bashrc.
>
> winclip()
> {
> cygpath -aw "$ " | tr -d '\n' > /dev/clipboard
> }
>
> Then just execute
>
> winclip TheFile
Jim Garrison
Running bash in a Windows environment, I often find the need to
generate a full Windows path to a file so that I can access the file
from a Windows app.
If I use
cygpath -aw TheFile > /dev/clipboard
I can paste into the Windows file-opener without browsing. Also, I
don't need to mouse around
Eliot Moss cs.umass.edu> writes:
>On 9/24/2014 6:19 PM, Paul.Domaskis wrote:
>>Andrey Repin 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.
Andrey Repin 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 remo
Gary Johnson 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.
>
> Nevertheless, th
Andrew DeFaria 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/pas
writes:
> 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
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
> any
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
Gary Johnson spocom.com> writes:
> I have both 32-bit and 64-bit versions of Cygwin installed on a
> Windows 7 Enterprise SP1 system. I can confirm that using a Cygwin
> Terminal, cc works on the 32-bit installation but not on the 64-bit
> installation.
>
> There is no connection between the vi
writes:
> writes:
>> I needed cygwin on a new work computer that was locked down. I
>> created a DVD from all the 64-bit packages some time in the first
>> quarter of 2014, then took the several months needed to get
>> approval for its installation. I then replicated the environment
>> from an o
writes:
> I needed cygwin on a new work computer that was locked down. I
> created a DVD from all the 64-bit packages some time in the first
> quarter of 2014, then took the several months needed to get approval
> for its installation. I then replicated the environment from an old
> work compute
vi editing at bash command line: cc command doesn't work
-
I needed cygwin on a new work computer that was locked down. I
created a DVD from all the 64-bit packages some time in the first
quarter of 2014, then took the several months needed t
Larry Hall (Cygwin cygwin.com> writes:
>On 08/18/2014 10:30 AM, Paul wrote:
>>Andrey Repin yandex.ru> writes:
>>> When I wanted to replicate my cygwin installation from a 32-bit
>>> machine to another 32-bit machine, it was straightforward. I would
>>> simply reinstall all installed packages, bu
Martin Fischer wrote:
>>>>>> Thorsten Kampe writes:
>> * Paul Domaskis (Tue, 22 Apr 2008 16:47:16 -0400)
>>> I will be using a standalone Win2K machine on which I will likely not
>>> have admin access. Will this be a problem, if I choose to install
>
Thorsten Kampe wrote:
> * Paul Domaskis (Tue, 22 Apr 2008 16:47:16 -0400) wrote:
>>
>> I will be using a standalone Win2K machine on which I will likely
>> not have admin access. Will this be a problem, if I choose to
>> install only for the account of interest?
I will be using a standalone Win2K machine on which I will likely not
have admin access. Will this be a problem, if I choose to install
only for the account of interest? There are various web references to
the requirement for admin, but they are generally associated with
specific packages e.g. Op
19 matches
Mail list logo
