headers
Duane Krings | 1 Jan 2010 08:55
Picon

Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

For of those of us who prefer the X window managers, I would like to request an option to this new command that
starts 
the server _not_ in multiwindow mode as there is no -singlewindow or -nomultiwindow options we can send to
the server as 
overrides.

--
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/
Permalink | Reply | 1 comment |
headers
Yaakov (Cygwin/X | 1 Jan 2010 09:33
Picon
Gravatar

Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

On 01/01/2010 01:55, Duane Krings wrote:
> For of those of us who prefer the X window managers, I would like to
> request an option to this new command that starts the server _not_ in
> multiwindow mode as there is no -singlewindow or -nomultiwindow options
> we can send to the server as overrides.

startx

Yaakov
Cygwin/X

--
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/
Permalink | Reply | 0 comments |
headers
Frédéric Bron | 1 Jan 2010 11:30

Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

> IMPORTANT: THE startxwin.bat AND startxwin.sh SCRIPTS ARE NO LONGER
> SUPPORTED.

I used to add the following option to XWin command because my screen
resolution is now always recognized automatically: -screen 0 1920x1200

How can I do the same using .startxwinrc?

Frédéric

--
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/
Permalink | Reply | 2 comments |
headers
Jim Reisert AD1C | 1 Jan 2010 16:53
Picon
Favicon

Re: Can't start xterm from Cygwin/X icon in system tray

On 12/31/2009 1:43 PM, Yaakov (Cygwin/X) wrote:

> This sounds like it has nothing to do with startxwin. I can't reproduce
> this, but do any of the following help:
>
> 1) creating a ~/.startxwinrc containing just "xterm &"?

Same problem.  No xterm.

> 2) changing that .startxwinrc to "run xterm"?

Pop-up:  "Couldn't find xterm anywhere.  I even looked in the PATH"

Same when I tried "run /usr/bin/xterm" (couldn't find /usr/bin/xterm 
anywhere etc.)

> 3) setting LANG=en_US.ISO-8859-1 ?

No change.

> 4) installing the font-daewoo-misc, font-isas-misc, and font-jis-misc
> packages?

Those fonts are already installed.

As I said, I have a desktop icon for starting an XTERM that works.  It 
only "doesn't work" when trying to start the xterm from ~/.startxwinrc, 
or from the system tray.

- Jim
(Continue reading)

