Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #85477 > unrolled thread

Re: Wildly OT: pop-up virtual keyboard for Mac or Linux?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Wildly OT: pop-up virtual keyboard for Mac or Linux? Laura Creighton <lac@openend.se> - 2015-02-10 23:15 +0100
    Re: Wildly OT: pop-up virtual keyboard for Mac or Linux? Grant Edwards <invalid@invalid.invalid> - 2015-02-10 23:15 +0000
    Re: Wildly OT: pop-up virtual keyboard for Mac or Linux? alister <alister.nospam.ware@ntlworld.com> - 2015-02-11 09:33 +0000
      Re: Wildly OT: pop-up virtual keyboard for Mac or Linux? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-02-11 08:50 -0500

#85477 — Re: Wildly OT: pop-up virtual keyboard for Mac or Linux?

In a message of Tue, 10 Feb 2015 15:29:00 -0600, Tim Chase writes:
>While it's not exactly a hold-down-get-a-menu, I opt for changing my
>(otherwise-useless) caps-lock key to an X compose key:
>
>  $ setxkbmap -option compose:caps
>
>I can then hit caps-lock followed by what are generally intuitive
>sequences.  For your first one, that would be "capital-D minus".  I'm
>not sure what the other characters are supposed to be, so I'm not
>sure how to find them.  But é is "compose, e, apostrophe", ñ is
>"compose, n, tilde", the degree sign is "compose, o, o", the € is
>"compose, E, equals", etc. There are loads of these documented in (on
>my machine, where my locale is en_US.UTF-8)
>/usr/share/X11/locale/en_US.UTF-8/Compose
>
>Some of them are a little less intuitive, though the majority of the
>time I can just guess them (I'd never typed "Đ" before, but guessed
>and was right). Otherwise I search that above file.
>
>This also has the advantage that it should work in every X
>application, including Unicode-aware terminal applications (in
>Unicode-aware terminals).  Adding some sort of press-and-hold UI
>would limit it to those applications that chose to support it (or
>even *could* support it).
>
>> While I'm a touch typist, I almost never use auto-repeat, which is
>> the "binding" of held keys in most environments
>
>I agree, as vi/vim makes it easy to insert multiples of the same
>character (or characters) akin to what you describe in Emacs.
>
>-tkc

Wow.  US keyboards do not come with a 'compose' key, then?  It just
never occurred to me that Skip might be missing one.

Oh, goodness gracious then, go with this solution.  Much better than
mine --though the one I pointed at is great should you suddenly need
to type something in cyrillic while at a non-cyrillic keyboard.

Laura

[toc] | [next] | [standalone]

#85478

On 2015-02-10, Laura Creighton <lac@openend.se> wrote:

> Wow.  US keyboards do not come with a 'compose' key, then?

Nope.

> It just never occurred to me that Skip might be missing one.

I always configure one of my "extra" keys (windows-key, menu-key,
right-ctrl, etc.) as compose. But, I use it infrequenty enough that
it's probably rather amusing watching me try to find it via trial and
error.

-- 
Grant Edwards               grant.b.edwards        Yow! I own seven-eighths of
                                  at               all the artists in downtown
                              gmail.com            Burbank!

[toc] | [prev] | [next] | [standalone]

#85515

On Tue, 10 Feb 2015 23:15:11 +0100, Laura Creighton wrote:

> In a message of Tue, 10 Feb 2015 15:29:00 -0600, Tim Chase writes:
>>While it's not exactly a hold-down-get-a-menu, I opt for changing my
>>(otherwise-useless) caps-lock key to an X compose key:
>>
>>  $ setxkbmap -option compose:caps
>>
>>I can then hit caps-lock followed by what are generally intuitive
>>sequences.  For your first one, that would be "capital-D minus".  I'm
>>not sure what the other characters are supposed to be, so I'm not sure
>>how to find them.  But é is "compose, e, apostrophe", ñ is "compose, n,
>>tilde", the degree sign is "compose, o, o", the € is "compose, E,
>>equals", etc. There are loads of these documented in (on my machine,
>>where my locale is en_US.UTF-8)
>>/usr/share/X11/locale/en_US.UTF-8/Compose
>>
>>Some of them are a little less intuitive, though the majority of the
>>time I can just guess them (I'd never typed "Đ" before, but guessed and
>>was right). Otherwise I search that above file.
>>
>>This also has the advantage that it should work in every X application,
>>including Unicode-aware terminal applications (in Unicode-aware
>>terminals).  Adding some sort of press-and-hold UI would limit it to
>>those applications that chose to support it (or even *could* support
>>it).
>>
>>> While I'm a touch typist, I almost never use auto-repeat, which is the
>>> "binding" of held keys in most environments
>>
>>I agree, as vi/vim makes it easy to insert multiples of the same
>>character (or characters) akin to what you describe in Emacs.
>>
>>-tkc
> 
> Wow.  US keyboards do not come with a 'compose' key, then?  It just
> never occurred to me that Skip might be missing one.
> 
> Oh, goodness gracious then, go with this solution.  Much better than
> mine --though the one I pointed at is great should you suddenly need to
> type something in cyrillic while at a non-cyrillic keyboard.
> 
> Laura

English keyboards (US & UK) don't have a compose key because wee do not 
normaly use accented characters (except when dealing with people that do 
& then being lazy we often cheat & don't bother with them. Apologies to 
all who do use them this is very poor behaviour)




-- 
No character, however upright, is a match for constantly reiterated 
attacks,
however false.
		-- Alexander Hamilton

[toc] | [prev] | [next] | [standalone]

#85530

On Wed, 11 Feb 2015 09:33:52 +0000 (UTC), alister
<alister.nospam.ware@ntlworld.com> declaimed the following:

>English keyboards (US & UK) don't have a compose key because wee do not 
>normaly use accented characters (except when dealing with people that do 
>& then being lazy we often cheat & don't bother with them. Apologies to 
>all who do use them this is very poor behaviour)
>
	Or have to drag out Windows character map utility to find a special
code to enter the character (and hope one has picked an encoding that is
compatible with the target <G>).

	Even though I seldom used it, I miss my Amiga -- when had a rather
clean "dead key" implementation... I forget the icons on the keys but it
would have been the equivalent of:

<alt-j><vowel> would add a ' accent, <alt-k><vowel> would add ` accent,
etc. There were five or six <alt-> keys, and <vowel> may not have been just
a vowel... the combo that would put an ~ over lowercase n, for example.
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web