On May 15 20:12, Yaakov (Cygwin Ports) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Michael Schaap wrote:
> > Yaakov, if possible, could you perhaps release a corresponding gvim as
> > well?
> > (Upgrading to vim-7.1 breaks gvim-7.0, so there is some amount of
> > urgency...)
>
Markus E.L. schrieb:
Possible replacements:
- http://www.cl.cam.ac.uk/research/dtg/attarchive/vnc/index.html (a
archive of the vanished site AFAIK)
- http://www.realvnc.com (The official successor)
- http://www.tightvnc.com/ (Another popular VNC)
and http://www.ultravnc.com/ (Another p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gary Johnson wrote:
> Except that the standard versioned directory structure also allows
> users to put customizations for all users in /usr/share/vim/vimfiles
> while the distributed files go in /usr/share/vim/vim. I
> don't see the advantage to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael Schaap wrote:
> Yaakov, if possible, could you perhaps release a corresponding gvim as
> well?
> (Upgrading to vim-7.1 breaks gvim-7.0, so there is some amount of
> urgency...)
Please understand that, unfortunately, I had no more warning tha
Corinna Vinschen wrote:
1.5.24 only asks the PDC and fails if it's unable to connect to it.
Try a developer snapshot. The function to contact the logon server
has been changed in CVS HEAD to use the newer DsGetDcNameA function
instead of the old NetGetDCName. Only on NT4 Cygwin falls back to
N
Corinna Vinschen wrote:
gem is not part of the ruby standard package.
And don't try to install a "native" gem from the main ruby site and
download gems using that, or you'll end up with a mishmash of cygwin and
native libraries for ruby. Been there, done that :-).
--
Unsubscribe info:
Linda Walsh wrote:
Hi, I don't claim to know what is going on, but I'm
using a dual-core system and haven't noticed the problems you are having,
but my processors are Intel Dual Core. That shouldn't make a difference
I wouldn't think.
Joseph Kowalski wrote:
1) Windows XP, fully updated; 2
On 2007-05-15, Igor Peshansky wrote:
> On Tue, 15 May 2007, Gary Johnson wrote:
>
> > On 2007-05-15, Michael Schaap wrote:
> > > On 14-May-2007 17:05, Corinna Vinschen wrote:
> > > > I have updated the version of vim on cygwin.com to 7.1-1.
> > >
> > > Yaakov, if possible, could you perhaps rele
Thank you.
The new eshell fixed the problem.
> -Original Message-
> From: Dr. Volker Zell
> New Packages in Pre-Release:
> ===
> eshell-1.11-pkg.tar.gz upstream version: 2.4.1
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem repo
On Tue, 15 May 2007, Gary Johnson wrote:
> On 2007-05-15, Michael Schaap wrote:
> > On 14-May-2007 17:05, Corinna Vinschen wrote:
> > > I have updated the version of vim on cygwin.com to 7.1-1.
> >
> > Yaakov, if possible, could you perhaps release a corresponding gvim
> > as well?
> > (Upgradi
On 2007-05-15, Michael Schaap wrote:
> On 14-May-2007 17:05, Corinna Vinschen wrote:
> > I have updated the version of vim on cygwin.com to 7.1-1.
> >
> >
> Yaakov, if possible, could you perhaps release a corresponding gvim as well?
> (Upgrading to vim-7.1 breaks gvim-7.0, so there is some a
All:
I was having a hard time setting a Umask for files that were transfered
via SFTP until Dave Korn kindly pointed me to this link -
http://www.derkeiler.com/Newsgroups/comp.security.ssh/2005-09/0094.html
I made a wrapper that sets the umask to 002 before starting the sftp
server. Files i
On May 15 10:48, Jeff Hawk wrote:
> > From: On Behalf
> > Of Michael Schaap
> > On 14-May-2007 17:05, Corinna Vinschen wrote:
> > > I have updated the version of vim on cygwin.com to 7.1-1.
> > >
> > Yaakov, if possible, could you perhaps release a corresponding gvim as
> > well?
> > (Upgrading to
> -Original Message-
> From: On Behalf
> Of Michael Schaap
> Sent: Tuesday, May 15, 2007 7:00 AM
> To: Cygwin list
> Subject: Attn: Yaakov - gvim (Was: [ANNOUNCEMENT] Updated: vim-7.1-1)
>
> On 14-May-2007 17:05, Corinna Vinschen wrote:
> > I have updated the version of vim on cygwin.com
* Ronald Fischer (Tue, 15 May 2007 15:32:27 +0200)
> I have set my ~/.inputrc like this:
>
> set print-completions-horizontally on
> set show-all-if-ambiguous on
> set show-all-if-unmodified on
> set visible-stats on
>
> But still, when I, for example, enter
>
> ls
>
> the terminal beeps. Ev
* Ronald Fischer (Tue, 15 May 2007 15:37:47 +0200)
> Following the advice in
> http://cygwin.com/cygwin-ug-net/setup-files.html,
> I put the following commands into my .inputrc:
>
> set meta-flag on
> set convert-meta off
> set output-meta on
>
> Still, I can not enter 8-bit characters (such as G
> Theoretically, but there still could be a few things going
> wrong, one of
> which being that you and your Cygwin environment have
> different ideas of
> what $HOME is.
At least, the environment variable HOME is set correctly, and also
my ~/.bash_profile is read, so this suggests that bash *
On Tue, 15 May 2007, Ronald Fischer wrote:
> > Make sure your .inputrc is read.
>
> Hmmm according to the Cygwin documentation page:
>
> ".inputrc controls how programs using the readline library
>(including bash) behave. It is loaded automatically."
>
> So, as long as I stick with the d
Lucio Cosmo wrote:
> Hello All.
>
> I've read some archives on the topic but I cannot understand exactly how
> to solve.
> To be sure, I've installed a brand new machine with
>
> - WinXP
> - MS Visual Studio 7
> - Cygwin
>
> Installed ssh daemon by following the instructions.
> Our target is com
Hello All.
I've read some archives on the topic but I cannot understand exactly
how to solve.
To be sure, I've installed a brand new machine with
- WinXP
- MS Visual Studio 7
- Cygwin
Installed ssh daemon by following the instructions.
Our target is compile from a ssh shell with key (authoma
> Make sure your .inputrc is read.
Hmmm according to the Cygwin documentation page:
".inputrc controls how programs using the readline library
(including bash) behave. It is loaded automatically."
So, as long as I stick with the default name ($HOME/.inputrc),
it should be read without
Following the advice in
http://cygwin.com/cygwin-ug-net/setup-files.html,
I put the following commands into my .inputrc:
set meta-flag on
set convert-meta off
set output-meta on
Still, I can not enter 8-bit characters (such as German umlaut
characters)
in bash shells. What am I missing still?
Ro
On Tue, 15 May 2007, Ronald Fischer wrote:
> I have set my ~/.inputrc like this:
>
> set print-completions-horizontally on
> set show-all-if-ambiguous on
> set show-all-if-unmodified on
> set visible-stats on
>
> But still, when I, for example, enter
>
> ls
>
> the terminal beeps. Even if I set
I have set my ~/.inputrc like this:
set print-completions-horizontally on
set show-all-if-ambiguous on
set show-all-if-unmodified on
set visible-stats on
But still, when I, for example, enter
ls
the terminal beeps. Even if I set in .inputrc:
set bell-style none
it beeps. This applies to rx
On 14-May-2007 17:05, Corinna Vinschen wrote:
I have updated the version of vim on cygwin.com to 7.1-1.
Yaakov, if possible, could you perhaps release a corresponding gvim as well?
(Upgrading to vim-7.1 breaks gvim-7.0, so there is some amount of
urgency...)
Thanks in advance,
- Michael
On 15 May 2007 08:03, Morgan Gangwere wrote:
> it would appear that until we increase the i/o buffer (am i using the
> right term?) to do the cp, we run slower than the windows cp
>
> is there a #DEFINE or some thing that we could add a diff for that
> adventurous people could use?
If you bui
On 15 May 2007 04:04, Karl Kobata wrote:
> Using gcc 3.4.4 on a redhat REL3 linux workstation, I can compile an
> application with no errors, yet if I do the same over on the cygwin gcc
> 3.4.4, I get many errors. Since there are so many errors and the platform
> is the only difference, I would l
Corinna Vinschen wrote:
On May 15 09:58, Carlo Florendo wrote:
Corinna Vinschen wrote:
I have updated the version of vim on cygwin.com to 7.1-1.
Thank you very much. We have been waiting for this for a long time.
You're welcome. I'm just wondering how two days between the official
upstream
On May 15 09:58, Carlo Florendo wrote:
> Corinna Vinschen wrote:
> >I have updated the version of vim on cygwin.com to 7.1-1.
>
> Thank you very much. We have been waiting for this for a long time.
You're welcome. I'm just wondering how two days between the official
upstream release and the Cyg
On 5/14/07, Brian Ford wrote:
On Sat, 12 May 2007, Bob Heckel wrote:
> Why would using Cygwin's cp to copy a large file from one Windows XP
> box to another take 30 minutes but take only 10 minutes if I use drag
> 'n' drop (via Explorer)?
>
> I saw mention of speed in other posts but couldn't f
30 matches
Mail list logo
