'run xterm' fails to open a window

2009-11-04 Thread Florent Fievez
Hi,

2009/11/3 Linda Walsh cyg...@tlinx.org:
 1) to Florent Fievee, (you don't need to answer if you have no good
  reason, but if you do, I'm curious as to your reasoning) --   Why did you
 copy Ken's complete note as into your response, when you
  simply has to say me too?

I simply clicked on reply button of my webmail. I will not do it again ;-)

 2) to both Florent and Ken?

  In addition to Gery Herbozo Jimenez's response and question to you,
  ( Have you tried just starting the XWin server first and the the
  xterm? it looks like the X server doesn't recognize that line
  command. ),
  a) Have you tried starting 'xterm' without 'run' ?

Yes, it works without problem but a cmd window remain and that is
annoying. To explain exactly my situation, I have a Windows cmd script
which try to launch a bash script.

--- rxvtwin.cmd --
@echo on

SET DISPLAY=127.0.0.1:0.0

if defined CYGWIN_ROOT goto :OK
set CYGWIN_ROOT=%~dp0
:OK

SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin

SET PATH=%CYGWIN_ROOT%\bin;%PATH%


%RUN% %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh %*
---

I call it in windows shortcut with a u...@host as parameter and it
launch a rxvt terminal with a ssh session to the host and background
color depending on host.
If instead of %RUN% %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh
%* I launch %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh %*, it
works.
So it seems to be really run which has an issue.



  b) I see you have started 'Xwin'.  Do either of you know what display
     'XWin' started itself on?         If you specified no value, it probably
 created the display :0.0.

Yes my server is running on display 0.0 and I specify it in DISPLAY
environment variable.
 (I specified it in both bash and cmd script since I don't know if
environment is inherited by bash process when I run it)


   Your cygwin path\bin\bash.exe -c 'DISPLAY=:0 xterm'

   for cygwin path='C:\cygwin':

      C:\cygwin\bin\bash.exe -c 'DISPLAY=:0 xterm'
        or
      C:\cygwin\bash\bash.exe -c 'xterm -display :0'
   for cygwin path= 'C:\':     (my value)

      C:\bin\bash.exe -c 'DISPLAY=:0 xterm'
                or

     C:\bash\bash.exe -c 'xterm -display :0'

 The above two commands work on WinXP and Vista under the 1.5.x series
 of Cygwin.

It don't work as I expected since what I have explained before.
But I have a little track : My office has given me a new computer and
with the old I had no problem with the same scripts, the difference
between the two is that the old one was Windows XP 32bits and the new
one is Windows XP 64 bits.
I tried first with cygwin 1.5 and I installed also cygwin 1.7 (I have
the same problem in both installation).


Best Regards,

Florent Fievez

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: Cygwin X query Solaris Login page reloads

2009-11-04 Thread BharathX


Thanks Larry for the reply.

Christopher,


Sorry man, i obviously didn't mean to post it so many times...i was pressing
the 'post message' button and nothing was happening..so had to try it a few
times..finally i got a message that the server is under maintainence. so
that was the reason.

I have the cygcheck file here...i've removed certain paths for obvious
reasons.
http://old.nabble.com/file/p26196300/cygcheck.out cygcheck.out 
Please let me know what else is needed to assist me.
The strange thing is, i can use the same Cygwin.bat to access another
solaris box(sol 10).

Thanks guys
Bharath



Christopher Faylor-8 wrote:
 
 On Mon, Nov 02, 2009 at 04:37:43AM -0800, BharathX wrote:

Hi Guys,

This is my first post so please bear with me...
 
 Actually, it's your sixth identical post.  Please correct the
 malfunction which is causing this.
 
 cgf
 
 --
 Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
 Problem reports:   http://cygwin.com/problems.html
 Documentation: http://x.cygwin.com/docs/
 FAQ:   http://x.cygwin.com/docs/faq/
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Cygwin-X-query-%3CSolaris%3E-Login-page-reloads-tp26156699p26196300.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



META CONTENT: posting format redux: education of a welcome, new community member...?

2009-11-04 Thread Linda Walsh

Florent Fievez wrote:

2009/11/3 Linda Walsh me'em...@me'dom:

