I have observed an issue in vim and mutt as of August 2012, which has
persisted to now. From conversations with some other cygwin users, the issue
may not be strictly related to ncurses based applications (mined apparently
suffers similarly), but my experience is limited to those.
In mutt, the (.
Could it be that a mount point called /home, or //home (if possible), makes a
difference?
- Original Message -
From: cygwin-ow...@cygwin.com
To: cygwin@cygwin.com
Sent: Wed Jul 15 04:46:35 2009
Subject: Re: [1.7] bug in chdir
On Jul 14 21:47, Eric Blake wrote:
> $ ls //home
> ls: read
--confirm-exit-error ?
- Original Message -
From: cygwin-ow...@cygwin.com
To: cygwin@cygwin.com
Sent: Wed Mar 25 20:50:45 2009
Subject: Re: MinTTY 0.4-alpha1
Frank Fesevur:
> An minor option I would like is to always close MinTTY, even when bash
> exits with status code. Now I need to p
Apologies for violating sane quoting convention, but I'm working off a
crapberry.
Wrt to window titles: change your PS1 prompt to no longer reassign the title
with the pwd (assuming you still have the default definition from /etc/profile
(or similar)) and use the same escape sequience it uses
After a recent upgrade of what appears to be tetex and x11 stuff, I see the
following generated on stderr prior to any normal response from a man query:
Unrecognized line in config file (ignored)
JNROFF LANG=ja_JP.UTF-8 /usr/bin/groff -Tnippon -mandocj
Unrecognized
On Fri, Jun 04, 2004 at 12:32:46PM -0400, Igor Pechtchanski wrote:
> On Fri, 4 Jun 2004, Ashok Vadekar wrote:
>
> > I have a bash script that ran cleanly under 1.5.9x, that now exhibits some
> > disturbing behaviour under a recent upgrade. The gist of the problem is that
&g
I have a bash script that ran cleanly under 1.5.9x, that now exhibits some
disturbing behaviour under a recent upgrade. The gist of the problem is that
the execution of
compact /c file.exe >NUL
which used to run and produce no output (due to the redirect) now actually
puts the output into
picks up the window size.
> Igor
> [*] It is on Win2k, FWIW.
>
> On Fri, 23 Apr 2004, Ashok Vadekar wrote:
>
> > I get the behaviour even if I comment out all the complex PS1
> > definitions in /etc/profile. To see it, open a bash (windows console, I
> > don&#
I get the behaviour even if I comment out all the complex PS1 definitions in
/etc/profile. To see it, open a bash (windows console, I don't know about rxvt)
and resize it to be larger than the 80x25 (mode.com con lines=50 cols=120).
Then type away (at a prompt) and see that the text will wrap at ~
I seem to have the following repeatable problem since upgrading to 1.5.x
from 1.3.x:
open bash shell (in Windows command prompt DOS box, not rxvt)
vi foo (works fine)
:q
telnet remote machine (in my case a solaris 8 box)
exit
vi foo (w
With a recent new system, I found that setup was aborting, generating neither
error message nor /var/log/setup.log* output. After a little messing around,
I found that my mount point for /tmp was cuasing the problem. After
umount(ing) /tmp, setup worked again. Should this (/tmp being a mounted
d
one would expect. Seems like top is actually
blocked trying to get at some windows resource that the closing shell has
locked.
On Fri, Jun 06, 2003 at 03:40:24PM -0400, Ashok Vadekar wrote:
> I've stumbled across some peculiar behaviour for top. I've got the following
> script (v
I've stumbled across some peculiar behaviour for top. I've got the following
script (vping) that I use to keep a VPN connection alive:
#!/bin/sh
while true;
do
ping -n 1 remoteMachine >/dev/null
sleep 60
It would seem to me that this should be easily accomplished by wrapping
open()/fopen() with code that does some sort of glyph recoding for uppercase
characters. Getting the library code to access your wrapper would be a minor
macro issue.
While this may not be the answer you were originally look
I noticed recently that shutdown from a bash causes a "End program now" dialogue
to pop up (for the bash console which is still running shutdow). Perhaps some
other application is not closing and you can't see it (if it's a remote
connection).
On Tue, Mar 12, 2002 at 10:38:50AM +0100, Corinna Vi
I recently updated my visual C installation, and for paranoia reasons I
maintained the original install (neither uses the registry, they are just
directory trees for command-line use). I happened to put the new tree
a little "deeper" that the original install, and noticed that I can't grep throu
16 matches
Mail list logo
