public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Stephan Mueller" <smueller@Exchange.Microsoft.com>
To: "Samuel" <samuel@socal.rr.com>, <cygwin@cygwin.com>
Subject: RE: bash and the delete key
Date: Wed, 31 Jul 2002 13:26:00 -0000	[thread overview]
Message-ID: <BF653A78FF4ED0468924C8721AC5EAE767D62A@df-muttley.dogfood> (raw)

I expect that the old keystrokes will probably be supported pretty much
forever (hmm, does Unix still go into all uppercase mode if you enter
your userid in all caps at login?)

I don't know how universal the old cut/copy/paste keystrokes are, but
Ctrl-C/X/V are universal in Windows apps these days.

I wasn't responding to the message you were responding to (about
Insert), I was responding to yours (about Ctrl-Insert, etc.).  You
suggested that the obsolete Windows keystrokes were a good choice for
use in Cygwin because "if a Windows user were to get in the habit of
using them in Windows then they should be able to use the "correct" keys
by habit".  My objection was to the part were you suggested that Windows
users get into the habit of using the obsolete keys in Windows.

stephan(not necessarily reflecting the views of my employer);


-----Original Message-----
From: Samuel [mailto:samuel@socal.rr.com] 
Sent: Wednesday, July 31, 2002 7:26 AM
To: cygwin@cygwin.com
Subject: Re: bash and the delete key


If I had things my way, I would encourage Microsoft to discontinue
making the transition in the wrong direction. The support of
Shift+Insert,
Ctrl+Insert and Shift+Delete are so universal that I think there would 
Ctrl+be
significant protest if support was discontinued. I understand that you
are advising not to encourage use of them but notice that I responded to
a recomendation to use "Insert" instead of Shift-Insert. I am surprised
that you did not make a comment on use of plain "Insert". Also not that
my reply was for a discussion in which the Microsoft recommendation is
not possible.


----- Original Message -----
From: "Stephan Mueller" <smueller@Exchange.Microsoft.com>
To: "Samuel" <samuel@socal.rr.com>; <cygwin@cygwin.com>
Sent: Tuesday, July 30, 2002 1:11 PM
Subject: RE: bash and the delete key


Please note that the Ctrl-Insert/Shift-Insert/Shift-Delete keystrokes
are legacy, supported for backwards compatibility.  The modern standard
is indeed Ctrl-C/V/X.

From "The Windows Interface Guidelines for Software Design" (covers
Windows 95 and NT! -- so you know it's not brand new :-)

"The system still supports shortcut assignments available in earlier
versions of Microsoft Windows (Alt+Backspace, Shift+Insert,
Ctrl+Insert, Shift+Delete).  You should consider supporting them (though
not documenting them) to support the transition of users."

(This is a footnote in Appendix B, which documents the standard
shortcuts - Ctrl-C/V/X among them).

As long as folks don't actually make the transition, I suspect the OS
will continue to support them, but please, let's not encourage folks to
make the transition in the wrong direction :-)

stephan();



-----Original Message-----
From: Samuel [mailto:samuel@socal.rr.com]
Sent: Tuesday, July 30, 2002 1:03 PM
To: cygwin@cygwin.com
Subject: Re: bash and the delete key


----- Original Message -----
From: "Randall R Schulz" <rrschulz@cris.com>
To: <cygwin@cygwin.com>
Sent: Friday, July 26, 2002 8:31 PM
Subject: RE: bash and the delete key
>
> Mapping the insert clipboard to the "Insert" key is sufficiently 
> "hella-useful."


I did not pay sufficient attention to what I was doing and this reply
got sent to Randall instead of to the list, so it has been delayed a
day.

I don't use Ctrl-V to insert the clipboard; I use Shift-Insert. I use
Ctrl-Insert to copy to the clipboard and Shift-Delete to cut. These have
been standard since Windows 3.1. I learned to use them by using the
technique of remembering that Ctrl-Insert begins with "C" as in "Copy".
If these keys were used in CygWin and if a Windows user were to get in
the habit of using them in Windows then they should be able to use the
"correct" keys by habit. I have encountered very few situations in which
Ctrl-Insert does not work and in the situations it does not work I did
not even think to try using Ctrl-V. I think that one situation in which
Ctrl-Insert does not work is Adobe Acrobat (the find dialog at least)
and all others are less common; at least less commonly used by me.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-07-31 17:53 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 13:26 Stephan Mueller [this message]
2002-08-01 12:07 ` Samuel
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05  8:16 Steve Chapel
2002-07-31 14:27 Barry Buchbinder
2002-07-31 13:33 Jelks Cabaniss
2002-07-31 14:15 ` Paul Derbyshire
2002-07-31 11:07 Barry Buchbinder
2002-07-31 11:36 ` Samuel
2002-07-30 20:55 Stephan Mueller
2002-07-31  3:31 ` Michael Hoffman
2002-07-31  9:48 ` Samuel
     [not found] <20020728170355.GA11806@butch.jgcomp.com>
2002-07-28 17:57 ` Joshua Daniel Franklin
2002-07-28 16:37 Joshua Daniel Franklin
2002-07-28 16:55 ` John Morrison
2002-07-27  3:16 Randall R Schulz
2002-07-27 13:03 ` Nicholas Wourms
2002-07-27 15:54   ` Randall R Schulz
2002-07-28 20:47 ` Andrew DeFaria
2002-07-28 20:56   ` Randall R Schulz
2002-07-28 21:18     ` Christopher Faylor
2002-07-29 10:55       ` Nicholas Wourms
2002-07-29  0:00     ` Gary R. Van Sickle
2002-07-29  0:08       ` Christopher Faylor
2002-07-29  1:21         ` Gary R. Van Sickle
2002-07-28 23:52   ` Gary R. Van Sickle
2002-07-26 10:08 Tony Fenleish
2002-07-26 10:36 ` Randall R Schulz
2002-07-27  0:19   ` Gary R. Van Sickle
     [not found]   ` <NCBBIHCHBLCMLBLOBONKIEMJDCAA.g.r.vansickle@worldnet.att.ne t>
2002-07-27  1:06     ` Randall R Schulz
2002-07-27  1:21       ` Gary R. Van Sickle
2002-07-30 19:59       ` Samuel
2002-07-26 13:40 ` Igor Pechtchanski
2002-07-28 10:06 ` John Morrison
2002-07-25 19:49 Tony Fenleish
2002-07-26  1:30 ` Dylan Cuthbert
2002-07-26  7:29 ` Gerrit P. Haase
2002-07-25 19:00 Paul Derbyshire
2002-07-25 19:49 ` Randall R Schulz
2002-07-25 22:30   ` Sylvain Petreolle
2002-07-26  2:51     ` Paul Derbyshire
     [not found]       ` <Mahogany-0.64.2-2620-20020725-204157.00@MCHASE-COMPAQ>
2002-07-26  4:17         ` Michael A Chase
2002-07-26  4:37     ` Gary R. Van Sickle
2002-07-25 20:13 ` Christopher Faylor
2002-07-26  2:21   ` Paul Derbyshire
2002-07-26  3:15     ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BF653A78FF4ED0468924C8721AC5EAE767D62A@df-muttley.dogfood \
    --to=smueller@exchange.microsoft.com \
    --cc=cygwin@cygwin.com \
    --cc=samuel@socal.rr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).