* Eric Roode (Thu, 20 Nov 2008 06:21:37 -0500)
I do check www.cygwin.com before doing (what I think is going to be) a
routine upgrade. If there's nothing in the news there, I assume that
what I'm getting is just an upgrade of existing packages that I
already have installed. Is that such a
Eric Roode wrote:
My xterms are screwed up. Numlock is very wonky: Let's say I start
off with numlock on; I am in a Windows (non-X) window; I switch to an
xterm; I use the numeric keypad to type; I get nothing (tildes, escape
codes, non-numlock crap). I switch to another xterm, I type
On Wed, 19 Nov 2008 21:43:19 -0500, cygwin at cwilson dot fastmail dot fm wrote:
Eric Roode wrote:
I updated my cygwin the other day, as I periodically do, and I am very
sorry I did so. Here are some of the problems I have encountered.
It has always been the advice of this list that you
Back, Michael wrote:
My point is that relying on a user to have the forethought, time, and
patience to scour through a mailing list archive is probably not the most
effective or convenient form of communicating common upgrade problems and
solutions.
Asking thousands of people to answer
How does the location of the startup batch file affect the behavior of
numlock and capslock in xterm?
Yes. The batch file is different. The binary is different. The
environment variables are different. For example this is in the old
batch file but not in the new one.
SET
Eric Roode wrote:
How amusingly recursive: It has always been the advice of the
mailing lists that you should check the mailing lists before
upgrading :-)
Somehow you found *this* list to complain to. On that same page, there
are two different *-announce lists. What did you think they
On Wed, Nov 19, 2008 at 11:03:11AM -0500, Eric Roode wrote:
I updated my cygwin the other day, as I periodically do, and I am very
sorry I did so. Here are some of the problems I have encountered.
So you just blindly updated without noticing that X was changing? Wow.
It's amazing that you
I have the same Numlock/Capslock issue (see my previous post).
Stop fighting about this, it doesn't help ! Please, does anybody have
a solution ??
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
Dont Care wrote:
I have the same Numlock/Capslock issue (see my previous post).
Stop fighting about this, it doesn't help ! Please, does anybody have
a solution ??
Yes. The location of the startup bat files changed from /usr/X11R6/bin
to /usr/bin. You need to change your start menu shortcuts
On Wed, 19 Nov 2008 17:06:37 -0500, Chuck wrote:
Dont Care wrote:
I have the same Numlock/Capslock issue (see my previous post).
Stop fighting about this, it doesn't help ! Please, does anybody have
a solution ??
Yes. The location of the startup bat files changed from /usr/X11R6/bin
to
Eric Roode wrote:
How does the location of the startup batch file affect the behavior of
numlock and capslock in xterm?
Yes. The batch file is different. The binary is different. The
environment variables are different. For example this is in the old
batch file but not in the new one.
SET
Chuck wrote:
I think the frustration on some people's behalf is that this question
has been asked (and answered) maybe 50 times already on the list.
Perhaps because people can't find the info. they need in any other way than
posting to this list?
I know that I only happened on this list during
On Wed, Nov 19, 2008 at 03:16:05PM -0800, Back, Michael wrote:
Chuck wrote:
I think the frustration on some people's behalf is that this question
has been asked (and answered) maybe 50 times already on the list.
Perhaps because people can't find the info. they need in any other way
than posting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Back, Michael wrote:
I solved this one by guessing and loading the right font pack...
Which font pack contains this one?:
app-image-san-004:station: Warning: Can't chmod /dev/console
XView warning: Cannot load font set
Eric Roode wrote:
I updated my cygwin the other day, as I periodically do, and I am very
sorry I did so. Here are some of the problems I have encountered.
It has always been the advice of this list that you should read the
announcements on cygwin-announce@ and cygwin-xfree-announce before
Back, Michael wrote:
Christopher Faylor did utter a clarion call of great frustration unto the
heavens:
On Wed, Nov 19, 2008 at 03:16:05PM -0800, Back, Michael wrote:
Chuck wrote:
I think the frustration on some people's behalf is that this question
has been asked (and answered) maybe 50
16 matches
Mail list logo
