Bash attempts to write two shell prompts?Can the empty spaces/background in a terminal be replaced with a random(but pretty) pattern of ASCII characters?How to write conditional if statement in bash shell script?Bash: show prompts if arguments weren't providedHow do I avoid echoing password (two simultaneous prompts)?bash: no job control in this shellBash shell script program that prompts for and reads two integers from the user.Find unused tty in the shell like bash?BASH question: using read, can I capture a single char OR arrow key (on keyup)
A Pixelated Sequence - Find the Continuation
Python web-scraper to download table of transistor counts from Wikipedia
What are some examples of research that does not solve a existing problem (maybe the problem is not obvious yet) but present a unique discovery?
What is the difference between an engine skirt and an engine nozzle?
What are the typical trumpet parts in classical music?
What does the Free Recovery sign (UK) actually mean?
Why is the UK still pressing on with Brexit?
Why is the year in this ISO timestamp not 2019?
Is there a tool to measure the "maturity" of a code in Git?
Why cannot a convert make certain statements? I feel they are being pushed away at the same time respect is being given to them
What is this WWII four-engine plane on skis?
Wouldn't Kreacher have been able to escape even without following an order?
What is the word for a person who destroys monuments?
Which version of the Pigeonhole principle is correct? One is far stronger than the other
Answer not a fool, or answer a fool?
Bash attempts to write two shell prompts?
Madrid to London w/ Expired 90/180 days stay as US citizen
Degenerate Gaussian Integral
Exam design: give maximum score per question or not?
Permutations in Disguise
Did slaves have slaves?
What does the "capacitor into resistance" symbol mean?
How to make classical firearms effective on space habitats despite the coriolis effect?
Why does dd not make working bootable USB sticks for Microsoft?
Bash attempts to write two shell prompts?
Can the empty spaces/background in a terminal be replaced with a random(but pretty) pattern of ASCII characters?How to write conditional if statement in bash shell script?Bash: show prompts if arguments weren't providedHow do I avoid echoing password (two simultaneous prompts)?bash: no job control in this shellBash shell script program that prompts for and reads two integers from the user.Find unused tty in the shell like bash?BASH question: using read, can I capture a single char OR arrow key (on keyup)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am looking at the strace output of a running bash process connected to
a terminal, for educational purposes.
My bash process has PID 2883.
I type
[OP@localhost ~]$ strace -e trace=openat,read,write,fork,vfork,clone,execve -p 2883 2> bash.strace
Into a terminal. I then go into my bash process, and have the following
interaction:
[OP@localhost ~]$ ls
Looking at the output, I see
strace: Process 2883 attached
read(0, "l", 1) = 1
write(2, "l", 1) = 1
read(0, "s", 1) = 1
write(2, "s", 1) = 1
read(0, "r", 1) = 1
write(2, "n", 1) = 1
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fec6b1d8e50) = 3917
--- SIGCHLD si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3917, si_uid=1000, si_status=0, si_utime=0, si_stime=0 ---
write(1, "33]0;OP@localhost:~7", 23) = 23
write(2, "[OP@localhost ~]$ ", 22) = 22
...
I am confused at the last two lines. It appears that bash is attempting
to write two shell prompts? What's going on here?
bash tty strace
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
add a comment
|
I am looking at the strace output of a running bash process connected to
a terminal, for educational purposes.
My bash process has PID 2883.
I type
[OP@localhost ~]$ strace -e trace=openat,read,write,fork,vfork,clone,execve -p 2883 2> bash.strace
Into a terminal. I then go into my bash process, and have the following
interaction:
[OP@localhost ~]$ ls
Looking at the output, I see
strace: Process 2883 attached
read(0, "l", 1) = 1
write(2, "l", 1) = 1
read(0, "s", 1) = 1
write(2, "s", 1) = 1
read(0, "r", 1) = 1
write(2, "n", 1) = 1
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fec6b1d8e50) = 3917
--- SIGCHLD si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3917, si_uid=1000, si_status=0, si_utime=0, si_stime=0 ---
write(1, "33]0;OP@localhost:~7", 23) = 23
write(2, "[OP@localhost ~]$ ", 22) = 22
...
I am confused at the last two lines. It appears that bash is attempting
to write two shell prompts? What's going on here?
bash tty strace
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
add a comment
|
I am looking at the strace output of a running bash process connected to
a terminal, for educational purposes.
My bash process has PID 2883.
I type
[OP@localhost ~]$ strace -e trace=openat,read,write,fork,vfork,clone,execve -p 2883 2> bash.strace
Into a terminal. I then go into my bash process, and have the following
interaction:
[OP@localhost ~]$ ls
Looking at the output, I see
strace: Process 2883 attached
read(0, "l", 1) = 1
write(2, "l", 1) = 1
read(0, "s", 1) = 1
write(2, "s", 1) = 1
read(0, "r", 1) = 1
write(2, "n", 1) = 1
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fec6b1d8e50) = 3917
--- SIGCHLD si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3917, si_uid=1000, si_status=0, si_utime=0, si_stime=0 ---
write(1, "33]0;OP@localhost:~7", 23) = 23
write(2, "[OP@localhost ~]$ ", 22) = 22
...
I am confused at the last two lines. It appears that bash is attempting
to write two shell prompts? What's going on here?
bash tty strace
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
I am looking at the strace output of a running bash process connected to
a terminal, for educational purposes.
My bash process has PID 2883.
I type
[OP@localhost ~]$ strace -e trace=openat,read,write,fork,vfork,clone,execve -p 2883 2> bash.strace
Into a terminal. I then go into my bash process, and have the following
interaction:
[OP@localhost ~]$ ls
Looking at the output, I see
strace: Process 2883 attached
read(0, "l", 1) = 1
write(2, "l", 1) = 1
read(0, "s", 1) = 1
write(2, "s", 1) = 1
read(0, "r", 1) = 1
write(2, "n", 1) = 1
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fec6b1d8e50) = 3917
--- SIGCHLD si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3917, si_uid=1000, si_status=0, si_utime=0, si_stime=0 ---
write(1, "33]0;OP@localhost:~7", 23) = 23
write(2, "[OP@localhost ~]$ ", 22) = 22
...
I am confused at the last two lines. It appears that bash is attempting
to write two shell prompts? What's going on here?
bash tty strace
bash tty strace
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
asked 9 hours ago
extremeaxe5extremeaxe5
4033 silver badges10 bronze badges
4033 silver badges10 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
The <ESC>]0; sequence (shown as 33]0; by strace) is the escape sequence to set the terminal window title. It's terminated with the BEL character (7), so the first write sets the window title. The second prints the actual prompt. Note that even apart from the escape sequence, they're not exactly the same. The prompt has a surrounding [..] while the window title doesn't.
We can also see that the first write goes to stdout (fd 1, the first argument to write()), and the second to stderr. Bash prints the prompt to stderr, so the first write comes from somewhere else. That somewhere is probably PROMPT_COMMAND, like the one in Debian's default startup scripts for Bash. There's something like this in there:
case "$TERM" in
xterm*|rxvt*)
PROMPT_COMMAND='echo -ne "33]0;$USER@$HOSTNAME: $PWD07"'
;;
*)
;;
esac
It sets that PROMPT_COMMAND if running xterm or rxvt, which should support that escape sequence.
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
add a comment
|
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/4.0/"u003ecc by-sa 4.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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f541909%2fbash-attempts-to-write-two-shell-prompts%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The <ESC>]0; sequence (shown as 33]0; by strace) is the escape sequence to set the terminal window title. It's terminated with the BEL character (7), so the first write sets the window title. The second prints the actual prompt. Note that even apart from the escape sequence, they're not exactly the same. The prompt has a surrounding [..] while the window title doesn't.
We can also see that the first write goes to stdout (fd 1, the first argument to write()), and the second to stderr. Bash prints the prompt to stderr, so the first write comes from somewhere else. That somewhere is probably PROMPT_COMMAND, like the one in Debian's default startup scripts for Bash. There's something like this in there:
case "$TERM" in
xterm*|rxvt*)
PROMPT_COMMAND='echo -ne "33]0;$USER@$HOSTNAME: $PWD07"'
;;
*)
;;
esac
It sets that PROMPT_COMMAND if running xterm or rxvt, which should support that escape sequence.
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
add a comment
|
The <ESC>]0; sequence (shown as 33]0; by strace) is the escape sequence to set the terminal window title. It's terminated with the BEL character (7), so the first write sets the window title. The second prints the actual prompt. Note that even apart from the escape sequence, they're not exactly the same. The prompt has a surrounding [..] while the window title doesn't.
We can also see that the first write goes to stdout (fd 1, the first argument to write()), and the second to stderr. Bash prints the prompt to stderr, so the first write comes from somewhere else. That somewhere is probably PROMPT_COMMAND, like the one in Debian's default startup scripts for Bash. There's something like this in there:
case "$TERM" in
xterm*|rxvt*)
PROMPT_COMMAND='echo -ne "33]0;$USER@$HOSTNAME: $PWD07"'
;;
*)
;;
esac
It sets that PROMPT_COMMAND if running xterm or rxvt, which should support that escape sequence.
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
add a comment
|
The <ESC>]0; sequence (shown as 33]0; by strace) is the escape sequence to set the terminal window title. It's terminated with the BEL character (7), so the first write sets the window title. The second prints the actual prompt. Note that even apart from the escape sequence, they're not exactly the same. The prompt has a surrounding [..] while the window title doesn't.
We can also see that the first write goes to stdout (fd 1, the first argument to write()), and the second to stderr. Bash prints the prompt to stderr, so the first write comes from somewhere else. That somewhere is probably PROMPT_COMMAND, like the one in Debian's default startup scripts for Bash. There's something like this in there:
case "$TERM" in
xterm*|rxvt*)
PROMPT_COMMAND='echo -ne "33]0;$USER@$HOSTNAME: $PWD07"'
;;
*)
;;
esac
It sets that PROMPT_COMMAND if running xterm or rxvt, which should support that escape sequence.
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
The <ESC>]0; sequence (shown as 33]0; by strace) is the escape sequence to set the terminal window title. It's terminated with the BEL character (7), so the first write sets the window title. The second prints the actual prompt. Note that even apart from the escape sequence, they're not exactly the same. The prompt has a surrounding [..] while the window title doesn't.
We can also see that the first write goes to stdout (fd 1, the first argument to write()), and the second to stderr. Bash prints the prompt to stderr, so the first write comes from somewhere else. That somewhere is probably PROMPT_COMMAND, like the one in Debian's default startup scripts for Bash. There's something like this in there:
case "$TERM" in
xterm*|rxvt*)
PROMPT_COMMAND='echo -ne "33]0;$USER@$HOSTNAME: $PWD07"'
;;
*)
;;
esac
It sets that PROMPT_COMMAND if running xterm or rxvt, which should support that escape sequence.
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
answered 8 hours ago
ilkkachuilkkachu
68.8k10 gold badges113 silver badges198 bronze badges
68.8k10 gold badges113 silver badges198 bronze badges
add a comment
|
add a comment
|
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f541909%2fbash-attempts-to-write-two-shell-prompts%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
