Re: Using konsole in Cygwin

2010-08-06 Thread JOHNER Jean 066030
On Thu, 5 Aug 2010, Thomas Dickey wrote:
 iirc, cygwin has xterm, rxvt and rxvt-unicode

which are very nice tools. And also Mintty which is great.
But console has also interesting features (multiple shells in the same
window in different tabs for example).

From your answer, I conclude that konsole is not available in Cygwin.
I guess the answer is the same for GNOME-termimal.
Do you confirm?

Best regards.

Jean Johner

--
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: Using konsole in Cygwin

2010-08-06 Thread Thomas Dickey

On Fri, 6 Aug 2010, JOHNER Jean 066030 wrote:


On Thu, 5 Aug 2010, Thomas Dickey wrote:

iirc, cygwin has xterm, rxvt and rxvt-unicode


which are very nice tools. And also Mintty which is great.
But console has also interesting features (multiple shells in the same
window in different tabs for example).

From your answer, I conclude that konsole is not available in Cygwin.
I guess the answer is the same for GNOME-termimal.
Do you confirm?


that's my understanding - there was just this week a thread on this
list which stated that.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

--
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: How to launch an xterm using Monospace font

2010-08-06 Thread JOHNER Jean 066030
On Thu, 5 Aug 2010, Thomas Dickey wrote:
 I would like to launch an xterm terminal using Monospace font.
 Monospace is the font used by default by gvim.
 I tried:
 xterm -fn Monospace

 xterm -fa Monospace

 is perhaps what you meant.

Thank you for your quick answer.
xterm -fa Monospace
gives no error message but open xterm with the same font (which is not
Monospace) as:
xterm

If you try
xterm -fa foobar
you also get the same result, for any foobar string.

Best regards.

Jean Johner

--
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: How to launch an xterm using Monospace font

2010-08-06 Thread Thomas Dickey

On Fri, 6 Aug 2010, JOHNER Jean 066030 wrote:


On Thu, 5 Aug 2010, Thomas Dickey wrote:

I would like to launch an xterm terminal using Monospace font.
Monospace is the font used by default by gvim.
I tried:
xterm -fn Monospace



xterm -fa Monospace



is perhaps what you meant.


Thank you for your quick answer.
xterm -fa Monospace
gives no error message but open xterm with the same font (which is not
Monospace) as:
xterm