^^^ --  another no no**(see bottom)

[curious] Why did you copy [the previous,] complete note
into your response, when [all you said was] me too?


I simply clicked on reply button of my webmail. I will not do it
again ;-)

---

  The point was not whether you hit reply, but whether or not you chose to
edit down the part you included to some minimal subset of the message so as
not to fill the rest of anyone's screen with unnecessary characters.

  Some people (call them group A) use text-only readers that display the
whole message from top to bottom that scrolls your response off the screen
if you fill your message with a copy of a long included response.  As a
result, they have to redisplay your message with paging enabled, just to see
a 1-liner that is placed at the top of the message (call that Style-A).

  Other people (call them group B) using Graphical-readers(GUI's) to read
email only see the first page of a long email, so when someone includes the
whole message and puts a 1-liner at the end (call that style B), have to
manually scroll through a bunch of text they've already read in previous
posts, just to see a one liner.

  Note: Style-A is sometimes called 'top-posting', and Style-B is sometimes
called 'bottom-posting'.   


  When someone is using a GUI, and reads a 'Style-B' message, they have to
slowly scroll through your message, either using the mouse or using some
page-down type character. That can be a tedious and error-prone process

  In both cases it requires more work to read your message which was simply
a me too message that didn't require inclusion of the entire previous
message.  So some people get 'irritated' at having to scroll up or page
through repeated text just to get to a me too response.

  This is even more of a problem for people who have disabilities -- blind
people might have problems reading through tons of repeated text just to get
to important stuff, so its important for you to pare down the extraneous
parts to make it easier in any event.  People with motion disabilities
(including people with RSI type problem (Carpal tunnel, Ulnar 'tunnel', or
spinal problems) may have problems with the extra motions required to read
your text.   


  So, in generally, it's just a good idea to trim down included text to
some minimal context that is needed to make your message make sense --
which is, nearly always, something that is both, considerably less than the
full message, but will also fit on 1 screen, with your message, of those in
group-A and in group-B -- thus making both happy, though, I believe
Style-A (AKA top-posing), as you did, would best serve those using
screen-readers -- which work with GUI's but not usually text-style windows.  


  Note -- you didn't do anything *wrong* -- I'm just letting you know the
problems that other people have raised about posting styles in the past, so
you can be aware, and be conscious about your posting style.  We certainly
don't want any *unconscious postings*! :-)  (been there, done that, got no
T-shirt -- just negative karma points).

  Hopefully I won't get flamed for this, but I'm cross-posting this to the
cygwin main list, as well, where this issue comes up on some periodic basis,
with the hope that my suggestions will be considered: Style-A (AKA
top-posting) is easier on people with disabilities, but excessively quoting
old text such that the new content is scrolled off a screen is also
annoying and wasteful.  For those in Group-B, if they are trying to be
thorough and make sure you had no further comments interspersed with the
content below, they'll still be forced to page through pages of repeated
text). 


  I'll respond to the rest of your note separately on the appropriate list.

Linda

** -- it's also considered a no-no, to include people's actual email
address when responding: use their name instead or at least heavily
obfuscate their email addr, since these emails are archived on publicly
searchable websites and spammers skim these archives to look for email
addresses to send spam to.  I can vouch for getting a considerable amount
of spam sent my list-dedicated email accounts.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



opengl 'visual capabilities' on windows 7

2009-11-04 Thread Luke J. West
Hi,

I've just installed Cygwin 1.7 (Win7 Hmoe Premium) and am trying to get
started with OpenGL.

I have a sample OpenGL program (sample.c) and I get the following.

sh-3.2$ gcc -o sample.bin sample.c -lglut -lglu -lgl

sh-3.2$ ./sample.bin 
freeglut (./sample.bin):  ERROR:  Internal error Visual with necessary
capabilities not found in function fgOpenWindow
Segmentation fault (core dumped)

sh-3.2$ glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: Brian Paul
...
64 GLX Visuals
   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
--
0x21 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16 16  0 0 None
0xc2 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16 16  0 0 None
0xc3 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16 16  0 0 None
0xc4 24 tc  0 24  0 r  y  .  8  8  8  0  0 16  8 16 16 16 16  0 0 None



Any advice or suggestions would be very much appreciated