Permalink | Reply | 4 comments |
headers
Yaakov (Cygwin/X | 1 Jan 2010 16:57
Picon
Gravatar

Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

On 01/01/2010 04:30, Frédéric Bron wrote:
> I used to add the following option to XWin command because my screen
> resolution is now always recognized automatically: -screen 0 1920x1200
>
> How can I do the same using .startxwinrc?

 From the announcment:

"startxwin also accepts command line arguments to use a different 
DISPLAY number and add additional options to pass to the server.  Please 
read the startxwin(1) manpage, which describes both the command-line 
arguments accepted by startxwin and the format of the $HOME/.startxwinrc 
file."

Yaakov
Cygwin/X

--
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/
Permalink | Reply | 1 comment |
headers
Frédéric Bron | 1 Jan 2010 17:25

Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2

>> I used to add the following option to XWin command because my screen
>> resolution is now always recognized automatically: -screen 0 1920x1200
>>
>> How can I do the same using .startxwinrc?
>
> From the announcment:
>
> "startxwin also accepts command line arguments to use a different DISPLAY
> number and add additional options to pass to the server.  Please read the
> startxwin(1) manpage, which describes both the command-line arguments
> accepted by startxwin and the format of the $HOME/.startxwinrc file."

I have read that but it was not clear to me. I suspect that I should
write "--" before the "-screen" option? Is that true?

Frédéric

--
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/
Permalink | Reply | 0 comments |
headers
Andy Koppe | 1 Jan 2010 17:55
Picon

Re: Alt key not recognized as Meta in xterm

2009/12/30 Gary Carvell:

X issues including xterm ones should go to the cygwin-xfree list. I'm
sending this to both lists, but please respond on cygwin-xfree only.

> With the upgrade to Cygwin 1.7, I found that the Alt key is no longer
> recognized as a Meta key in xterm. This means the Alt based command
> line editing keys such as Alt-F/B for forward- and backward-word must
> be entered with the Esc key instead. I assume this is related to the
> internationalization changes in 1.7.
>
> I liked the old behavior better, but had some trouble changing it
> back. So here's my little hack for this in case anyone else finds it
> useful. In your home directory, create a file .Xdefaults containing
> this line:
>
>    XTerm*vt100.metaSendsEscape: true

Actually that's not a hack, but the correct solution. I think this
needs to be part of the default config in /etc/X11/app-defaults/XTerm.

When that option is not enabled, 'meta' is sent by setting the highest
bit of the metafied character, e.g. 'f' (0x66) turns into 0xE6. That's
fine if you're using ASCII only, but obviously it'll conflict with any
character encodings beyond ASCII, e.g.in ISO-8859-1 and others, 0xE6
is æ (the ae ligature).

And in UTF-8, which of course is the Cygwin default now, a 0xE6 byte
would be an incomplete sequence. That's why xterm applies the meta bit
before doing the UTF-8 encoding, so Alt-f is sent as \xC3\xA6, which
(Continue reading)

Permalink | Reply | 6 comments |
headers
Andy Koppe | 1 Jan 2010 18:15
Picon

Re: Alt key not recognized as Meta in xterm

2010/1/1 Thomas Dickey:
> On Fri, 1 Jan 2010, Andy Koppe wrote:
>
>>>    XTerm*vt100.metaSendsEscape: true
>>
>> Actually that's not a hack, but the correct solution. I think this
>> needs to be part of the default config in /etc/X11/app-defaults/XTerm.
>
> However, the reason that it's not is because there's no standard for
> the meta key assignment.

Understood. I didn't mean it should be the default for Xterm in
general, but it should be for Cygwin's version, due to UTF-8 being the
default charset.

Andy

--
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/
Permalink | Reply | 3 comments |
headers
Thomas Dickey | 1 Jan 2010 18:17
Picon

Re: Alt key not recognized as Meta in xterm

On Fri, 1 Jan 2010, Andy Koppe wrote:

> 2010/1/1 Thomas Dickey:
>> On Fri, 1 Jan 2010, Andy Koppe wrote:
>>
>>>>    XTerm*vt100.metaSendsEscape: true
>>>
>>> Actually that's not a hack, but the correct solution. I think this
>>> needs to be part of the default config in /etc/X11/app-defaults/XTerm.
>>
>> However, the reason that it's not is because there's no standard for
>> the meta key assignment.
>
> Understood. I didn't mean it should be the default for Xterm in
> general, but it should be for Cygwin's version, due to UTF-8 being the
> default charset.

Is Cygwin also specifying a meta key?

(some people equate meta==alt, though they're not necessarily the same)

--

-- 
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/
(Continue reading)

Permalink | Reply | 2 comments |
headers
Andy Koppe | 1 Jan 2010 19:49
Picon

Re: Alt key not recognized as Meta in xterm

2010/1/1 Thomas Dickey:
> Is Cygwin also specifying a meta key?
>
> (some people equate meta==alt, though they're not necessarily the same)

I don't know whether there's ever been an official policy decision on
that, but I think the general assumption among Cygwin users is that
Alt==Meta, since of course PC keyboards don't have a Meta key yet lots
of programs expect one.

I realise that in X it is possible to map a different key to Meta, but
the altIsNotMeta setting is off by default in Cygwin's xterm. Also,
the Cygwin console, rxvt, and mintty (via PuTTY) assume that Alt is
Meta (and they all encode it as Escape by default).

Andy

--
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/
Permalink | Reply | 1 comment |

Gmane