Daniel Colascione gmail.com> writes:
>
> On 6/26/11 11:37 AM, Andy wrote:
> > I achieved the desired effect of modifying the nonvirtualized
> > _vimrc by clicking on Compatibility Files to go to the
> > virtualization directory and moving it from there to the location
> > ov the nonvirtualized _v
p7zip is the Unix port of 7-Zip, a file archiver that archives
with very high compression ratios.
p7zip provides /usr/bin/7zr, a standalone minimal version of the
7-zip tool that only handles 7z archives. It also provides
/usr/bin/7za, a statically-linked application that supports packing
and unpa
Den 2011-06-26 17:57 skrev Andrey Repin:
> Greetings, Peter Rosin!
>
>> cygpath, at its core, calls some form of the cygwin_conv_path API. That
>> function takes either a POSIX path or a Win32 path and converts to the
>> other form. Anything interesting or useful that's happening when feeding
>> i
On 6/26/11 11:37 AM, Andy wrote:
> I achieved the desired effect of modifying the nonvirtualized _vimrc by
> clicking
> on Compatibility Files to go to the virtualization directory and moving it
> from
> there to the location ov the nonvirtualized _vimrc (thus overwriting it).
I usually run with
Michael Lutz gmx.net> writes:
>
> Am 26.06.2011 17:14 schrieb Andrew Hancock:
> > Thanks for any comments or suggestions for courses of action. I'm
> > beginning to wonder if a fundamental incompatibility with Windows 7
> > (64-bit, in case it matters) could prevent the use of Cygwin on my
> >
Am 26.06.2011 17:14 schrieb Andrew Hancock:
> Thanks for any comments or suggestions for courses of action. I'm
> beginning to wonder if a fundamental incompatibility with Windows 7
> (64-bit, in case it matters) could prevent the use of Cygwin on my
> machine. Mega- :(
It works as designed (TM
Greetings, Robert Jacobson!
>> Or rename setup.exe to foo.exe.
> I'm both relieved and dismayed that it is so easy to bypass ...
It's not THAT easy. In this regard, UAC is troubling more than helping.
User with limited rights will not be able to affect system stability (except
if using exploits
Greetings, Peter Rosin!
> cygpath, at its core, calls some form of the cygwin_conv_path API. That
> function takes either a POSIX path or a Win32 path and converts to the
> other form. Anything interesting or useful that's happening when feeding
> it a Win32 path and requesting it to convert from
Greetings, Marco atzeri!
> On Win XP cmd.exe, is not always true that the
> two forms are equivalent (we are not anymore on CP/M, DOS age):
C:\Temp>>cd c:/Temp
> The system cannot find the path specified.
This has been fixed for Vista and Win7 to my knowledge.
At least last time I ran into issue
Sorry, this thread has been superseded by "Divergent file system
contents, Cygwin versus Windows 7"
(http://article.gmane.org/gmane.os.cygwin/127335). During the thick
of troubleshooting, I lost track of the fact that I posted this
earlier understanding of the problem.
On Sun, Jun 26, 2011 at 10:
I am seeing two different versions of a file depending on how I access
it. Specifically, the file "C:\Program Files (x86)\Vim\_vimrc" uses
plain text to provide startup specifications for the text editor gvim.
This is the standalone installation for Windows, not the one the one
that comes with Cy
I am seeing two different versions of a file depending on how I access
it. Specifically, the file "C:\Program Files (x86)\Vim\_vimrc" uses
plain text to provide startup specifications for the text editor gvim.
This is the standalone installation for Windows, not the one the one
that comes with Cy
After some web surfing about how to clear the screen in cygwin, I
installed ncurses. /bin/clear.exe is not there, but /bin/clearw.exe
is. Nothing comes up on a search for clearw either in the mailing
list archives or google. Just wondering if this was a filenaming
typo.
--
Problem reports:
13 matches
Mail list logo
