I finally managed to duplicate this.
On Thu, Jan 08, 2009 at 11:15:13AM -0500, Christopher Faylor wrote:
>On Thu, Jan 08, 2009 at 11:33:49AM +0100, Corinna Vinschen wrote:
>>On Jan 7 00:52, Charles Wilson wrote:
>>> With cygwin-1.7.36:
>>>
>>> $ scp gcc-tools-autoconf-2.59-10-src.tar.bz2 sources
Hi, all.
I'm trying to compile GNU Screen under Cygwin. Right now, I'm failing to
compile an unmodified package, but my goal is to compile with 256 color support.
I downloaded the package via the Cygwin installer and ran
cygport screen-4.0.3-1.cygport almostall
At compile, I get the followin
Interesting feature or bug of MinTTY that does not obtain with any other
terminal emulator with which I'm familiar.
To wit:
If you have a running synchronous script or command to the screen and you
type ^l (Ctrl-l) it will immediately clear the screen before the ongoing
command terminates.
My f
On 1/25/09, Chris Sutcliffe wrote:
> On 1/25/09, Paul McFerrin wrote:
>> I don't like changes in "default" behavior of certain programs. Vim7.2 is
>> one.
>
> Given that this post was entirely Vim specific, it would probably get
> better attention on the vim mailing lists, as opposed to the Cygwin
On Sun, Jan 25, 2009 at 08:32:00PM -0500, Paul McFerrin wrote:
>I was vim had it's own separate mailing list. BTW: What if RTFM ??
If you type either "vim" or "RTFM" into google you will be enlightened.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
I was vim had it's own separate mailing list. BTW: What if RTFM ??
Christopher Faylor wrote:
On Sun, Jan 25, 2009 at 08:13:31PM -0500, Chris Sutcliffe wrote:
On Sun, Jan 25, 2009 at 06:41:35PM -0500, Paul McFerrin wrote:
I don't like changes in "default" behavior of certain programs.
On Sun, Jan 25, 2009 at 08:13:31PM -0500, Chris Sutcliffe wrote:
>On Sun, Jan 25, 2009 at 06:41:35PM -0500, Paul McFerrin wrote:
>>I don't like changes in "default" behavior of certain programs. Vim7.2
>>is one.
>
>Given that this post was entirely Vim specific, it would probably get
>better atten
> I don't like changes in "default" behavior of certain programs. Vim7.2 is
> one.
Given that this post was entirely Vim specific, it would probably get
better attention on the vim mailing lists, as opposed to the Cygwin
list.
Chris
--
Chris Sutcliffe
http://emergedesktop.org
--
Unsubscribe i
I don't like changes in "default" behavior of certain programs. Vim7.2
is one. How can I turn off "autoindent". In my .vimrc file, I have
"set noautoindent" and issued in comand mode ":set notutoindent" but it
still autoindens. If I insert a new line below a .vimrc comment, not
oinly is the
On Sun, Jan 25, 2009 at 03:30:29PM +0100, Sjors Gielen wrote:
> Eric Blake schreef:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>> According to Sjors Gielen on 1/25/2009 6:46 AM:
>>> Hey all,
>>>
>>> In Cygwin (the CVS version), it seems paths starting with two slashes
>>> are "special path
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Sjors Gielen on 1/25/2009 7:30 AM:
> I figured this was by design, but I didn't know there was an explicit
> exception in POSIX for this.
> However, as I'm sure you're aware, there are a lot of Linux applications
> which depend on, for exa
Eric Blake schreef:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Sjors Gielen on 1/25/2009 6:46 AM:
Hey all,
In Cygwin (the CVS version), it seems paths starting with two slashes
are "special paths" for accessing remote machines or bypassing the mount
table.
This however is inco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Sjors Gielen on 1/25/2009 6:46 AM:
> Hey all,
>
> In Cygwin (the CVS version), it seems paths starting with two slashes
> are "special paths" for accessing remote machines or bypassing the mount
> table.
>
> This however is incompatible
Hey all,
In Cygwin (the CVS version), it seems paths starting with two slashes
are "special paths" for accessing remote machines or bypassing the mount
table.
This however is incompatible with Linux, where i.e. //etc is a valid
path. See, for example: (`ls` indicators removed for readability
On Jan 25 01:04, timcygwin wrote:
> Problem is that the existing files in my Windows area have user ownership
> Administrators, group ownership None, e.g.,
> -rwxrwxrwx 1 Administrators None5513 Jul 20 2005
> set_from_reg.awk*
>
> whereas new files created under cygwin have owner t
Dave Korn-6 wrote:
>
> Larry Hall (Cygwin) wrote:
>
>> It's best to just add the users and groups needed the passwd and group
>> files. This will allow Cygwin to work with these users as Windows sees
>> them, which is really what you want. If you just have the current user
>> to add, try:
>>
I have the following cygwin environment set up:
/etc/passwd hacked such that user tim has group 544 rather than 513
tim:unused_by_nt/2000/xp:1002:544:tim
othy,U-olorin\tim,S-1-5-21-**etc**-1002:/home/tim:/bin/bash
cygwin installed on a shared Windows directory (E:\utils\cygwin\), with the
key
17 matches
Mail list logo