On 2018-05-27 14:30:04, Marco Atzeri wrote:
>On 5/27/2018 12:14 PM, Nuzhna Pomoshch via cygwin wrote:
>>Sorry to ask so many questions.
>>
>>In linux, this is easily done with loadkeys (though I have actually
>>patched the keymaps before compiling kbd and the X terminal
>>programs that I use), but
On 5/27/2018 12:14 PM, Nuzhna Pomoshch via cygwin wrote:
Sorry to ask so many questions.
In linux, this is easily done with loadkeys (though I have actually
patched the keymaps before compiling kbd and the X terminal
programs that I use), but I have no idea where those are set it
cygwin.
Thanks
Sorry to ask so many questions.
In linux, this is easily done with loadkeys (though I have actually
patched the keymaps before compiling kbd and the X terminal
programs that I use), but I have no idea where those are set it
cygwin.
Thanks.
--
Problem reports: http://cygwin.com/problems.htm
t; On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
>>>>>> Here's an interesting bug: normally in a Bash session in MinTTY,
>>>>>> backspace and Ctrl+H both delete the previous character, as expected.
>>>>>> However, after running texconfig and re
Here's an interesting bug: normally in a Bash session in MinTTY,
backspace and Ctrl+H both delete the previous character, as expected.
However, after running texconfig and returning to the shell, both the
backspace key and Ctrl+H appear to just print "^H" to the terminal.
It loo
On 3/18/2016 4:14 PM, Yaakov Selkowitz wrote:
On 2016-03-18 06:34, Ken Brown wrote:
The best long-term solution is to get rid of the need for texconfig by
making
tlmgr work on Cygwin[*].
No thanks. Don't we have all of TeX Live packaged already? Wouldn't
using this conflict with the packages
on in MinTTY,
backspace and Ctrl+H both delete the previous character, as expected.
However, after running texconfig and returning to the shell, both the
backspace key and Ctrl+H appear to just print "^H" to the terminal.
It looks like this is genuinely the terminal trying to render a
back
On 3/18/2016 4:34 PM, Yaakov Selkowitz wrote:
On 2016-03-18 15:27, Ken Brown wrote:
On 3/18/2016 4:14 PM, Yaakov Selkowitz wrote:
On 2016-03-18 06:34, Ken Brown wrote:
The best long-term solution is to get rid of the need for texconfig by
making
tlmgr work on Cygwin[*].
No thanks. Don't we
On 2016-03-18 15:27, Ken Brown wrote:
On 3/18/2016 4:14 PM, Yaakov Selkowitz wrote:
On 2016-03-18 06:34, Ken Brown wrote:
The best long-term solution is to get rid of the need for texconfig by
making
tlmgr work on Cygwin[*].
No thanks. Don't we have all of TeX Live packaged already? Wouldn'
On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
Here's an interesting bug: normally in a Bash session in MinTTY,
backspace and Ctrl+H both delete the previous character, as expected.
However, after running texconfig and returning to the shell, both the
backspace key and Ctrl+H appear to just
On Wed, Mar 16, 2016 at 08:34:45AM -0400, Ken Brown wrote:
> On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
> >Here's an interesting bug: normally in a Bash session in MinTTY,
> >backspace and Ctrl+H both delete the previous character, as expected.
> >However, after running
On 3/16/2016 10:00 AM, Adam Dinwoodie wrote:
On Wed, Mar 16, 2016 at 08:34:45AM -0400, Ken Brown wrote:
On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
Here's an interesting bug: normally in a Bash session in MinTTY,
backspace and Ctrl+H both delete the previous character, as expected.
Ho
Am 16.03.2016 um 16:07 schrieb Ken Brown:
On 3/16/2016 10:00 AM, Adam Dinwoodie wrote:
On Wed, Mar 16, 2016 at 08:34:45AM -0400, Ken Brown wrote:
On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
Here's an interesting bug: normally in a Bash session in MinTTY,
backspace and Ctrl+H both delet
On Wed, Mar 16, 2016 at 08:34:45AM -0400, Ken Brown wrote:
> >>>>> On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
> >>>>>> Here's an interesting bug: normally in a Bash session in MinTTY,
> >>>>>> backspace and Ctrl+H both delete the p
On 2016-03-18 06:34, Ken Brown wrote:
The best long-term solution is to get rid of the need for texconfig by making
tlmgr work on Cygwin[*].
No thanks. Don't we have all of TeX Live packaged already? Wouldn't
using this conflict with the packages we already have?
--
Yaakov
--
Problem repo
On 2015-04-10, René Berber wrote:
> On 4/10/2015 2:21 PM, Gary Johnson wrote:
> > On 2015-04-09, René Berber wrote:
>
> >> Why vim on Cygwin doesn't install, or use if you add one, /etc/vimrc?
> >
> > Executing
> > $ vim --version
> > shows
> >system vimrc file: "$VIM/vimrc"
> >
On 4/10/2015 2:21 PM, Gary Johnson wrote:
> On 2015-04-09, René Berber wrote:
>> Why vim on Cygwin doesn't install, or use if you add one, /etc/vimrc?
>
> Executing
> $ vim --version
> shows
>system vimrc file: "$VIM/vimrc"
> user vimrc file: "$HOME/.vimrc"
> 2nd user vi
e or /etc/vimrc on Linux.
I have a.vimrc, yes.
>
> The real question:
>
> Why vim on Cygwin doesn't install, or use if you add one, /etc/vimrc?
>
> On Linux I have one with the following contents (which fixes the
> thread problem):
>
> " Begin /etc/vimrc
>
inux I have one with the following contents (which fixes the
thread problem):
" Begin /etc/vimrc
set nocompatible
set backspace=2
syntax on
set background=dark
if (&term == "iterm") || (&term == "putty")
set background=dark
endif
" End /etc/vimrc
Th
On Apr 9 09:54, Weston Turner wrote:
> I corroborate the original poster's experience with this issue.
>
> Steps to reproduce the issue: for example open a file with vim under
> Cygwin, press: up, up, down, down, left, left, right, right. Vim under
> Cygwin places:
>
> C
> C
> D
> D
> B
> B
> A
On 9. 4. 2015 18:54, Weston Turner wrote:
> I corroborate the original poster's experience with this issue.
>
> Steps to reproduce the issue: for example open a file with vim under
> Cygwin, press: up, up, down, down, left, left, right, right. Vim under
> Cygwin places:
>
> C
> C
> D
> D
> B
> B
Hi,
>>I am using a thinkpad laptop preinstalled win8 system, later
>> upgraded to win8.1. I installed the latest version of cygwin, found
>> when using vim editor can not backspace to delete characters, press
>> the arrow keys appear 'A', 'B' and other
On Wed, Apr 08, 2015 at 09:42:55PM +0800, George jiang wrote:
> Hi,
>I am using a thinkpad laptop preinstalled win8 system, later
> upgraded to win8.1. I installed the latest version of cygwin, found
> when using vim editor can not backspace to delete characters, press
> the ar
On Wed, Apr 08, 2015 at 08:38:11PM +0100, JAS gmail wrote:
> i have a very similar problem. any help on this? many thanks...vim and vi
> same effects.
>
> Sent from my iPhone
>
> > On 8 Apr 2015, at 14:42, George jiang <> wrote:
Please don't post raw email addresses in replies, and please make
rsion of cygwin, found
> when using vim editor can not backspace to delete characters, press
> the arrow keys appear 'A', 'B' and other characters. I follow the
> online presentation solutions, copied from a vimrc_example.vim ubentu
> system files to / home / xx fold
Hi,
I am using a thinkpad laptop preinstalled win8 system, later
upgraded to win8.1. I installed the latest version of cygwin, found
when using vim editor can not backspace to delete characters, press
the arrow keys appear 'A', 'B' and other characters. I follow the
That makes much more sense. Thanks!
On Sun, Sep 7, 2014 at 3:50 PM, Andrey Repin wrote:
> Greetings, Andrey Repin!
>
>> Greetings, Mark Yagnatinsky!
>
>>> Sorry, no quoting this time. I don't have an ssh server either, I'm
>>> using a weird telnet server described here:
>>> http://www.chiark.g
Greetings, Andrey Repin!
> Greetings, Mark Yagnatinsky!
>> Sorry, no quoting this time. I don't have an ssh server either, I'm
>> using a weird telnet server described here:
>> http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/cygwin-terminal-window.html
> That's what mintty is. A PuTT
Oh, ok.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Greetings, Mark Yagnatinsky!
> Sorry, no quoting this time. I don't have an ssh server either, I'm
> using a weird telnet server described here:
> http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/cygwin-terminal-window.html
That's what mintty is. A PuTTY-based telnet (pty) client for C
Sorry, no quoting this time. I don't have an ssh server either, I'm
using a weird telnet server described here:
http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/cygwin-terminal-window.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com
Greetings, Mark Yagnatinsky!
>>> I've tried the following in mintty and in putty, and it happens in both:
>>
>>> First, launch cat or grep or similar.
>>> Type a line with some tabs in it.
>>> Try to backspace them away.
>>
>>> The t
2014 at 11:14 AM, Andrey Repin wrote:
> Greetings, Mark Yagnatinsky!
>
>> I've tried the following in mintty and in putty, and it happens in both:
>
>> First, launch cat or grep or similar.
>> Type a line with some tabs in it.
>> Try to backspace them away.
>
Greetings, Mark Yagnatinsky!
> I've tried the following in mintty and in putty, and it happens in both:
> First, launch cat or grep or similar.
> Type a line with some tabs in it.
> Try to backspace them away.
> The tabs are erased one space at time, leading to ... You know
I'm new to this list, this is my first message; I subscribed less than
an hour ago. Please be gentle if I break etiquette.
I've tried the following in mintty and in putty, and it happens in both:
First, launch cat or grep or similar.
Type a line with some tabs in it.
Try to backspace
Thanks a lot ! For a perfectionist like me this means so much ! Thanks !
2013/1/29 Ken Brown :
> On 1/28/2013 7:40 AM, Ken Brown wrote:
>>
>> On 1/27/2013 3:49 PM, Андрей Забавников wrote:
>>>
>>> In `M-x term`, I type `ab`, press backspace, then `ab_` is visibl
On 1/28/2013 7:40 AM, Ken Brown wrote:
On 1/27/2013 3:49 PM, Андрей Забавников wrote:
In `M-x term`, I type `ab`, press backspace, then `ab_` is visible (_
is space). Hitting enter tells no such command `a`, so the deletion
has effect but the the terminal is not updated correctly. Likewise for
2013/1/28 Ken Brown :
>>>> On 1/27/2013 3:49 PM, Андрей Забавников wrote:
>>>>>
>>>>> In `M-x term`, I type `ab`, press backspace, then `ab_` is visible (_
>>>>> is space). Hitting enter tells no such command `a`, so the deletion
>>>
в :
>> 2013/1/28 Ken Brown :
>>> On 1/27/2013 3:49 PM, Андрей Забавников wrote:
>>>>
>>>> In `M-x term`, I type `ab`, press backspace, then `ab_` is visible (_
>>>> is space). Hitting enter tells no such command `a`, so the deletion
>>>&g
kills that
feature, right ? (And here i'm really asking, because it's been a
while since i was working in Emacs last time).
2013/1/28 Андрей Забавников :
> 2013/1/28 Ken Brown :
>> On 1/27/2013 3:49 PM, Андрей Забавников wrote:
>>>
>>> In `M-x term`, I type
2013/1/28 Ken Brown :
> On 1/27/2013 3:49 PM, Андрей Забавников wrote:
>>
>> In `M-x term`, I type `ab`, press backspace, then `ab_` is visible (_
>> is space). Hitting enter tells no such command `a`, so the deletion
>> has effect but the the terminal is not upda
On 1/27/2013 3:49 PM, Андрей Забавников wrote:
In `M-x term`, I type `ab`, press backspace, then `ab_` is visible (_
is space). Hitting enter tells no such command `a`, so the deletion
has effect but the the terminal is not updated correctly. Likewise for
`home` and `end` buttons.
I can
> -Original Message-
> Behalf Of KARR, DAVID
> Sent: Thursday, January 03, 2013 2:03 PM
> Subject: Backspace in shell doesn't backspace after Cygwin update
>
> My hard drive on my Win7 laptop crashed last week, and I'm now trying to
> get everything I had re
"C:\Cygwin\bin\rxvt.exe -display :0 -fn "Lucida Console-14" -tn
rxvt-cygwin-native -e /bin/bash --login" from a shortcut for a shell outside of
Emacs. When I do this now, it looks ok, but I'm now finding that the Backspace
key just moves the cursor forward one character,
On Thu, Jun 21, 2012 at 2:56 PM, Andrew DeFaria wrote:
> On 6/21/2012 9:09 AM, Ryan Johnson wrote:
>>
>> At this point I'd revert to defaults until I saw a problem worse than
>> those caused by the non-default setting.
>
> I think this is the way to go...
>>
>> If you're only interacting with cygwi
On 6/21/2012 9:09 AM, Ryan Johnson wrote:
At this point I'd revert to defaults until I saw a problem worse than
those caused by the non-default setting.
I think this is the way to go...
If you're only interacting with cygwin and linux at this point, you
should be safe. Solaris and the other Uni
be generated by the backspace
key, and stty erase is by default set to ^? as well, usually. Why don't
you just use the default?
Because some time in the past I had problem with backspace not working
and setting erase to ^h fixed it. I've had this setting for years -
perhaps decad
On 06/21/2012 02:07 AM, Corinna Vinschen wrote:
I'm not quite sure what you're trying to accomplish by enforcing ^H.
The Cygwin console as well as mintty, the Linux console or any X terminal
emulation I'm aware of default to ^? to be generated by the backspace
key, and stty eras
On Jun 20 22:26, Andrew DeFaria wrote:
> On 06/20/2012 07:05 PM, Larry Hall (Cygwin) wrote:
> >>Stated differently, I want the backspace key to move backwards
> >>one space and to erase the previous character, like, for
> >>example, the less man page says it's
On 06/20/2012 07:05 PM, Larry Hall (Cygwin) wrote:
Stated differently, I want the backspace key to move backwards one
space and to erase the previous character, like, for example, the
less man page says it's supposed to.
Now methinks you're just being obtuse.
I'm not trying
On 6/20/2012 8:06 PM, Andrew DeFaria wrote:
On 6/20/2012 11:05 AM, Larry Hall (Cygwin) wrote:
I see the same thing if I set stty erase (in bash) as you did and start a
new shell (bash again) from it. Of course, the parent shell outputs ^? for
any press of backspace. This behavior is the same
On 6/20/2012 11:05 AM, Larry Hall (Cygwin) wrote:
I see the same thing if I set stty erase (in bash) as you did and
start a new shell (bash again) from it. Of course, the parent shell
outputs ^? for any press of backspace. This behavior is the same for
bash started from a command prompt and
On 6/20/2012 11:35 AM, Andrew DeFaria wrote:
Have you ever had the backspace key not go backward on character erasing the
previous character in Windows programs? Neither have I.
This has been bothering me for a while so... I have properly set stty erase
^h and from the bash command line
Have you ever had the backspace key not go backward on character erasing
the previous character in Windows programs? Neither have I.
This has been bothering me for a while so... I have properly set stty
erase ^h and from the bash command line backspace works as expected. But
I often find
h line and it should be green, but it's just white on black..
like the windows command-window.
2) backspace is working, but the graphics is not acting correctly. So when I
type "helllo", then remove the "lo" because there is an L to much, then type
"o" again, it w
On 9/26/2010 9:30 AM, MikeS wrote:
Larry Hall (Cygwin cygwin.com> writes:
On 5/27/2010 10:11 AM, RISINGP1 nationwide.com wrote:
I was having trouble with the backspace key, but it was with pdksh, so I
don't know if this will work for you, but it is worth a try...
Andy Koppe g
Larry Hall (Cygwin cygwin.com> writes:
>
> On 5/27/2010 10:11 AM, RISINGP1 nationwide.com wrote:
> > I was having trouble with the backspace key, but it was with pdksh, so I
> > don't know if this will work for you, but it is worth a try...
> >
> > Andy
On 13 August 2010 10:20, Nuzhna Pomoshch wrote:
> On Tue, 20 Apr 2010 00:12:29 +0100, Andy Koppe wrote:
>
>> From the cygwin-1.7.5 release announcement:
>>
>> - Support DEC Backarrow Key Mode escape sequences
>> (ESC [ ? 67 h, ESC [ ? 67 l) in Windows console.
>>
>> (The first one switches to ^H. Y
On Tue, 20 Apr 2010 10:03:19 +0200, Corinna Vinschen wrote:
> Did you work in xterm or the Linux console lately?
> Try pressing Ctrl-V Backspace in both of them.
> You'll see ^?, not ^H.
I see ^H (because I have set it up so that when I press
the backspace key, I actually get a
On 5/27/2010 10:11 AM, risin...@nationwide.com wrote:
I was having trouble with the backspace key, but it was with pdksh, so I
don't know if this will work for you, but it is worth a try...
Andy Koppe wrote:
From the cygwin-1.7.5 release announcement:
- Support DEC Backarrow Key
I was having trouble with the backspace key, but it was with pdksh, so I
don't know if this will work for you, but it is worth a try...
Andy Koppe wrote:
>From the cygwin-1.7.5 release announcement:
- Support DEC Backarrow Key Mode escape sequences (ESC [ ? 67 h,
ESC [ ? 67 l) in
On Thu, May 27, 2010 at 05:49:53PM +0400, Andrei Dmitriev wrote:
>Dave Korn wrote:
>>On 27/05/2010 11:48, Andrei Dmitriev wrote:
>>>after I installed the cygwin on May 19 the bash console don't recognize
>>>*BACKSPACE* and continue to follow to the righ
Eliot Moss wrote:
On 5/27/2010 6:48 AM, Andrei Dmitriev wrote:
** Hello,
after I installed the cygwin on May 19 the bash console don't recognize
*BACKSPACE* and continue to follow to the right each time I
press BACKSPACE.
Although, seem it actually erases the chars from the
Dave Korn wrote:
On 27/05/2010 11:48, Andrei Dmitriev wrote:
** Hello,
after I installed the cygwin on May 19 the bash console don't recognize
*BACKSPACE* and continue to follow to the right each time I
press BACKSPACE.
Although, seem it actually erases the chars from the
On 27/05/2010 11:48, Andrei Dmitriev wrote:
> ** Hello,
>
> after I installed the cygwin on May 19 the bash console don't recognize
> *BACKSPACE* and continue to follow to the right each time I
> press BACKSPACE.
> Although, seem it actually erases the chars fr
** Hello,
after I installed the cygwin on May 19 the bash console don't recognize
*BACKSPACE* and continue to follow to the right each time I
press BACKSPACE.
Although, seem it actually erases the chars from the left (ENTER says
nothing - so I concluded the command is
Andy Koppe wrote:
> Matthias Meyer wrote:
>> cygwin 1.7.5 need, at least, the /usr/share/terminfo/63/cygwin file.
>>
>> cygwin 1.7.2, used by the actual copssh distribution, didn't need this
>> file.
>
> Third-party Cygwin distributions like copssh aren't supported here.
>
> /usr/share/terminfo
Matthias Meyer wrote:
> cygwin 1.7.5 need, at least, the /usr/share/terminfo/63/cygwin file.
>
> cygwin 1.7.2, used by the actual copssh distribution, didn't need this file.
Third-party Cygwin distributions like copssh aren't supported here.
/usr/share/terminfo isn't used by the Cygwin DLL, so th
Hello,
The solution should not be far away ;-)
cygwin 1.7.5 need, at least, the /usr/share/terminfo/63/cygwin file.
cygwin 1.7.2, used by the actual copssh distribution, didn't need this file.
Somebody knows:
1) what is the job of the other directories (41..78)
below /usr/share/terminfo ?
2) has
Andy Koppe wrote:
> Matthias Meyer:
>>> I'm stumped. I think 'cygcheck -svr' output is needed to
>>> get any further. Please attach, not include it, and make sure you
>>> delete any sensitive info from it first.
>>
>> see attachment :-)
>
> You've got Cygwin installed under 'C:/Program Files', wh
Matthias Meyer:
>> I'm stumped. I think 'cygcheck -svr' output is needed to
>> get any further. Please attach, not include it, and make sure you
>> delete any sensitive info from it first.
>
> see attachment :-)
You've got Cygwin installed under 'C:/Program Files', which I suspect
is likely to cau
Andy Koppe wrote:
> Matthias Meyer:
>> Andy Koppe wrote:
>>> Matthias Meyer wrote:
>>>> I've installed cygwin 1.7 in Vista and have two problems, not known
>>>> prior with cygwin 1.5.25:
>>>>
>>>> 1) If I login in a shell (e.
On 30/04/2010 08:14, Sameer khan wrote:
> Hi,
>
> I installed cygwin 1.7.5-1. on my windows-xp desktop.
> On cygwin command prompt, backspace is not working.
> I tried following , but none of these worked
> stty erase ^H
> stty erase ^h
> stty erase ^?
>
> backsp
On Apr 19 18:52, risin...@nationwide.com wrote:
> 2) Once the console window is open, enter the command "stty erase ^?"
> (this is the incorrect character value (0x7f) that the backspace key is
> now sending in the console window - it should be sending ^H (0x08) like it
&
RISINGP1:
> The ability to modify the character value generated by the Backspace key
> is a logical solution rather than forcing people to accept a change to the
> 0x7f value.
>From the cygwin-1.7.5 release announcement:
- Support DEC Backarrow Key Mode escape sequences (ESC [
When using the "set -o vi" mode in pdksh, the backspace key is no longer a
movement key - it does not make the cursor move to the left over the
existing characters leaving them unchanged when the command line edit mode
is entered using the ESC key. The cursor does not move at all.
hing wrong here. Setting the
VERASE key on the console device to _POSIX_VDISABLED (i.e., zero) is
perfectly legitimate, it's the console using that as the backspace
keycode that caused the problem.
@ Larry: Sorry, still not used to responding to the digests. I PEBCAKd
the Spam info.
Where
't doing anything wrong here. Setting the
>VERASE key on the console device to _POSIX_VDISABLED (i.e., zero) is
>perfectly legitimate, it's the console using that as the backspace
>keycode that caused the problem.
@ Larry: Sorry, still not used to responding to the digests. I PEB
hing wrong here. Setting the
VERASE key on the console device to _POSIX_VDISABLED (i.e., zero) is
perfectly legitimate, it's the console using that as the backspace
keycode that caused the problem.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://
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, actua
> 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
> > > handling that".
> >
> > You're right. Zero is the value of the _POSIX_VDISABLE constant for
> > disabling special characters. Therefore, using c_cc[VERASE] as the
> > backspace keycode was a bad idea all along. Sorry for suggesting it in
> > the
> > it does that to mean "there is really no erase character since I'm
> > handling that".
>
> You're right. Zero is the value of the _POSIX_VDISABLE constant for
> disabling special characters. Therefore, using c_cc[VERASE] as the
> backspace
mean that
>the user's backspace keycode setting is ignored. Also, 'screen' would
>be expecting what was set in c_cc[VERASE] as the backspace keycode.
Uh, no. I made it send \177 when c_cc[VERASE] is 0. Screen is just
forwarding characters along so it doesn't care.
c
r since I'm
> handling that".
You're right. Zero is the value of the _POSIX_VDISABLE constant for
disabling special characters. Therefore, using c_cc[VERASE] as the
backspace keycode was a bad idea all along. Sorry for suggesting it in
the first place.
> That should not cause Cy
>>>console without 'tty' in the CYGWIN settings: the backspace key sends
>>>^@ instead of what's set in the console's stty settings. Yes, I assume
>>>it's a Cygwin bug.
>>
>>Since setting CYGWIN=tty is pretty much equivalent to runnin
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 k
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
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 Cy
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 t
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)
On 4/9/2010 12:30 PM, Al G. wrote:
From: "Larry Hall (Cygwin)"
^^^
<http://cygwin.com/acronyms/#PCYMTNQREAIYR>. No need to feed the spammers.
To: snipped
^^^
Here too.
Date: Thu, 08 Apr 2010 16:41:25 -0400
Subject: Re: 1.7.
> 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 eras
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 (
2009/12/25 Andy Koppe:
> 2009/12/25 Ric Anderson:
>> For a variety of reasons, I need a way to switch the character sent by the
>> Console Window Backspace key from ASCII \177 to ASCII \008 (that is, make
>> the backspace key send the ASCII backspace character like it d
2009/12/25 Ric Anderson:
> For a variety of reasons, I need a way to switch the character sent by the
> Console Window Backspace key from ASCII \177 to ASCII \008 (that is, make
> the backspace key send the ASCII backspace character like it did in older
> cygwin versions).
Can'
For a variety of reasons, I need a way to switch the character sent by
the Console Window Backspace key from ASCII \177 to ASCII \008 (that is,
make the backspace key send the ASCII backspace character like it did in
older cygwin versions).
I thought of using dumpkeys/loadkeys, but I can&#
On Thu, Dec 4, 2008 at 12:00 PM, Brian Dessent <[EMAIL PROTECTED]> wrote:
> Jonathon Merz wrote:
>
>> I recently upgraded from rxvt-20050409-7 to rxvt-20050409-9 and have
>> stopped getting different output for Backspace and Control-Backspace.
>> In rxvt-20050409-7,
Jonathon Merz wrote:
> I recently upgraded from rxvt-20050409-7 to rxvt-20050409-9 and have
> stopped getting different output for Backspace and Control-Backspace.
> In rxvt-20050409-7, I get ^? for Backspace and ^H for
> Control-Backspace. In rxvt-20050409-9, I get ^H for both.
>
1 - 100 of 166 matches
Mail list logo
