Ctrl-Enter, Shift-Enter and Enter are interpreted as the same keyconsole vim in screen session: remap...

What to say to a student who has failed?

Why doesn't the Falcon-9 first stage use three legs to land?

Fancy String Replace

Can you feel passing through the sound barrier in an F-16?

Can you help me understand Modes from the aspect of chord changes?

Why does The Ancient One think differently about Doctor Strange in Endgame than the film Doctor Strange?

Why can't an Airbus A330 dump fuel in an emergency?

What is the appropriate benchmark for a Long/Short VIX futures strategy?

How to persuade recruiters to send me the Job Description?

Why were movies shot on film shot at 24 frames per second?

Is it possible to create a golf ball sized star?

In the MCU, why does Mjölnir retain its enchantments after Ragnarok?

When translating the law, who ensures that the wording does not change the meaning of the law?

If all stars rotate, why was there a theory developed, that requires non-rotating stars?

Why did this happen to Thanos's ships at the end of "Avengers: Endgame"?

Is there any practical application for performing a double Fourier transform? ...or an inverse Fourier transform on a time-domain input?

Why didn’t Doctor Strange stay in the original winning timeline?

What is wrong about this application of Kirchhoffs Current Law?

Is it safe to remove the bottom chords of a series of garage roof trusses?

How to compare two different formulations of a problem?

Concatenation of the result of a function with a mutable default argument in python

What’s the difference between something that approaches infinity and something that is infinite.

What professions would a medieval village with a population of 100 need?

Is there a limit on how long the casting (speaking aloud part of the spell) of Wish can be?



Ctrl-Enter, Shift-Enter and Enter are interpreted as the same key


console vim in screen session: remap Ctrl-Shift-Left, Ctrl-Shift-Right to not delete linesMint 17 (Cinnamon): CTRL+Shift+U not letting me enter unicode symbolsCan't enter capital letters using shift keyUnable to simulate Ctrl+Shift+Fn+F10 Key press ctrl+shift+e causes beepingStack tilde and bar over letter






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I'm using Fedora 30 with KDE and am trying to bind (Zsh) autosuggest-execute to Ctrl+Enter for convenience. I'm trying to get it to work in gnome-terminal.



However I discovered that showkey -a always returns ^M in these three cases: Enter, Ctrl+Enter, and Shift+Enter.



I tried this method (Ctrl <Return> : "33M" in .XCompose), but it didn't work at all as the XCompose file wasn't being read. So I decided to install ibus as it is not shipped with my KDE install with dnf groupinstall input-methods.



Running ìbus-setup gets me this warning now:



GTK+ supports to output one char only: "33M": ! Ctrl <Return> : "33M"


Unfortunately all enter combinations still boil down to ^M in gnome-terminal as well as xterm.



Is there a way to differentiate between those key combinations with or without ibus?










share|improve this question



























  • FWIW, the "string" in .XCompose can only be a single (possibly multi-byte) character. I don't see how that "33M" could've ever worked.

    – mosvy
    yesterday


















0















I'm using Fedora 30 with KDE and am trying to bind (Zsh) autosuggest-execute to Ctrl+Enter for convenience. I'm trying to get it to work in gnome-terminal.



However I discovered that showkey -a always returns ^M in these three cases: Enter, Ctrl+Enter, and Shift+Enter.



I tried this method (Ctrl <Return> : "33M" in .XCompose), but it didn't work at all as the XCompose file wasn't being read. So I decided to install ibus as it is not shipped with my KDE install with dnf groupinstall input-methods.



Running ìbus-setup gets me this warning now:



GTK+ supports to output one char only: "33M": ! Ctrl <Return> : "33M"


Unfortunately all enter combinations still boil down to ^M in gnome-terminal as well as xterm.



Is there a way to differentiate between those key combinations with or without ibus?










share|improve this question



























  • FWIW, the "string" in .XCompose can only be a single (possibly multi-byte) character. I don't see how that "33M" could've ever worked.

    – mosvy
    yesterday














0












0








0








I'm using Fedora 30 with KDE and am trying to bind (Zsh) autosuggest-execute to Ctrl+Enter for convenience. I'm trying to get it to work in gnome-terminal.



However I discovered that showkey -a always returns ^M in these three cases: Enter, Ctrl+Enter, and Shift+Enter.



I tried this method (Ctrl <Return> : "33M" in .XCompose), but it didn't work at all as the XCompose file wasn't being read. So I decided to install ibus as it is not shipped with my KDE install with dnf groupinstall input-methods.



Running ìbus-setup gets me this warning now:



