On 4/12/2010 8:36 AM, Al G. wrote:
It sounds as though no change is required in screen for this.
Correct.
screen is an ancient program from the dim mists of early terminal days, so I'm
not surprised that it has some problems of this kind.
Don't worry, screen isn't doing anything wrong here.
>> It sounds as though no change is required in screen for this.
>
>Correct.
>
>> screen is an ancient program from the dim mists of early terminal days, so
>> I'm
>> not surprised that it has some problems of this kind.
>
>Don't worry, screen isn't doing anything wrong here. Setting the
>VERASE k
Andrew Schulman wrote:
> It sounds as though no change is required in screen for this.
Correct.
> screen is an ancient program from the dim mists of early terminal days, so I'm
> not surprised that it has some problems of this kind.
Don't worry, screen isn't doing anything wrong here. Setting th
Corinna Vinschen:
> I think I see what you mean now. The c_cc[VERASE] value is the one
> which is expected for the VERASE functionality (unless it's set to
> 0 == _POSIX_VDISABLE), but it has nothing to do with the actual setting
> of the backspace key in the terminal. So, actually the key value
> So, what we really need to implement is what you proposed.
It sounds as though no change is required in screen for this. I trust someone
will let me know if it turns out otherwise.
screen is an ancient program from the dim mists of early terminal days, so I'm
not surprised that it has some pro
On Apr 11 11:33, Corinna Vinschen wrote:
> On Apr 10 22:09, Andy Koppe wrote:
> > Christopher Faylor wrote:
> > > The problem is that screen explicitly sets VERASE to 0. I believe that
> > > it does that to mean "there is really no erase character since I'm
> > > handling that".
> >
> > You're ri
On Apr 10 22:09, Andy Koppe wrote:
> Christopher Faylor wrote:
> > I'm not 100% sure that this is the right fix but the new snapshot at
> > least works around the problem.
>
> Thanks.
>
> > The problem is that screen explicitly sets VERASE to 0. I believe that
> > it does that to mean "there is
On Sat, Apr 10, 2010 at 10:09:32PM +0100, Andy Koppe wrote:
>Christopher Faylor wrote:
>> That should not cause Cygwin to send a null character.
>> I think it should probably just send the default \177 character.
>
>Makes sense given the botched design, but of course it does mean that
>the user's b
Christopher Faylor wrote:
> I'm not 100% sure that this is the right fix but the new snapshot at
> least works around the problem.
Thanks.
> The problem is that screen explicitly sets VERASE to 0. I believe that
> it does that to mean "there is really no erase character since I'm
> handling that
On Sat, Apr 10, 2010 at 01:36:07PM -0400, Christopher Faylor wrote:
>On Sat, Apr 10, 2010 at 12:16:26PM -0400, Christopher Faylor wrote:
>>On Sat, Apr 10, 2010 at 05:00:30PM +0100, Andy Koppe wrote:
>>>The issue only affects the specific case of 'screen' running in the
>>>console without 'tty' in t
On Sat, Apr 10, 2010 at 12:16:26PM -0400, Christopher Faylor wrote:
>On Sat, Apr 10, 2010 at 05:00:30PM +0100, Andy Koppe wrote:
>>The issue only affects the specific case of 'screen' running in the
>>console without 'tty' in the CYGWIN settings: the backspace key sends
>>^@ instead of what's set i
On Sat, Apr 10, 2010 at 05:00:30PM +0100, Andy Koppe wrote:
>Christopher Faylor:
>>>Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're
>>>starting your session from), or use one of the other terminals.
>>If setting CYGWIN=tty affects the setting of the backspace key for ptys
>>then
Christopher Faylor:
>>Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're
>>starting your session from), or use one of the other terminals.
>
> If setting CYGWIN=tty affects the setting of the backspace key for ptys
> then that's a bug in Cygwin. You really should *not* be setting
On Sat, Apr 10, 2010 at 10:31:36AM +0100, Andy Koppe wrote:
>Workarounds: Add 'set CYGWIN=tty' to Cygwin.bat (or wherever you're
>starting your session from), or use one of the other terminals.
If setting CYGWIN=tty affects the setting of the backspace key for ptys
then that's a bug in Cygwin. Yo
Al G.:
> using GNU screen (4.00.03) and trying to backspace by
> hitting the backspace key results in nothing happening. The cursor
> doesn't move, the character isn't erased and the command remains the
> same (if you hit Enter whatever your typo was gets the usual error).
Uh oh, this is most like
3: Backspace key not working in GNU screen.
^^^
And there's really no need for this repeated header information. It's
largely content-free in the mail list thread.
On 4/8/2010 4:07 PM, Al G. wrote:
This started happening ar
> From: "Larry Hall (Cygwin)"
> To: cyg...@cygwin.com
> Date: Thu, 08 Apr 2010 16:41:25 -0400
> Subject: Re: 1.7.3: Backspace key not working in GNU screen.
> On 4/8/2010 4:07 PM, Al G. wrote:
>>
>> This started happening around March 23, no problems with sc
On 4/8/2010 4:07 PM, Al G. wrote:
This started happening around March 23, no problems with screen before
then. Since then using GNU screen (4.00.03) and trying to backspace by
hitting the backspace key results in nothing happening. The cursor
doesn't move, the character isn't erased and the comma
This started happening around March 23, no problems with screen before
then. Since then using GNU screen (4.00.03) and trying to backspace by
hitting the backspace key results in nothing happening. The cursor
doesn't move, the character isn't erased and the command remains the
same (if you hit Ente
19 matches
Mail list logo
