starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1698] When I type in console and something else is printed to the console what ever I typed gets removed. But when I press enter the command is ran #1325

New issue

Closed

opened 2026-02-27 02:56:30 +03:00 by kerem · 9 comments

kerem commented

2026-02-27 02:56:30 +03:00

Owner

Originally created by @Synkstar on GitHub (Nov 19, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1698

Plz fix

Originally created by @Synkstar on GitHub (Nov 19, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1698 Plz fix

kerem closed this issue

2026-02-27 02:56:30 +03:00

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@Scarsz commented on GitHub (Nov 19, 2017):

An exemplary example of how not to use GitHub Issues. This is a problem with the server software, not LGSM.

@Scarsz commented on GitHub (Nov 19, 2017): An exemplary example of how not to use GitHub Issues. This is a problem with the server software, not LGSM.

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@MarkTwoFive commented on GitHub (Nov 20, 2017):

Actually that is up to the terminal you're using and has to do with how the Std. IO-Streams work.

Whatever you type is sent to the stdIN stream either instantaneously or as soon as you hit enter (depending on your terminal/shell) and whatever the program wants to send to its console is sent to the stdOUT stream.

Those two streams do not interact with each other. So actions on one do not affect the other.

Now what you're experiencing is a behavior of you terminal/shell which displays both your input and the process output in the same log:

You type a few characters
Application sends a line (followed by a newline character) -> This is only visually appended to what you've written (Remember that the stdIN is not affected by this)
You type the rest and hit enter -> The application receives what you typed via stdIN and does not know that you've seen something different

tl;dr: You don't need to worry about this as it is just a visual effect.

@MarkTwoFive commented on GitHub (Nov 20, 2017): Actually that is up to the terminal you're using and has to do with how the Std. IO-Streams work. Whatever you type is sent to the stdIN stream either instantaneously or as soon as you hit enter (depending on your terminal/shell) and whatever the program wants to send to its console is sent to the stdOUT stream. Those two streams ___do not interact___ with each other. So actions on one do not affect the other. Now what you're experiencing is a behavior of you terminal/shell which displays both your input and the process output in the same log: 1. You type a few characters 2. Application sends a line (followed by a ``newline`` character) -> This is ___only visually___ appended to what you've written (Remember that the stdIN is not affected by this) 3. You type the rest and hit enter -> The application receives what you typed via stdIN and does ___not know___ that you've seen something different tl;dr: You don't need to worry about this as it is just a visual effect.

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@Synkstar commented on GitHub (Nov 20, 2017):

I am just wondering if it is possible to fix this because I cant review what I am typing.

@Synkstar commented on GitHub (Nov 20, 2017): I am just wondering if it is possible to fix this because I cant review what I am typing.

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@Scarsz commented on GitHub (Nov 20, 2017):

No. Sorry but you have to live with it. Certain server softwares (such as Minecraft, I believe) don't have the problem while some do. Nothing we as developers of LGSM can do. I'm as annoyed by it as you are.

@Scarsz commented on GitHub (Nov 20, 2017): No. Sorry but you have to live with it. Certain server softwares (such as Minecraft, I believe) don't have the problem while some do. Nothing we as developers of LGSM can do. I'm as annoyed by it as you are.

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@Synkstar commented on GitHub (Nov 20, 2017):

On Mon, Nov 20, 2017 at 3:59 PM, Austin Shapiro notifications@github.com
wrote:

No. Sorry but you have to live with it. Certain server softwares (such as
Minecraft, I believe) don't have the problem while some do. Nothing we as
developers of LGSM can do.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GameServerManagers/LinuxGSM/issues/1698#issuecomment-345829948,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY9notHmvA4ND7MOMr4FSKuWp_ut6v-eks5s4egigaJpZM4QjM5l
.

@Synkstar commented on GitHub (Nov 20, 2017): Ok On Mon, Nov 20, 2017 at 3:59 PM, Austin Shapiro <notifications@github.com> wrote: > No. Sorry but you have to live with it. Certain server softwares (such as > Minecraft, I believe) don't have the problem while some do. Nothing we as > developers of LGSM can do. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/GameServerManagers/LinuxGSM/issues/1698#issuecomment-345829948>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AY9notHmvA4ND7MOMr4FSKuWp_ut6v-eks5s4egigaJpZM4QjM5l> > . >

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@MarkTwoFive commented on GitHub (Nov 20, 2017):

Actually there is: Use a terminal/shell that does not write stdIN and stdOUT on the same lines.

Or wrap another one that is capable of that around lgsm.

Or just find a way not to need the server console ^^

@MarkTwoFive commented on GitHub (Nov 20, 2017): Actually there is: Use a terminal/shell that does not write stdIN and stdOUT on the same lines. Or wrap another one that is capable of that around lgsm. Or just find a way not to need the server console ^^

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@Synkstar commented on GitHub (Nov 20, 2017):

Like what ? I am using ssh to connect to my server.

On Mon, Nov 20, 2017 at 5:15 PM, Magnus Leßmann (aka. mark332) <
notifications@github.com> wrote:

Actually there is: Use a terminal/shell that does not write stdIN and
stdOUT on the same lines.

Or wrap another one that is capable of that around lgsm.

Or just find a way not to need the server console ^^

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GameServerManagers/LinuxGSM/issues/1698#issuecomment-345848828,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY9nomTWmVPev_pRMRXXN8owvL2yvH9mks5s4fnwgaJpZM4QjM5l
.

@Synkstar commented on GitHub (Nov 20, 2017): Like what ? I am using ssh to connect to my server. On Mon, Nov 20, 2017 at 5:15 PM, Magnus Leßmann (aka. mark332) < notifications@github.com> wrote: > Actually there is: Use a terminal/shell that does not write stdIN and > stdOUT on the same lines. > > Or wrap another one that is capable of that around lgsm. > > Or just find a way not to need the server console ^^ > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/GameServerManagers/LinuxGSM/issues/1698#issuecomment-345848828>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AY9nomTWmVPev_pRMRXXN8owvL2yvH9mks5s4fnwgaJpZM4QjM5l> > . >

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@MarkTwoFive commented on GitHub (Nov 21, 2017):

The last one is propably the way to go for you. It is also the easiest.

@MarkTwoFive commented on GitHub (Nov 21, 2017): The last one is propably the way to go for you. It is also the easiest.

kerem commented

2026-02-27 02:56:31 +03:00

Author

Owner

@lock[bot] commented on GitHub (Nov 21, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Nov 21, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.