GTK+ supports to output one char only: "33M": ! Ctrl <Return> : "33M"


Unfortunately all enter combinations still boil down to ^M in gnome-terminal as well as xterm.



Is there a way to differentiate between those key combinations with or without ibus?










share|improve this question
















I'm using Fedora 30 with KDE and am trying to bind (Zsh) autosuggest-execute to Ctrl+Enter for convenience. I'm trying to get it to work in gnome-terminal.



However I discovered that showkey -a always returns ^M in these three cases: Enter, Ctrl+Enter, and Shift+Enter.



I tried this method (Ctrl <Return> : "33M" in .XCompose), but it didn't work at all as the XCompose file wasn't being read. So I decided to install ibus as it is not shipped with my KDE install with dnf groupinstall input-methods.



Running ìbus-setup gets me this warning now:



GTK+ supports to output one char only: "33M": ! Ctrl <Return> : "33M"


Unfortunately all enter combinations still boil down to ^M in gnome-terminal as well as xterm.



Is there a way to differentiate between those key combinations with or without ibus?







keyboard-shortcuts input-method ibus






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday









fra-san

2,6851 gold badge8 silver badges25 bronze badges




2,6851 gold badge8 silver badges25 bronze badges










asked 2 days ago









rudibrudib

6785 silver badges17 bronze badges




6785 silver badges17 bronze badges
















  • FWIW, the "string" in .XCompose can only be a single (possibly multi-byte) character. I don't see how that "33M" could've ever worked.

    – mosvy
    yesterday



















  • FWIW, the "string" in .XCompose can only be a single (possibly multi-byte) character. I don't see how that "33M" could've ever worked.

    – mosvy
    yesterday

















FWIW, the "string" in .XCompose can only be a single (possibly multi-byte) character. I don't see how that "33M" could've ever worked.

– mosvy
yesterday





FWIW, the "string" in .XCompose can only be a single (possibly multi-byte) character. I don't see how that "33M" could've ever worked.

– mosvy
yesterday










2 Answers
2






active

oldest

votes


















1













No need to install ibus, etc. All X11 apps have access to the exact keycodes and to their xkb / xim translations, and may ignore the latter.



The problem is in the terminal emulator, and with the fact that there's no standard way to represent key combos like Ctrl-Enter in the terminal. Also, each terminal emulator has (or hasn't) its own way of configuring key-bindings.



In xterm, like in any xt-based app you can easily configure it with X11 resources. For instance, this will translate Ctrl-Enter to the escape corresponding to the F33 function key (according to infocmp):



xterm -xrm '*VT100*translations: #override Ctrl<Key>Return:string("33[20;5~")'