yes (one of the features of Xft is that it provides no error messages,
but simply uses the default font if there's any problem...)


If you try
xterm -fa foobar
you also get the same result, for any foobar string.


That sounds as if the strings you're giving don't match the available
font family names.  If you have fc-list, it can give a list of names.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

--
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/



[ANNOUNCEMENT] Updated xorg-server-1.8.2-1

2010-08-06 Thread Yaakov (Cygwin/X)
The following package has been updated in the Cygwin distribution:

*** xorg-server-1.8.2-1
*** xorg-server-dmx-1.8.2-1

This is an update to the latest upstream release of the X servers.

Support for RANDR display resizing was added.  In windowed mode, this
requires the XWin -resize option; in multiwindow mode, the display will
automatically resize to match a change in Windows display resolution.
See XWin(1) for details.

Additional patches:
- Generate X keycodes for multimedia keys.
- Update mapping for Canadian keyboard layouts.
- Add -resize command line option.
- Internal WM workaround for Java AWT bug.
- Fix a GDI bitmap resource leak of window icons.
- Store pthread_ids and chain IOError handlers to avoid longjmp across
threads.
- Make select() poll and not block if there are unprocessed Windows
messages.
- Better keyboard debugging output.
- Show any fatal error message.


Yaakov
Cygwin/X

-- 

CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO
==

If you want to unsubscribe from the cygwin-xfree-announce mailing list,
please use the automated form at:

http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then look at the List-Unsubscribe:  tag in the
email header of this message.  Send email to the address specified
there.  It will be in the format:

cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.



--
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: How to launch an xterm using Monospace font

2010-08-06 Thread JOHNER Jean 066030
On Fri, 6 Aug 2010, Thomas Dickey wrote:
 If you try
 xterm -fa foobar
 you also get the same result, for any foobar string.

 That sounds as if the strings you're giving don't match the available
 font family names.  If you have fc-list, it can give a list of
names.

fc-list results in many fonts being listed but no Monospace!
Times is in the list. I tried:
xterm -fn Times
xterm -fn Times-12
xterm -fa Times
xterm -fa Times-12

Always the same result with the same default font.

Has anybody been able to launch xterm with a font (any is welcome) which
is not the default?

That would give a track before going in the details of unix fonts
literature.

Thank you for your help.

Jean Johner 

--
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: [ANNOUNCEMENT] Updated xorg-server-1.8.2-1

2010-08-06 Thread Jon TURNEY

On 06/08/2010 10:21, Yaakov (Cygwin/X) wrote:

The following package has been updated in the Cygwin distribution:

*** xorg-server-1.8.2-1
*** xorg-server-dmx-1.8.2-1

This is an update to the latest upstream release of the X servers.

Support for RANDR display resizing was added.  In windowed mode, this
requires the XWin -resize option; in multiwindow mode, the display will
automatically resize to match a change in Windows display resolution.
See XWin(1) for details.


I'm afraid I made a mistake when updating the XWin(1) man page when adding the 
description of '-resize'.  '-resize' is also required in multiwindow mode to 
activate resize support.  Also, something like the following needs to be added:


In -multwindow or -rootless mode, if the X screen is
of the same dimensions as a Windows monitor or the virtual desktop,
the X server will respond to the WM_DISPLAYCHANGED sent when those
dimensions change by resizing the X screen.  Changing the size
of the X screen using the RANDR extension is not permitted.

We'll probably make -resize on by default in -multiwindow mode in the future, 
after more testing and feedback.



Additional patches:
- Generate X keycodes for multimedia keys.
- Update mapping for Canadian keyboard layouts.
- Add -resize command line option.
- Internal WM workaround for Java AWT bug.
- Fix a GDI bitmap resource leak of window icons.
- Store pthread_ids and chain IOError handlers to avoid longjmp across
threads.


Just to clarify, this should fix the problem of X crashing during shutdown, 
leaving behind a stale lock file.  Which should in turn fix the problem of not 
being able to start X if it was previously run by an Administrator if you 
aren't an Administrator.


If there are still problems with multiple users of X on the same computer, 
either sequentially or in parallel, we'd like to hear about them.



- Make select() poll and not block if there are unprocessed Windows
messages.
- Better keyboard debugging output.
- Show any fatal error message.


--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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: XWin crash after the launch of startkde on a remote Red Hat 5 machine

2010-08-06 Thread Michel Hummel
2010/8/3 Michel Hummel hummel.mic...@gmail.com:
 Hello,
 I'm using cygwin on Microsoft Windows XP with XWin version :
 sh-3.2# XWin.exe -version
 Welcome to the XWin X Server
 Vendor: The Cygwin/X Project
 Release: 1.8.0.0 (1080)
 Build Date: 2010-04-02
 Contact: cygwin-xfree@cygwin.com

 I think I have found a bug in the XWin reset procedure which leads to
 the start of two clipboard thread's and sometime to a crash of the X
 server.

 The crash can be produced by lauching startkde on a Red Hat 5 remote
 machine (The crash should arrive after some minutes of work)
 but the bug can simply be produced like this :

 On my installation if I launch Xwin with this options :
 XWin :0 -ac
 then I do
 xsetroot -solid '#00'

 After setting the color, Xwin launches its reset procedure because
 there is no more client connected ( the server loses the color but it
 is the normal comportment isn't it ?
 http://sourceware.org/ml/cygwin-xfree/2002-01/msg00106.html)

 The problem comes from the clipboard thread. In this example, when the
 server launches its reset procedure, the clipboard is in state
 Launched but is not in state Started (Boolean variable about
 clipboard status, see file hw/xwin/winclipboardthread.c).

 This particular status of the ClipboardThread during server reset is
 normaly managed by two if statements :

 * An if in the file hw/xwin/InitOutput.c disables the exit of the
 clipboard thread in this state
 Extract of the file hw/xwin/InitOutput.c (with line number) :

  169 winClipboardShutdown (void)
  170 {
  171   /* Close down clipboard resources */
  172   if (g_fClipboard  g_fClipboardLaunched  g_fClipboardStarted)
  173     {
  174       /* Synchronously destroy the clipboard window */
  175       if (g_hwndClipboard != NULL)
  176         {
  177           SendMessage (g_hwndClipboard, WM_DESTROY, 0, 0);
  178           /* NOTE: g_hwndClipboard is set to NULL in
 winclipboardthread.c */
  179         }
  180       else
  181         return;
  182
  183       /* Wait for the clipboard thread to exit */
  184       pthread_join (g_ptClipboardProc, NULL);
  185
  186       g_fClipboardLaunched = FALSE;
  187       g_fClipboardStarted = FALSE;
  188
  189       winDebug (winClipboardShutdown - Clipboard thread has exited.\n);
  190     }
  191 }

 * An if statement in the file hw/xwin/winclipboardwrappers.c
 prohibits the launch of clipboard thread if one is already Launched.
 Extract of the file hw/xwin/winclipboardwrappers.c (with line number)
 256   /* If the clipboard client has already been started, abort */
 257   if (g_fClipboardLaunched)
 258     {
 259       ErrorF (winProcEstablishConnection - Clipboard client already 
 260               launched, returning.\n);
 261       return iReturn;
 262     }


 The problem is that the Boolean variables g_fClipboardLaunched and
 g_fClipboardStarted are re-initialized by the server reset procedure
 (function winInitializeGlobals of the file  hw/xwin/winglobals.c)
 Extract of the file hw/xwin/winglobals.c (with line number)
 128 /*
 129  * Re-initialize global variables that are invalidated 130  * by a
 server reset.
 131  */
 132
 133 void
 134 winInitializeGlobals (void)
 135 {
 136   g_dwCurrentThreadID = GetCurrentThreadId ();
 137   g_hwndKeyboardFocus = NULL;
 138 #ifdef XWIN_CLIPBOARD
 139   g_fClipboardLaunched = FALSE;
 140   g_fClipboardStarted = FALSE;
 141   g_iClipboardWindow = None;
 142   g_pClipboardDisplay = NULL;
 143   g_atomLastOwnedSelection = None;
 144   g_hwndClipboard = NULL;
 145 #endif
 146 }

 The consequence of this Re-initialization in this particular situation
 is that the clipboard thread is launched two times and sometimes leads
 to a crash of the X server.
 You can see the double launch of the clipboard thread at the end of
 the attached log file Xwin.0.log ( 2 times the sentence :
 winClipboardProc - XOpenDisplay () returned and successfully opened
 the display. )

 To fix this bug I purpose to remove the variables g_fClipboardLaunched
 and g_fClipboardStarted of the winInitializeGlobals (void) function,
 as their re-initializations are handled in in the files :
 hw/xwin/InitOutput.c.

 That what is doing the patch Attached to this email.

 Regards,
 Michel Hummel


Hello,
I didn't saw any response to my patch proposition, did someone tried it ?
If I didn't posted it in the good place where should I have to

I will be happy to explain the problem if my first mail wasn't clear.

--
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: Using konsole in Cygwin

2010-08-06 Thread Larry Hall (Cygwin X)

On 8/6/2010 4:21 AM, Thomas Dickey wrote:

On Fri, 6 Aug 2010, JOHNER Jean 066030 wrote:


On Thu, 5 Aug 2010, Thomas Dickey wrote:

iirc, cygwin has xterm, rxvt and rxvt-unicode


which are very nice tools. And also Mintty which is great.
But console has also interesting features (multiple shells in the same
window in different tabs for example).

From your answer, I conclude that konsole is not available in Cygwin.
I guess the answer is the same for GNOME-termimal.
Do you confirm?


that's my understanding - there was just this week a thread on this
list which stated that.


Right.  There are external ports of these but nothing in the distribution
right now.  As for other terminals with things like tabs, you can check
out Poderosa and/or Console2.

--
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/



RE: How to launch an xterm using Monospace font

2010-08-06 Thread Timares, Brian (HP)
JOHNER Jean wrote:
Has anybody been able to launch xterm with a font (any is welcome)
which
is not the default?

Jean,

I think this is what you want.  I have:
XTerm*font: -*-courier-medium-r-*-*-*-100-*-*-*-*-*-*
in my .Xdefaults

Other than colors, here is my .Xdefaults (in my home directory, natch):
XTerm*scrollBar: on
XTerm*saveLines: 9
XTerm*font: -*-courier-medium-r-*-*-*-140-*-*-*-*-*-*
XTerm*visualBell: true
XTerm*titeInhibit: true
urxvt*secondaryScreen: false

The most important part is the XTerm*titeInhibit: true, it is beyond me
why that isn't the default everywhere (it prevents a screen clear when
you're, say, done reading a man page).  I want to get rid of the title
bar but haven't explored that as I launch most of my xterms from a
script. Extract:

nohup xterm -name $h -title $h -ls -mc none +tb +mb -vb -sb -sl 9
-background grey95 -fg black -cr black -ms black -font
-*-lucidatypewriter-medium-*-*-*-*-100-*-*-*-*-*-* -e ssh -Yq r...@$h
/dev/null  21

Naturally $h is the server :)

To get the fonts I launched xfontsel and went through it and
experimented.  Use the 'select' button to put the string into the
buffer.


Brian



--
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: How to launch an xterm using Monospace font

2010-08-06 Thread Timares, Brian (HP)
I wrote:
I want to get rid of the title
bar

Sorry, make that Toolbar.


Brian

--
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/