Luke

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: release scheduling, cygwin 1.7 et al (was Re: X11R7.5 fontcache..)

2009-11-04 Thread Linda Walsh

* Yaakov (Cygwin/X) wrote: http://cygwin.com/acronyms/#RSN :-)
** LW wrote: --I don't suppose you could express that in ISO format? :-)

Larry Hall wrote:

Since you've asked this on multiple lists, I'm going to assume this is
more than just a humorous comment that you don't expect an answer to.


  Posting this as a reply on cygwin would have been more appropriate, as
there, it was obvious, I was *repeating* the question, (I mentioned it came
up on this list), and it was there that I was *probing*, to see if a more
firm day had been given that I had missed.


Cygwin 1.7 will be released as soon as it's ready.

  So I've heard.

There is no specific date at this time. 

---

  Same as before.  So I haven't missed any news and there is still no
timeframe (could still be a year away) for release...  firm dates are one
thing, but we are hoping before Xmas, or Beltane (May Day) would give an
idea.  That said, I very well know  the unpredictable nature of SW
development.  How can one give a real schedule about something that has
never been done before?  


  Managers have pushed the moniker 'software engineering' onto the field --
as though software is something that can be engineered and manufactured like
off-the-shell nuts and bolts.  That does the field a great disservice.  As
writing software is all about creativity.  It's not about creating the nuts
and bolts, but how they go together -- just like painting is not about the
paint, it's about how it goes onto the medium.

  Sure you can give estimates, but reality is they are only best guesses
and any number of things can come up to alter them.  This was known as far
back as 1985.  See good paper at:

  http://dspace.mit.edu/handle/1721.1/48174?show=full

  Says basically, even the act of coming up with a schedule can
[adversely] affect the outcome of not creating one.  The compare it to the
'Heisenberg Uncertainty Principle' But even with such knowledge at your
disposal, you'll still run into Dilbertian manager types who live in a
fantasy world, where, by force of will, they believe they can force a
product into existence on their schedule.  :^)  However, I am not the
manager type -- I'm not ruthless enough.


That's not a reason not to use it however, if you prefer.  And if you need
something that's only on 1.7, this is a good time to try it out.  And
since you can install 1.7 beside 1.5 if you like, your risk of borking
your Cygwin installation is pretty minimal.

---

  I saw support for dual installations in a recent announcement on Cygwin's
main list.  I've also seen quite a few problems reported against 1.7 in the
compatibility department, but I realize that gives no indication of the
number of users who don't have problems.  


The announced wasn't clear if the dual installation support was backwards
compatible to 1.5.  My history with cygwin goes back a bit, to, when having
more than one cygwin install on your disk at the same time was grounds for
being drawn and quartered if you reported any problem in such a setup.  You
know how the cygwin-standard team can be...any excuse for flaying a user
provides them joy (in their 'we take pride in our meaness' way).  :-)

  Maybe when I'm not swamped w/other probs...

  Thanks for the ~informative~ response.  ;^)

-linda


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: release scheduling, cygwin 1.7 et al (was Re: X11R7.5 fontcache..)

2009-11-04 Thread Larry Hall (Cygwin X)

On 11/04/2009 05:05 PM, Linda Walsh wrote:

   I saw support for dual installations in a recent announcement on Cygwin's
main list.  I've also seen quite a few problems reported against 1.7 in the
compatibility department, but I realize that gives no indication of the
number of users who don't have problems.
The announced wasn't clear if the dual installation support was backwards
compatible to 1.5.


It's been possible to install and run Cygwin 1.7 alongside 1.5 since, well, for
quite a long time.  This was seen as a requirement for package maintainers
to start making the move to 1.7 (though it isn't a strict requirement that they
do so).  The announcement that you saw about multiple cygwin1.dlls with
1.7 means that this flexibility has been extended to any 1.7.x version as
well.  So, start dropping 1.7 cygwin1.dlls all over your disk.  It's time to
spread the joy! ;-)

As for compatibility, that's in the eye of the beholder.  But I haven't seen
anything yet that I consider a show-stopper, especially considering that 1.5 is
still going to be there for anyone that can't tolerate 1.7 for some reason. But
that's just my opinion.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/