Then you could bind that e[20;5~ to whatever action you want in readline's ~/.inputrc, with bind in bash, with bindkey in zsh, etc.



X11 resources are stored as the RESOURCE_MANAGER property of the root window and can be loaded there with the xrdb utility; usually, xrdb will be called from an x11 session initialization script to load the content of the ~/.Xresources file.



KDE or Gnome applications like konsole and gnome-terminal have their own way of configuring key combos to actions; I don't know if that includes the ability to write arbitrary strings to the pseudo-tty master.






share|improve this answer




























  • Thanks for the info, I was able to get it half-working in konsole. Ctrl-Enter now translates to e[20;5~, but bindkey doesn't work for some reason. I'm using bindkey 'e[20;5~' forward-word. As of now, it just outputs e[20;5~ when pressing the combination. I was hoping to get it working in gnome-terminal as well, but Konsole may be a viable alternative.

    – rudib
    yesterday






  • 1





    bindkey 'e[20;5~' forward-word works for me. Maybe konsole is sending literally + e instead of Esc (ascii 0x1f)? Also, if you're using vi keys in zsh, you'll have to use bindkey -a ... to do the binding in "command mode".

    – mosvy
    19 hours ago













  • Yes, that was the problem, thanks! konsole needs a capital e in order for it to be escape: E[20;5~.

    – rudib
    16 hours ago






  • 1





    ESC is ascii 0x1b, not 0x1f, sorry ;-)

    – mosvy
    15 hours ago



















1













This is how to set it up in konsole:



Also see the Kde Reference for Key Bindings in Konsole.



Settings -> Edit Current Profile -> Keyboard -> (select used keyboard layout) -> Edit -> Search/Filter for Return.



Edit the following entries (left column only):




  • Change Return-Shift-NewLine to Return-Shift-Ctrl-NewLine

  • Change Return-Shift+NewLine to Return-Shift-Ctrl+NewLine


This allows to differentiate between Enter and Ctrl + Enter.



Add the following entry:



Return+Ctrl -> E[20;5~



Now just add bindkey 'e[20;5~' autosuggest-execute or any other sink in ~/.zshrc.






share|improve this answer




























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f536352%2fctrl-enter-shift-enter-and-enter-are-interpreted-as-the-same-key%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1













    No need to install ibus, etc. All X11 apps have access to the exact keycodes and to their xkb / xim translations, and may ignore the latter.



    The problem is in the terminal emulator, and with the fact that there's no standard way to represent key combos like Ctrl-Enter in the terminal. Also, each terminal emulator has (or hasn't) its own way of configuring key-bindings.



    In xterm, like in any xt-based app you can easily configure it with X11 resources. For instance, this will translate Ctrl-Enter to the escape corresponding to the F33 function key (according to infocmp):



    xterm -xrm '*VT100*translations: #override Ctrl<Key>Return:string("33[20;5~")'


    Then you could bind that e[20;5~ to whatever action you want in readline's ~/.inputrc, with bind in bash, with bindkey in zsh, etc.



    X11 resources are stored as the RESOURCE_MANAGER property of the root window and can be loaded there with the xrdb utility; usually, xrdb will be called from an x11 session initialization script to load the content of the ~/.Xresources file.



    KDE or Gnome applications like konsole and gnome-terminal have their own way of configuring key combos to actions; I don't know if that includes the ability to write arbitrary strings to the pseudo-tty master.






    share|improve this answer




























    • Thanks for the info, I was able to get it half-working in konsole. Ctrl-Enter now translates to e[20;5~, but bindkey doesn't work for some reason. I'm using bindkey 'e[20;5~' forward-word. As of now, it just outputs e[20;5~ when pressing the combination. I was hoping to get it working in gnome-terminal as well, but Konsole may be a viable alternative.

      – rudib
      yesterday






    • 1





      bindkey 'e[20;5~' forward-word works for me. Maybe konsole is sending literally + e instead of Esc (ascii 0x1f)? Also, if you're using vi keys in zsh, you'll have to use bindkey -a ... to do the binding in "command mode".

      – mosvy
      19 hours ago













    • Yes, that was the problem, thanks! konsole needs a capital e in order for it to be escape: E[20;5~.

      – rudib
      16 hours ago






    • 1





      ESC is ascii 0x1b, not 0x1f, sorry ;-)

      – mosvy
      15 hours ago
















    1













    No need to install ibus, etc. All X11 apps have access to the exact keycodes and to their xkb / xim translations, and may ignore the latter.



    The problem is in the terminal emulator, and with the fact that there's no standard way to represent key combos like Ctrl-Enter in the terminal. Also, each terminal emulator has (or hasn't) its own way of configuring key-bindings.



    In xterm, like in any xt-based app you can easily configure it with X11 resources. For instance, this will translate Ctrl-Enter to the escape corresponding to the F33 function key (according to infocmp):



    xterm -xrm '*VT100*translations: #override Ctrl<Key>Return:string("33[20;5~")'


    Then you could bind that e[20;5~ to whatever action you want in readline's ~/.inputrc, with bind in bash, with bindkey in zsh, etc.



    X11 resources are stored as the RESOURCE_MANAGER property of the root window and can be loaded there with the xrdb utility; usually, xrdb will be called from an x11 session initialization script to load the content of the ~/.Xresources file.



    KDE or Gnome applications like konsole and gnome-terminal have their own way of configuring key combos to actions; I don't know if that includes the ability to write arbitrary strings to the pseudo-tty master.






    share|improve this answer




























    • Thanks for the info, I was able to get it half-working in konsole. Ctrl-Enter now translates to e[20;5~, but bindkey doesn't work for some reason. I'm using bindkey 'e[20;5~' forward-word. As of now, it just outputs e[20;5~ when pressing the combination. I was hoping to get it working in gnome-terminal as well, but Konsole may be a viable alternative.

      – rudib
      yesterday






    • 1





      bindkey 'e[20;5~' forward-word works for me. Maybe konsole is sending literally + e instead of Esc (ascii 0x1f)? Also, if you're using vi keys in zsh, you'll have to use bindkey -a ... to do the binding in "command mode".

      – mosvy
      19 hours ago













    • Yes, that was the problem, thanks! konsole needs a capital e in order for it to be escape: E[20;5~.

      – rudib
      16 hours ago






    • 1





      ESC is ascii 0x1b, not 0x1f, sorry ;-)

      – mosvy
      15 hours ago














    1












    1








    1







    No need to install ibus, etc. All X11 apps have access to the exact keycodes and to their xkb / xim translations, and may ignore the latter.



    The problem is in the terminal emulator, and with the fact that there's no standard way to represent key combos like Ctrl-Enter in the terminal. Also, each terminal emulator has (or hasn't) its own way of configuring key-bindings.



    In xterm, like in any xt-based app you can easily configure it with X11 resources. For instance, this will translate Ctrl-Enter to the escape corresponding to the F33 function key (according to infocmp):



    xterm -xrm '*VT100*translations: #override Ctrl<Key>Return:string("33[20;5~")'


    Then you could bind that e[20;5~ to whatever action you want in readline's ~/.inputrc, with bind in bash, with bindkey in zsh, etc.



    X11 resources are stored as the RESOURCE_MANAGER property of the root window and can be loaded there with the xrdb utility; usually, xrdb will be called from an x11 session initialization script to load the content of the ~/.Xresources file.



    KDE or Gnome applications like konsole and gnome-terminal have their own way of configuring key combos to actions; I don't know if that includes the ability to write arbitrary strings to the pseudo-tty master.






    share|improve this answer















    No need to install ibus, etc. All X11 apps have access to the exact keycodes and to their xkb / xim translations, and may ignore the latter.



    The problem is in the terminal emulator, and with the fact that there's no standard way to represent key combos like Ctrl-Enter in the terminal. Also, each terminal emulator has (or hasn't) its own way of configuring key-bindings.



    In xterm, like in any xt-based app you can easily configure it with X11 resources. For instance, this will translate Ctrl-Enter to the escape corresponding to the F33 function key (according to infocmp):



    xterm -xrm '*VT100*translations: #override Ctrl<Key>Return:string("33[20;5~")'


    Then you could bind that e[20;5~ to whatever action you want in readline's ~/.inputrc, with bind in bash, with bindkey in zsh, etc.



    X11 resources are stored as the RESOURCE_MANAGER property of the root window and can be loaded there with the xrdb utility; usually, xrdb will be called from an x11 session initialization script to load the content of the ~/.Xresources file.



    KDE or Gnome applications like konsole and gnome-terminal have their own way of configuring key combos to actions; I don't know if that includes the ability to write arbitrary strings to the pseudo-tty master.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited yesterday

























    answered yesterday









    mosvymosvy

    15.9k2 gold badges19 silver badges51 bronze badges




    15.9k2 gold badges19 silver badges51 bronze badges
















    • Thanks for the info, I was able to get it half-working in konsole. Ctrl-Enter now translates to e[20;5~, but bindkey doesn't work for some reason. I'm using bindkey 'e[20;5~' forward-word. As of now, it just outputs e[20;5~ when pressing the combination. I was hoping to get it working in gnome-terminal as well, but Konsole may be a viable alternative.

      – rudib
      yesterday






    • 1





      bindkey 'e[20;5~' forward-word works for me. Maybe konsole is sending literally + e instead of Esc (ascii 0x1f)? Also, if you're using vi keys in zsh, you'll have to use bindkey -a ... to do the binding in "command mode".

      – mosvy
      19 hours ago













    • Yes, that was the problem, thanks! konsole needs a capital e in order for it to be escape: E[20;5~.

      – rudib
      16 hours ago






    • 1





      ESC is ascii 0x1b, not 0x1f, sorry ;-)

      – mosvy
      15 hours ago



















    • Thanks for the info, I was able to get it half-working in konsole. Ctrl-Enter now translates to e[20;5~, but bindkey doesn't work for some reason. I'm using bindkey 'e[20;5~' forward-word. As of now, it just outputs e[20;5~ when pressing the combination. I was hoping to get it working in gnome-terminal as well, but Konsole may be a viable alternative.

      – rudib
      yesterday






    • 1





      bindkey 'e[20;5~' forward-word works for me. Maybe konsole is sending literally + e instead of Esc (ascii 0x1f)? Also, if you're using vi keys in zsh, you'll have to use bindkey -a ... to do the binding in "command mode".

      – mosvy
      19 hours ago













    • Yes, that was the problem, thanks! konsole needs a capital e in order for it to be escape: E[20;5~.

      – rudib
      16 hours ago






    • 1





      ESC is ascii 0x1b, not 0x1f, sorry ;-)

      – mosvy
      15 hours ago

















    Thanks for the info, I was able to get it half-working in konsole. Ctrl-Enter now translates to e[20;5~, but bindkey doesn't work for some reason. I'm using bindkey 'e[20;5~' forward-word. As of now, it just outputs e[20;5~ when pressing the combination. I was hoping to get it working in gnome-terminal as well, but Konsole may be a viable alternative.

    – rudib
    yesterday





    Thanks for the info, I was able to get it half-working in konsole. Ctrl-Enter now translates to e[20;5~, but bindkey doesn't work for some reason. I'm using bindkey 'e[20;5~' forward-word. As of now, it just outputs e[20;5~ when pressing the combination. I was hoping to get it working in gnome-terminal as well, but Konsole may be a viable alternative.

    – rudib
    yesterday




    1




    1





    bindkey 'e[20;5~' forward-word works for me. Maybe konsole is sending literally + e instead of Esc (ascii 0x1f)? Also, if you're using vi keys in zsh, you'll have to use bindkey -a ... to do the binding in "command mode".

    – mosvy
    19 hours ago







    bindkey 'e[20;5~' forward-word works for me. Maybe konsole is sending literally + e instead of Esc (ascii 0x1f)? Also, if you're using vi keys in zsh, you'll have to use bindkey -a ... to do the binding in "command mode".

    – mosvy
    19 hours ago















    Yes, that was the problem, thanks! konsole needs a capital e in order for it to be escape: E[20;5~.

    – rudib
    16 hours ago





    Yes, that was the problem, thanks! konsole needs a capital e in order for it to be escape: E[20;5~.

    – rudib
    16 hours ago




    1




    1





    ESC is ascii 0x1b, not 0x1f, sorry ;-)

    – mosvy
    15 hours ago





    ESC is ascii 0x1b, not 0x1f, sorry ;-)

    – mosvy
    15 hours ago













    1













    This is how to set it up in konsole:



    Also see the Kde Reference for Key Bindings in Konsole.



    Settings -> Edit Current Profile -> Keyboard -> (select used keyboard layout) -> Edit -> Search/Filter for Return.



    Edit the following entries (left column only):




    • Change Return-Shift-NewLine to Return-Shift-Ctrl-NewLine

    • Change Return-Shift+NewLine to Return-Shift-Ctrl+NewLine


    This allows to differentiate between Enter and Ctrl + Enter.



    Add the following entry:



    Return+Ctrl -> E[20;5~



    Now just add bindkey 'e[20;5~' autosuggest-execute or any other sink in ~/.zshrc.






    share|improve this answer






























      1













      This is how to set it up in konsole:



      Also see the Kde Reference for Key Bindings in Konsole.



      Settings -> Edit Current Profile -> Keyboard -> (select used keyboard layout) -> Edit -> Search/Filter for Return.



      Edit the following entries (left column only):




      • Change Return-Shift-NewLine to Return-Shift-Ctrl-NewLine

      • Change Return-Shift+NewLine to Return-Shift-Ctrl+NewLine


      This allows to differentiate between Enter and Ctrl + Enter.



      Add the following entry:



      Return+Ctrl -> E[20;5~



      Now just add bindkey 'e[20;5~' autosuggest-execute or any other sink in ~/.zshrc.






      share|improve this answer




























        1












        1








        1







        This is how to set it up in konsole:



        Also see the Kde Reference for Key Bindings in Konsole.



        Settings -> Edit Current Profile -> Keyboard -> (select used keyboard layout) -> Edit -> Search/Filter for Return.



        Edit the following entries (left column only):




        • Change Return-Shift-NewLine to Return-Shift-Ctrl-NewLine

        • Change Return-Shift+NewLine to Return-Shift-Ctrl+NewLine


        This allows to differentiate between Enter and Ctrl + Enter.



        Add the following entry:



        Return+Ctrl -> E[20;5~



        Now just add bindkey 'e[20;5~' autosuggest-execute or any other sink in ~/.zshrc.






        share|improve this answer













        This is how to set it up in konsole:



        Also see the Kde Reference for Key Bindings in Konsole.



        Settings -> Edit Current Profile -> Keyboard -> (select used keyboard layout) -> Edit -> Search/Filter for Return.



        Edit the following entries (left column only):




        • Change Return-Shift-NewLine to Return-Shift-Ctrl-NewLine

        • Change Return-Shift+NewLine to Return-Shift-Ctrl+NewLine


        This allows to differentiate between Enter and Ctrl + Enter.



        Add the following entry:



        Return+Ctrl -> E[20;5~



        Now just add bindkey 'e[20;5~' autosuggest-execute or any other sink in ~/.zshrc.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 16 hours ago









        rudibrudib

        6785 silver badges17 bronze badges




        6785 silver badges17 bronze badges

































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f536352%2fctrl-enter-shift-enter-and-enter-are-interpreted-as-the-same-key%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Ciclooctatetraenă Vezi și | Bibliografie | Meniu de navigare637866text4148569-500570979m