Re: AW: AW: possible to run XWin as windows service?
On 7/28/2012 9:08 AM, Paul Maier wrote: The cygwin program run.exe is designed to do just that. It's what I use for this purpose :-) ... I was using run.exe too. run.exe used to hide the window and the task bar entry. But since my upgrade from Cygwin 1.7.9 to 1.7.15, run.exe only hides the window but not the task bar entry, when invoked from the Startup menu in some cases. This seems buggy, see my thread: http://cygwin.com/ml/cygwin/2012-07/msg00473.html But I don't have the impression that a developer accepted this as bug. Do you have a suggestion how to avoid this situation? I used to have difficulty like that with startxwin, but it does not happen any more for me with xlaunch. It did look like a race condition or something ... Eliot -- 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: AW: possible to run XWin as windows service?
On 7/28/2012 8:57 AM, Eliot Moss wrote: On 7/28/2012 8:15 AM, Paul Maier wrote: Can you recommend me how to start the X Server without getting a task bar entry? The cygwin program run.exe is designed to do just that. It's what I use for this purpose :-) ... ... and I just tried it in the Startup folder and it works fine. Here is the "Target" of the shortcut: C:\cygwin\bin\run.exe /usr/bin/xlaunch.exe -p /usr/bin -run ***cygwin-path-to***/config.xlaunch I find the -p makes it easier to write the various files, since it allows cygwin programs to be found. The "Start in" is: C:\cygwin\bin My cygwin installation is in C:\cygwin Regards -- Eliot Moss -- 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: "xterm -si" doesn't hold the line
On Sat, Jul 28, 2012 at 02:49:22PM +0200, Paul Maier wrote: > Hi, > > xterm -si doesn't work as expected. The short answer is that it's always been that way :-) This refers to the scrollTtyOutput, which in xterm is described: scrollTtyOutput (class ScrollCond) Specifies whether or not output to the terminal should automat- ically cause the scrollbar to go to the bottom of the scrolling region. The default is ``true.'' and in rxvt (in the mid-1990s): scrollTtyOutput: boolean True: scroll to bottom when tty receives output; option -si. False: do not scroll to bottom when tty receives output; option +si. However, rxvt (also long ago) implemented a different flavor: scrollWithBuffer: boolean True: scroll with scrollback buffer when tty receives new lines (and scrollTtyOutput is False); option -sw. False: do not scroll with scrollback buffer when tty receives new lines; option +sw. and (relatively recently - two years ago) I implemented a different choice: allowScrollLock (class AllowScrollLock) Specifies whether control sequences that set/query the Scroll Lock key should be allowed, as well as whether the Scroll Lock key responds to user's keypress. The default is "false". When this feature is enabled, xterm will sense the state of the Scroll Lock key each time it acquires focus. Pressing the Scroll Lock key toggles xterm's internal state, as well as tog- gling the associated LED. While the Scroll Lock is active, xterm attempts to keep a viewport on the same set of lines. If the current viewport is scrolled past the limit set by the saveLines resource, then Scroll Lock has no further effect. The reason for setting the default to "false" is to avoid user surprise. This key is generally unused in keyboard configura- tions, and has not acquired a standard meaning even when it is used in that manner. Consequently, users have assigned it for ad hoc purposes. That has the same general effect if Scroll Lock is set - I might still add a "-sw" option like rxvt. > To reproduce (think of a "tail -f" instead of xev): > > 1. xterm -si -e /bin/xev > 2. move the mouse in the xev window to produce some lines > 3. scroll the xterm up half way and remember the visible lines > 4. while looking at the xterm, again move the mouse in the xev window > > You see: xterm scrolls slowly down. > > I would expect xterm to hold the current view while xev produces more lines > at the end. > > > Suppose you have a "tail -f" running and scroll the xterm up to view a > specific line. > I would expect that line to stay visible until I scroll somewhere else. > But it's not: as the "tail -f" produces output, the xterm scrolls slowly down. > To clarify: xterm does not scroll down to the very end but it scrolls down > line by line, > as if xterm would try to keep the same distance between the current scrolling > position and the most recent line. > > I would expect xterm to keep the same distance between the current scrolling > position and the *FIRST* line. > > > In case above behaviour is the desired behaviour, I wanted to suggest another > command line option like "-si-top" > for my use case. > > Regards, > Paul > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: AW: typo in "man xterm"
On Sat, Jul 28, 2012 at 02:57:35PM +0200, Paul Maier wrote: > > > > Hi, > > > > > > the word "not" should be added to this description: > > > > > > > > > man xterm > > >[...] > > >+maximized > > >This option indicates that xterm should ask the window > > > manager to > > maximize its layout on startup. > > > > > > > > > It should read: > > > ... should *not* ask the window manager ... > > > > The immediate call is made via the X server, but the window manager > > is in control of the subsequent reconfiguration requests, and as > > a result can keep xterm's window from changing size. To simplify > > the manpage, xterm does "ask". > > > > > Hi Thomas, > > so what is the difference between options "+maximized" and "-maximized"? sorry - I misread the question :-) > The behaviour is different: one maximizes, the other not, > but the descriptions in the man page are exactly the same. > > I still think the word "not" should be added to the description of > "+maximized" > to match the behaviour of this option. you're correct (thanks) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
AW: AW: possible to run XWin as windows service?
> > The cygwin program run.exe is designed to do just that. > It's what I use for this purpose :-) ... > Hi Eliot, thank you for your input. 8-) I was using run.exe too. run.exe used to hide the window and the task bar entry. But since my upgrade from Cygwin 1.7.9 to 1.7.15, run.exe only hides the window but not the task bar entry, when invoked from the Startup menu in some cases. This seems buggy, see my thread: http://cygwin.com/ml/cygwin/2012-07/msg00473.html But I don't have the impression that a developer accepted this as bug. Do you have a suggestion how to avoid this situation? Regards, Paul -- 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/
AW: typo in "man xterm"
> > Hi, > > > > the word "not" should be added to this description: > > > > > > man xterm > >[...] > >+maximized > >This option indicates that xterm should ask the window > > manager to > maximize its layout on startup. > > > > > > It should read: > > ... should *not* ask the window manager ... > > The immediate call is made via the X server, but the window manager > is in control of the subsequent reconfiguration requests, and as > a result can keep xterm's window from changing size. To simplify > the manpage, xterm does "ask". > Hi Thomas, so what is the difference between options "+maximized" and "-maximized"? The behaviour is different: one maximizes, the other not, but the descriptions in the man page are exactly the same. I still think the word "not" should be added to the description of "+maximized" to match the behaviour of this option. Regards, Paul -- 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: AW: possible to run XWin as windows service?
On 7/28/2012 8:15 AM, Paul Maier wrote: Can you recommend me how to start the X Server without getting a task bar entry? The cygwin program run.exe is designed to do just that. It's what I use for this purpose :-) ... Eliot Moss -- 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/
"xterm -si" doesn't hold the line
Hi, xterm -si doesn't work as expected. To reproduce (think of a "tail -f" instead of xev): 1. xterm -si -e /bin/xev 2. move the mouse in the xev window to produce some lines 3. scroll the xterm up half way and remember the visible lines 4. while looking at the xterm, again move the mouse in the xev window You see: xterm scrolls slowly down. I would expect xterm to hold the current view while xev produces more lines at the end. Suppose you have a "tail -f" running and scroll the xterm up to view a specific line. I would expect that line to stay visible until I scroll somewhere else. But it's not: as the "tail -f" produces output, the xterm scrolls slowly down. To clarify: xterm does not scroll down to the very end but it scrolls down line by line, as if xterm would try to keep the same distance between the current scrolling position and the most recent line. I would expect xterm to keep the same distance between the current scrolling position and the *FIRST* line. In case above behaviour is the desired behaviour, I wanted to suggest another command line option like "-si-top" for my use case. Regards, Paul -- 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: typo in "man xterm"
On Sat, Jul 28, 2012 at 02:24:52PM +0200, Paul Maier wrote: > Hi, > > the word "not" should be added to this description: > > > man xterm >[...] >+maximized >This option indicates that xterm should ask the window manager > to maximize its layout on startup. > > > It should read: > ... should *not* ask the window manager ... The immediate call is made via the X server, but the window manager is in control of the subsequent reconfiguration requests, and as a result can keep xterm's window from changing size. To simplify the manpage, xterm does "ask". -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
typo in "man xterm"
Hi, the word "not" should be added to this description: man xterm [...] +maximized This option indicates that xterm should ask the window manager to maximize its layout on startup. It should read: ... should *not* ask the window manager ... Regards, Paul -- 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/
AW: possible to run XWin as windows service?
> > I would like to start XWin automatically on Windows startup (Windows user > > login). > > I couldn't find any hint in the manual. > > > > Is it possible to run (and automatically start) XWin as windows service? > > Possible? Yes. > [...] > > Running it from the "Startup" program group is the correct approach. > Hi Jon, running it from the Startup program group worked fine as long as my ~/.startxwinrc has been empty. But I had to add the line /bin/ico -r -obj cube -sleep .05 & to ~/.startxwinrc to fix http://cygwin.com/ml/cygwin-xfree/2012-07/msg00012.html That workaround is perfect, but as a side effect, startxwin won't terminate any more; it blocks as long ico runs, and ico runs forever, so startxwin never terminates. This results in an annoying task bar entry staying there all day. This X Server task bar entry is (obviously) not being attached to any visible window or application, so this entry shouldn't exist in the task bar. Can you recommend me how to start the X Server without getting a task bar entry? Thank you & regards, Paul -- 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/
