I have a brand new installation of openSuSE on a laptop. And when I tried to type something I noticed that keys like " now compose letter by it self. Like for ë or ä. I was use to doing this with the alt key like I have done for years. I just hate it when the computer tries to think for me. Ans the worst part is. When I press " And then a letter or symbel that doesn’t compose with letter it just does nothing at all.
The big question. How can I remove the irratating and bad for normal use auto composer key? BTW I have found the way to set the alt key.
On 07/19/2013 11:46 PM, Drunken wrote:
> I have a brand new installation of openSuSE on a laptop.
your sig tells me you installed openSUSE 11.4 on that new laptop, is
that true? if so, have you taken it to Evergreen yet?
and, i’ve never heard of an “auto composer key” other than in your
posts (and neither has google, see https://www.google.dk/search?q=linux+“Auto+Composor+keys”), so
tell me where that is located and what is printed on it? (are you
talking about the “AltGr” key which is what the right Alt key is
labeled in some non-US keyboards?
i’m a little confused–so, also tell if you are using a desktop
environment, and which version…and, if your laptop keyboard is not
in US English, tell us what it is, as well as what language you told
the installer you were using.
but, the FIRST thing for you to do is make sure the system is using
the correct keyboard layout–a setting selected during the
install…to check, go YaST > Hardware > System Keyboard
Layout…and, when that new window pane opens it will be set to the
keyboard map you told the installer you were using…but, if it
does not match the actual keyboard, then change it to the correct one
and TEST it by typing into the test box, inside that YaST
pane…(and tell us which you was displayed, and which one you
changed it to…and the effect)
and the next thing (if that fixes it) is to go to http://tinyurl.com/4aflkpy and follow the instructions there to bring
your system up to date…because, as born 11.4 is open to attacks
from several vectors that are easily closed–so, do NOT miss this
needed update.
Like dd I can not completely understand what you are telling. He detects that by the somewhat cryptic expression “brand new installation of openSuSE” you probably mean openSUSE 11.4 because that is in your signature.But your sisnature reads “openSuSE 12.3” (whith which you probably mean openSUSE 12.3, yes it is a bit difficult to understand you).
Also as dd explains, you do not tell if, when yes which, desktop environment you use (KDE, Gnome, other). Likewise the bit vague description of the key you mention.
The one thing you do mention though is that you are based in Groningen. Thus it could be that you installed using Netherlands as the language (but you did not tell, thus this is a guess). In a Netherlands installation, there was indeed a change of the default keyboard. (That is of course reprehensible, but that is another story).
Please check in YaST > Hardware > Systeemtoetsenbordindeling if your keyboard is set to Engels (VS). And when not, check it helps when you change it to that.
Again, this advise is based om a lot of assumptions and we not being clairvoyant could be completely wrong.
On 07/20/2013 09:56 AM, hcvv wrote:
>
> “brand new installation of
> openSuSE” you probably mean openSUSE 11.4 because that is in your
> signature.But your sisnature reads “openSuSE 12.3” (whith which you
> probably mean openSUSE 12.3
so, there is another molehill in the http<>nntp lash-up as evidenced
in side-by-side comparison at http://susepaste.org/86303649
>
> The one thing you do mention though is that you are based in Groningen.
which is not mentioned in his post as delivered to me…
When you have any problems with the way you prefer to use the forums (like not getting the information about a poster in the post heading), please mention this (or complain about it) in the approporiate (sub)forum. Please do not litter a technical question/answer thread with it. The OP here will have no idea at all what you are talking about.
On 07/20/2013 10:56 AM, hcvv wrote:
>
> When you have any problems with the way you prefer to use the forums
> (like not getting the information about a poster in the post heading),
> please mention this (or complain about it) in the approporiate
> (sub)forum. Please do not litter a technical question/answer thread with
> it. The OP here will have no idea at all what you are talking about.
it was neither a complaint nor problem…rather a reason (for the the
OP) why your and my post to him were inconsistent…and, especially
why i thought he used 11.4 and you 12.3!
note: if you had PM’ed your problem with my post, the OP would not
have to wade through this administrative litter in his technical
question/answer thread…which the OP certainly will have no idea
what you are talking about, also.
Yes it’s an new 12.3 installation. I installed it on a BTO 15CL58 (Clevo 350STQ). (The signature was outdated. Been using suse from version 7.3)
Yes I do have a Dutch installation. But have set they keyboard to US. The Dutch hardly ever use there own layout. I don’t even think you can get it any more. And there for all the keys are in the right place.
The alt key is the right on so it says “Alt Gr”.
I’m using the KDE version shipped with 12.3. I’m planning on updating to 4.10.
The auto compose keys are the same as in windows. ',",^,~,` And so on. But in windows if you type two keys that don’t compose, like ’ and t it will print 't and not nothing like now is happening.
Daniël
p.s. Yes I’m from Groningen and it says so on the location part of the forum.
On 07/20/2013 04:56 PM, Drunken wrote:
> The auto compose keys are the same as in windows. ',",^,~,` And so on.
> But in windows if you type two keys that don’t compose, like ’ and t it
> will print 't and not nothing like now is happening.
sorry, i can’t help any more because i just don̈́’t know anything about
Windows “auto compose keys” (almost never use windows since '95) and
don’t know if or how to mimic them in Linux…so, lets hope someone
who knows comes along…
sorry. (and for all the administrative talk in your help thread)
oh, i do wonder if you updated your sig in the forums after reading
my input? and, if you did that before reading Henk’s?
Of course he did. That was clear to everybody reading first your answer (where you reported it being 11.4) and my answer (where I found out it now being 12.3).
I tried to communicate to Drunken that, when he changes the rules halfway the game, he should clearly report that and not doing it in secresy, leaving all the first readers (including you) in the dark.
And I can add that this incident again stiffens my idea that such things should not be in the signature. When signatures change, every page loaded anew will show the actual signature. Thus on a problem of 2009, it will e.g. show hardware from 2011 and openSUSE 12.3. And this makes older threads rather useless.
First, refering to the more or less parallel discusion going on here between dd and me, please next time simply tell that you installed openSUSE 12.3 instead of things like “brand new installation of openSuSE”. To begin with you have to type less. Second you tell more. Such an expression forces us to go searching for information in things like signatures and as you know these are not trustworthy.
Then about your prblem description. Like dd I do not know much about Windows (except that Linux is not Windows). Thus you better describe what happens identifying keyboard keys with the character/codes that are engraved on them. The only way to tell us what you do on the keyboard.
You say you have the keyboard set to US. But I asked you to check using YaST if it is on Engels (VS). Now did you check or do you tell what you think it is?
You you did something (not clear what) using Alt for years. It is not clear to me if that was in openSUSE or in Windows.
I changed my signature right after posting. I haven’t read DD’s post yet. Then I would have replied to correct the error.
The auto compose is exactly the same as when you press alt in Linux without pressing alt. And Linux knows more combinations.
I know my keyboard is set to US (Engels (VS)). That’s what YaST and KDE tell me. I did set the keyboard to US on installation and it’s what I have ordered.
To bad you can’t help me any further. It’s just a very annoying function.
And my use of windows is forced… On my home computer I’m running only Linux for 10+ years now. Only on my laptop there is a small installation of windows for the use I’m forced to. (Some programs don’t run in a VM)
I think the whole signature case is clear now. Let us concentrate on your problem.
This I do not undersrtand. What is “pressing alt in Linux without pressing alt”?
OK, thatis clear now.
None of us told you that we can not help you. But we must know what you do, what you expect to happen and what happened instead. We still do not know. How can we help with a solution when we do not understand the problem?
You seem to think that we all experience the same as you have, but I doubt that that is the case. But again we need a good, exact description of what happens.
We are not interested in the fact that you are using Windows some of the time. Some of the time I go for a cycle tour. But that is not interseting for your problem. You should only be aware that we do not much about Windows. Thus saying thinks like “it is like in Windows” does not help, because we do not know whhat “like Windows” is.
Beste Drunken,
Is het niet het beste om dit in het Nederlands te doen? Start dan een nieuwe draad in het Nederlandse gedeelte van deze forums.
On 2013-07-21 13:46, Drunken wrote:
> The auto compose is exactly the same as when you press alt in Linux
> without pressing alt. And Linux knows more combinations.
The correct name is not “auto compose” but “dead keys”. That is how it
is found in documentation all over Internet.
> I know my keyboard is set to US (Engels (VS)). That’s what YaST and KDE
> tell me.
A pure US keyboard definition has no dead keys at all. The ‘"’ is just
‘"’ and it doesn’t wait for a second key press. However, there is the
“US International” keyboard definition (here and in Windows) in which
the ‘"’ key waits for a second key before deciding what to really
display. By the way, typing ‘""’ produces a single ‘"’.
What you describe seems a non pure US keyboard.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On 07/20/2013 09:06 PM, hcvv wrote:
> And I can add that this incident again stiffens my idea that such
> things shouldnot be in the signature.
i jump to agree with you! (and, if you write it in the forum feedback
sub-forum i will agree again):
imo the sig should NOT change once the post is submitted or
system data should be banned in the sig, but required in the
message body…and, if missing then all answers are blocked until
the OP designates needed system info.
but, i guess this might be a molehill>mountain problem.
and, from http://lists.opensuse.org/opensuse/2002-01/msg00332.html i
presume you need to (in KDE) go Configure Desktop > Hardware > Input
Devices > Keyboard > Layouts > click to focus on the layout you are
using [Engels (VS)] then click “Add Layout” button which will open a
new pop-up, then using the spinner on the “Varient” line (third from
top) make sure you have NOT selected “International (with dead keys)”
instead select “International (AltGr dead keys)” then Ok > Apply
[QUOTE=DenverD;2573528
[…]
and, from Re: [SLE] Diacritical marks i
presume you need to (in KDE) go Configure Desktop > Hardware > Input
Devices > Keyboard > Layouts > click to focus on the layout you are
using [Engels (VS)] then click “Add Layout” button which will open a
new pop-up, then using the spinner on the “Varient” line (third from
top) make sure you have NOT selected “International (with dead keys)”
instead select “International (AltGr dead keys)” then Ok > Apply
[/QUOTE]
That was it! Now it works like a charm! Not even the need to change the settings in x to set the alt as composer.