Pushdown Terminal Output Announcing the arrival of Valued Associate #679: Cesar Manara ...
Did MS DOS itself ever use blinking text?
Has negative voting ever been officially implemented in elections, or seriously proposed, or even studied?
If my PI received research grants from a company to be able to pay my postdoc salary, did I have a potential conflict interest too?
How do I make this wiring inside cabinet safer? (Pic)
Why are there no cargo aircraft with "flying wing" design?
What causes the direction of lightning flashes?
Why are the trig functions versine, haversine, exsecant, etc, rarely used in modern mathematics?
Do square wave exist?
What would be the ideal power source for a cybernetic eye?
How to answer "Have you ever been terminated?"
How do I find out the mythology and history of my Fortress?
What's the meaning of "fortified infraction restraint"?
Can melee weapons be used to deliver Contact Poisons?
2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?
Amount of permutations on an NxNxN Rubik's Cube
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
If a VARCHAR(MAX) column is included in an index, is the entire value always stored in the index page(s)?
How to convince students of the implication truth values?
What do you call a floor made of glass so you can see through the floor?
Delete nth line from bottom
What is the longest distance a player character can jump in one leap?
Fantasy story; one type of magic grows in power with use, but the more powerful they are, they more they are drawn to travel to their source
Closed form of recurrent arithmetic series summation
What are the out-of-universe reasons for the references to Toby Maguire-era Spider-Man in ITSV
Pushdown Terminal Output
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionWhat part of the terminal stack is responsible for the direction of text being output?Shell console clearingCan the empty spaces/background in a terminal be replaced with a random(but pretty) pattern of ASCII characters?Save cursor position and restore it in terminalDifferent outputs to different terminals in UbuntuHighlight specific text in command output, allowing interaction with the commandControl characters in a terminal with an active foreground processIs it possible to prepend all terminal output with a certain character?Move terminal typed input to new line when console application/script displays output textHow can I get colors when executing `bash -c`?xdotool type and stty occasionally cut off first letter of input
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Is there a standard way to reverse the output order of a terminal output, ie:
~/Developer $ command0
-bash: comman0: command not found
~/Developer $ command2
-bash: command2: command not found
~/Developer $ command3
-bash: command3: command not found
~/Developer $
would be displayed as:
~/Developer $
-bash: command3: command not found
~/Developer $ command3
-bash: command2: command not found
~/Developer $ command2
-bash: comman0: command not found
~/Developer $ comman0
I feel always having your prompt at the bottom is counter intuitive a more effective way of presenting the output woud be to reverse the output order. How might I go about implementing this? Specifically where output portion of the OSX terminal program defined?
terminal
|
show 1 more comment
Is there a standard way to reverse the output order of a terminal output, ie:
~/Developer $ command0
-bash: comman0: command not found
~/Developer $ command2
-bash: command2: command not found
~/Developer $ command3
-bash: command3: command not found
~/Developer $
would be displayed as:
~/Developer $
-bash: command3: command not found
~/Developer $ command3
-bash: command2: command not found
~/Developer $ command2
-bash: comman0: command not found
~/Developer $ comman0
I feel always having your prompt at the bottom is counter intuitive a more effective way of presenting the output woud be to reverse the output order. How might I go about implementing this? Specifically where output portion of the OSX terminal program defined?
terminal
This would confuse me, but I applaud your efforts. On of linux/unix/open source major lesssons is that One Size Does Not Fit All.
– Bruce Ediger
Apr 3 '12 at 17:18
I think this is not possible at all unless you change the source code of the shell (e.g.bash
).
– Renan
Apr 3 '12 at 17:20
4
You'd need to hack more than just the shell. Terminals have been scrolling this way since they were electromechanical. At the very least, I'd say you'd need to hack a terminal emulator, maybe also a shell.
– Alexios
Apr 3 '12 at 17:31
This is actually counter intuitive. Have you noticed the ENTER key arrow? It points to the line below, not above.
– dresende
Apr 3 '12 at 18:07
Is there a way to grab the items of out put from a terminal, my thought is to create some sort of wrapper which grabs each of these output items, treats each of them similar to how tweets are posted with the newest always apear on top and sticking the input prompt at the top of the Wrapper UI.
– rudolph9
Apr 3 '12 at 21:13
|
show 1 more comment
Is there a standard way to reverse the output order of a terminal output, ie:
~/Developer $ command0
-bash: comman0: command not found
~/Developer $ command2
-bash: command2: command not found
~/Developer $ command3
-bash: command3: command not found
~/Developer $
would be displayed as:
~/Developer $
-bash: command3: command not found
~/Developer $ command3
-bash: command2: command not found
~/Developer $ command2
-bash: comman0: command not found
~/Developer $ comman0
I feel always having your prompt at the bottom is counter intuitive a more effective way of presenting the output woud be to reverse the output order. How might I go about implementing this? Specifically where output portion of the OSX terminal program defined?
terminal
Is there a standard way to reverse the output order of a terminal output, ie:
~/Developer $ command0
-bash: comman0: command not found
~/Developer $ command2
-bash: command2: command not found
~/Developer $ command3
-bash: command3: command not found
~/Developer $
would be displayed as:
~/Developer $
-bash: command3: command not found
~/Developer $ command3
-bash: command2: command not found
~/Developer $ command2
-bash: comman0: command not found
~/Developer $ comman0
I feel always having your prompt at the bottom is counter intuitive a more effective way of presenting the output woud be to reverse the output order. How might I go about implementing this? Specifically where output portion of the OSX terminal program defined?
terminal
terminal
asked Apr 3 '12 at 17:16
rudolph9rudolph9
6601123
6601123
This would confuse me, but I applaud your efforts. On of linux/unix/open source major lesssons is that One Size Does Not Fit All.
– Bruce Ediger
Apr 3 '12 at 17:18
I think this is not possible at all unless you change the source code of the shell (e.g.bash
).
– Renan
Apr 3 '12 at 17:20
4
You'd need to hack more than just the shell. Terminals have been scrolling this way since they were electromechanical. At the very least, I'd say you'd need to hack a terminal emulator, maybe also a shell.
– Alexios
Apr 3 '12 at 17:31
This is actually counter intuitive. Have you noticed the ENTER key arrow? It points to the line below, not above.
– dresende
Apr 3 '12 at 18:07
Is there a way to grab the items of out put from a terminal, my thought is to create some sort of wrapper which grabs each of these output items, treats each of them similar to how tweets are posted with the newest always apear on top and sticking the input prompt at the top of the Wrapper UI.
– rudolph9
Apr 3 '12 at 21:13
|
show 1 more comment
This would confuse me, but I applaud your efforts. On of linux/unix/open source major lesssons is that One Size Does Not Fit All.
– Bruce Ediger
Apr 3 '12 at 17:18
I think this is not possible at all unless you change the source code of the shell (e.g.bash
).
– Renan
Apr 3 '12 at 17:20
4
You'd need to hack more than just the shell. Terminals have been scrolling this way since they were electromechanical. At the very least, I'd say you'd need to hack a terminal emulator, maybe also a shell.
– Alexios
Apr 3 '12 at 17:31
This is actually counter intuitive. Have you noticed the ENTER key arrow? It points to the line below, not above.
– dresende
Apr 3 '12 at 18:07
Is there a way to grab the items of out put from a terminal, my thought is to create some sort of wrapper which grabs each of these output items, treats each of them similar to how tweets are posted with the newest always apear on top and sticking the input prompt at the top of the Wrapper UI.
– rudolph9
Apr 3 '12 at 21:13
This would confuse me, but I applaud your efforts. On of linux/unix/open source major lesssons is that One Size Does Not Fit All.
– Bruce Ediger
Apr 3 '12 at 17:18
This would confuse me, but I applaud your efforts. On of linux/unix/open source major lesssons is that One Size Does Not Fit All.
– Bruce Ediger
Apr 3 '12 at 17:18
I think this is not possible at all unless you change the source code of the shell (e.g.
bash
).– Renan
Apr 3 '12 at 17:20
I think this is not possible at all unless you change the source code of the shell (e.g.
bash
).– Renan
Apr 3 '12 at 17:20
4
4
You'd need to hack more than just the shell. Terminals have been scrolling this way since they were electromechanical. At the very least, I'd say you'd need to hack a terminal emulator, maybe also a shell.
– Alexios
Apr 3 '12 at 17:31
You'd need to hack more than just the shell. Terminals have been scrolling this way since they were electromechanical. At the very least, I'd say you'd need to hack a terminal emulator, maybe also a shell.
– Alexios
Apr 3 '12 at 17:31
This is actually counter intuitive. Have you noticed the ENTER key arrow? It points to the line below, not above.
– dresende
Apr 3 '12 at 18:07
This is actually counter intuitive. Have you noticed the ENTER key arrow? It points to the line below, not above.
– dresende
Apr 3 '12 at 18:07
Is there a way to grab the items of out put from a terminal, my thought is to create some sort of wrapper which grabs each of these output items, treats each of them similar to how tweets are posted with the newest always apear on top and sticking the input prompt at the top of the Wrapper UI.
– rudolph9
Apr 3 '12 at 21:13
Is there a way to grab the items of out put from a terminal, my thought is to create some sort of wrapper which grabs each of these output items, treats each of them similar to how tweets are posted with the newest always apear on top and sticking the input prompt at the top of the Wrapper UI.
– rudolph9
Apr 3 '12 at 21:13
|
show 1 more comment
3 Answers
3
active
oldest
votes
In bash this will display the current prompt/command at the top, and its output below, but with no scrolling or previous commands:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1'
This function will put previous commands below, but you have to pipe each and every command to it individually. Unfortunately, exec > >(f)
can't help with this as it redirects the whole of bash, not individual commands. Here's the function:
f () { tee ~/.STDIN | wc -l | xargs expr 1 + | xargs tput il && cat ~/.STDIN; }
Then run every command like:
command args |f
It saves the output, creates a number of blank lines equal to length+1, then puts the output back in. You can tag a line on at the end that will display a fake prompt or horizontal rule if you like. E.g.
printf '%*s' $COLUMNS | tr ' ' _;
As a crap but automatic alternative to this whole function thing, we can add a command to the end of our earlier $PROMPT_COMMAND that clears a somewhat arbitrary 11 lines:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1; tput il 11'
You can also use tput -S
to avoid multiple binary calls.
I got the $PROMPT_COMMAND
from https://github.com/swirepe/alwaysontop .
add a comment |
Unfortunately, this will be fairly difficult. The protocol between the applications and the OS-X terminal is a variant of the VT100 / ANSI terminal control protocol, specifically the XTerm protocol.
That includes a bunch of assumptions about screen position, etc, that would be challenging to remap to a world where the display was reversed.
Even worse, all your terminal emulator gets is a string of "put this character at this position" type commands. There is no distinction made between the command prompt and the output of a command run by it, so you can't do one thing for both parts - at least, not without cooperation from the shell underneath.
The shell, and the programs, assume that the screen proceeds upwards - new data at the bottom, and carries on downward forever.
You could, at least theoretically, have your terminal emulator modified so that it displayed lines in reverse order - the "bottom" line first, and so on up to the "top" line at the bottom of the screen.
That would reverse the order of lines in command output, though, so the rest of the content would pop out backwards too. If you wanted the commands (eg: ls, cat) to run "down" but prompts to move "up" life is harder.
I don't know any software that implements this. (...but see JdeBD's comment to this for a link to one.) :)
I do. (-:
– JdeBP
Aug 27 '18 at 19:54
add a comment |
Although this won't exactly reverse output, it will keep your prompt at the top:
https://github.com/swirepe/alwaysontop
To use it run:
git clone https://github.com/swirepe/alwaysontop.git
cd alwaysontop/
source alwaysontop.sh
If you decide you like it just source it in your .bash_profile with something like:
echo "source ~/alwaysontop/alwaysontop.sh" >> ~/.bash_profile
This is a bit buggy (e.g. with tab-autocomplete and history) but it's a very good demo of what this UI might feel like if it was implemented properly. I think it's valuable for that - to help people know if they'd want it or not!
– scipilot
Apr 27 '17 at 4:34
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/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
});
}
});
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%2f35627%2fpushdown-terminal-output%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
In bash this will display the current prompt/command at the top, and its output below, but with no scrolling or previous commands:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1'
This function will put previous commands below, but you have to pipe each and every command to it individually. Unfortunately, exec > >(f)
can't help with this as it redirects the whole of bash, not individual commands. Here's the function:
f () { tee ~/.STDIN | wc -l | xargs expr 1 + | xargs tput il && cat ~/.STDIN; }
Then run every command like:
command args |f
It saves the output, creates a number of blank lines equal to length+1, then puts the output back in. You can tag a line on at the end that will display a fake prompt or horizontal rule if you like. E.g.
printf '%*s' $COLUMNS | tr ' ' _;
As a crap but automatic alternative to this whole function thing, we can add a command to the end of our earlier $PROMPT_COMMAND that clears a somewhat arbitrary 11 lines:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1; tput il 11'
You can also use tput -S
to avoid multiple binary calls.
I got the $PROMPT_COMMAND
from https://github.com/swirepe/alwaysontop .
add a comment |
In bash this will display the current prompt/command at the top, and its output below, but with no scrolling or previous commands:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1'
This function will put previous commands below, but you have to pipe each and every command to it individually. Unfortunately, exec > >(f)
can't help with this as it redirects the whole of bash, not individual commands. Here's the function:
f () { tee ~/.STDIN | wc -l | xargs expr 1 + | xargs tput il && cat ~/.STDIN; }
Then run every command like:
command args |f
It saves the output, creates a number of blank lines equal to length+1, then puts the output back in. You can tag a line on at the end that will display a fake prompt or horizontal rule if you like. E.g.
printf '%*s' $COLUMNS | tr ' ' _;
As a crap but automatic alternative to this whole function thing, we can add a command to the end of our earlier $PROMPT_COMMAND that clears a somewhat arbitrary 11 lines:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1; tput il 11'
You can also use tput -S
to avoid multiple binary calls.
I got the $PROMPT_COMMAND
from https://github.com/swirepe/alwaysontop .
add a comment |
In bash this will display the current prompt/command at the top, and its output below, but with no scrolling or previous commands:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1'
This function will put previous commands below, but you have to pipe each and every command to it individually. Unfortunately, exec > >(f)
can't help with this as it redirects the whole of bash, not individual commands. Here's the function:
f () { tee ~/.STDIN | wc -l | xargs expr 1 + | xargs tput il && cat ~/.STDIN; }
Then run every command like:
command args |f
It saves the output, creates a number of blank lines equal to length+1, then puts the output back in. You can tag a line on at the end that will display a fake prompt or horizontal rule if you like. E.g.
printf '%*s' $COLUMNS | tr ' ' _;
As a crap but automatic alternative to this whole function thing, we can add a command to the end of our earlier $PROMPT_COMMAND that clears a somewhat arbitrary 11 lines:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1; tput il 11'
You can also use tput -S
to avoid multiple binary calls.
I got the $PROMPT_COMMAND
from https://github.com/swirepe/alwaysontop .
In bash this will display the current prompt/command at the top, and its output below, but with no scrolling or previous commands:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1'
This function will put previous commands below, but you have to pipe each and every command to it individually. Unfortunately, exec > >(f)
can't help with this as it redirects the whole of bash, not individual commands. Here's the function:
f () { tee ~/.STDIN | wc -l | xargs expr 1 + | xargs tput il && cat ~/.STDIN; }
Then run every command like:
command args |f
It saves the output, creates a number of blank lines equal to length+1, then puts the output back in. You can tag a line on at the end that will display a fake prompt or horizontal rule if you like. E.g.
printf '%*s' $COLUMNS | tr ' ' _;
As a crap but automatic alternative to this whole function thing, we can add a command to the end of our earlier $PROMPT_COMMAND that clears a somewhat arbitrary 11 lines:
PROMPT_COMMAND='tput cup 0 0; tput el; tput el1; tput il 11'
You can also use tput -S
to avoid multiple binary calls.
I got the $PROMPT_COMMAND
from https://github.com/swirepe/alwaysontop .
edited Oct 14 '13 at 5:15
answered Oct 14 '13 at 4:44
Tommy JollyboatTommy Jollyboat
5112
5112
add a comment |
add a comment |
Unfortunately, this will be fairly difficult. The protocol between the applications and the OS-X terminal is a variant of the VT100 / ANSI terminal control protocol, specifically the XTerm protocol.
That includes a bunch of assumptions about screen position, etc, that would be challenging to remap to a world where the display was reversed.
Even worse, all your terminal emulator gets is a string of "put this character at this position" type commands. There is no distinction made between the command prompt and the output of a command run by it, so you can't do one thing for both parts - at least, not without cooperation from the shell underneath.
The shell, and the programs, assume that the screen proceeds upwards - new data at the bottom, and carries on downward forever.
You could, at least theoretically, have your terminal emulator modified so that it displayed lines in reverse order - the "bottom" line first, and so on up to the "top" line at the bottom of the screen.
That would reverse the order of lines in command output, though, so the rest of the content would pop out backwards too. If you wanted the commands (eg: ls, cat) to run "down" but prompts to move "up" life is harder.
I don't know any software that implements this. (...but see JdeBD's comment to this for a link to one.) :)
I do. (-:
– JdeBP
Aug 27 '18 at 19:54
add a comment |
Unfortunately, this will be fairly difficult. The protocol between the applications and the OS-X terminal is a variant of the VT100 / ANSI terminal control protocol, specifically the XTerm protocol.
That includes a bunch of assumptions about screen position, etc, that would be challenging to remap to a world where the display was reversed.
Even worse, all your terminal emulator gets is a string of "put this character at this position" type commands. There is no distinction made between the command prompt and the output of a command run by it, so you can't do one thing for both parts - at least, not without cooperation from the shell underneath.
The shell, and the programs, assume that the screen proceeds upwards - new data at the bottom, and carries on downward forever.
You could, at least theoretically, have your terminal emulator modified so that it displayed lines in reverse order - the "bottom" line first, and so on up to the "top" line at the bottom of the screen.
That would reverse the order of lines in command output, though, so the rest of the content would pop out backwards too. If you wanted the commands (eg: ls, cat) to run "down" but prompts to move "up" life is harder.
I don't know any software that implements this. (...but see JdeBD's comment to this for a link to one.) :)
I do. (-:
– JdeBP
Aug 27 '18 at 19:54
add a comment |
Unfortunately, this will be fairly difficult. The protocol between the applications and the OS-X terminal is a variant of the VT100 / ANSI terminal control protocol, specifically the XTerm protocol.
That includes a bunch of assumptions about screen position, etc, that would be challenging to remap to a world where the display was reversed.
Even worse, all your terminal emulator gets is a string of "put this character at this position" type commands. There is no distinction made between the command prompt and the output of a command run by it, so you can't do one thing for both parts - at least, not without cooperation from the shell underneath.
The shell, and the programs, assume that the screen proceeds upwards - new data at the bottom, and carries on downward forever.
You could, at least theoretically, have your terminal emulator modified so that it displayed lines in reverse order - the "bottom" line first, and so on up to the "top" line at the bottom of the screen.
That would reverse the order of lines in command output, though, so the rest of the content would pop out backwards too. If you wanted the commands (eg: ls, cat) to run "down" but prompts to move "up" life is harder.
I don't know any software that implements this. (...but see JdeBD's comment to this for a link to one.) :)
Unfortunately, this will be fairly difficult. The protocol between the applications and the OS-X terminal is a variant of the VT100 / ANSI terminal control protocol, specifically the XTerm protocol.
That includes a bunch of assumptions about screen position, etc, that would be challenging to remap to a world where the display was reversed.
Even worse, all your terminal emulator gets is a string of "put this character at this position" type commands. There is no distinction made between the command prompt and the output of a command run by it, so you can't do one thing for both parts - at least, not without cooperation from the shell underneath.
The shell, and the programs, assume that the screen proceeds upwards - new data at the bottom, and carries on downward forever.
You could, at least theoretically, have your terminal emulator modified so that it displayed lines in reverse order - the "bottom" line first, and so on up to the "top" line at the bottom of the screen.
That would reverse the order of lines in command output, though, so the rest of the content would pop out backwards too. If you wanted the commands (eg: ls, cat) to run "down" but prompts to move "up" life is harder.
I don't know any software that implements this. (...but see JdeBD's comment to this for a link to one.) :)
edited Aug 31 '18 at 17:12
answered Apr 3 '12 at 17:28
Daniel PittmanDaniel Pittman
5,60712317
5,60712317
I do. (-:
– JdeBP
Aug 27 '18 at 19:54
add a comment |
I do. (-:
– JdeBP
Aug 27 '18 at 19:54
I do. (-:
– JdeBP
Aug 27 '18 at 19:54
I do. (-:
– JdeBP
Aug 27 '18 at 19:54
add a comment |
Although this won't exactly reverse output, it will keep your prompt at the top:
https://github.com/swirepe/alwaysontop
To use it run:
git clone https://github.com/swirepe/alwaysontop.git
cd alwaysontop/
source alwaysontop.sh
If you decide you like it just source it in your .bash_profile with something like:
echo "source ~/alwaysontop/alwaysontop.sh" >> ~/.bash_profile
This is a bit buggy (e.g. with tab-autocomplete and history) but it's a very good demo of what this UI might feel like if it was implemented properly. I think it's valuable for that - to help people know if they'd want it or not!
– scipilot
Apr 27 '17 at 4:34
add a comment |
Although this won't exactly reverse output, it will keep your prompt at the top:
https://github.com/swirepe/alwaysontop
To use it run:
git clone https://github.com/swirepe/alwaysontop.git
cd alwaysontop/
source alwaysontop.sh
If you decide you like it just source it in your .bash_profile with something like:
echo "source ~/alwaysontop/alwaysontop.sh" >> ~/.bash_profile
This is a bit buggy (e.g. with tab-autocomplete and history) but it's a very good demo of what this UI might feel like if it was implemented properly. I think it's valuable for that - to help people know if they'd want it or not!
– scipilot
Apr 27 '17 at 4:34
add a comment |
Although this won't exactly reverse output, it will keep your prompt at the top:
https://github.com/swirepe/alwaysontop
To use it run:
git clone https://github.com/swirepe/alwaysontop.git
cd alwaysontop/
source alwaysontop.sh
If you decide you like it just source it in your .bash_profile with something like:
echo "source ~/alwaysontop/alwaysontop.sh" >> ~/.bash_profile
Although this won't exactly reverse output, it will keep your prompt at the top:
https://github.com/swirepe/alwaysontop
To use it run:
git clone https://github.com/swirepe/alwaysontop.git
cd alwaysontop/
source alwaysontop.sh
If you decide you like it just source it in your .bash_profile with something like:
echo "source ~/alwaysontop/alwaysontop.sh" >> ~/.bash_profile
edited 6 hours ago
Rui F Ribeiro
42.1k1484142
42.1k1484142
answered Oct 10 '14 at 23:05
ryanpcmcquenryanpcmcquen
1515
1515
This is a bit buggy (e.g. with tab-autocomplete and history) but it's a very good demo of what this UI might feel like if it was implemented properly. I think it's valuable for that - to help people know if they'd want it or not!
– scipilot
Apr 27 '17 at 4:34
add a comment |
This is a bit buggy (e.g. with tab-autocomplete and history) but it's a very good demo of what this UI might feel like if it was implemented properly. I think it's valuable for that - to help people know if they'd want it or not!
– scipilot
Apr 27 '17 at 4:34
This is a bit buggy (e.g. with tab-autocomplete and history) but it's a very good demo of what this UI might feel like if it was implemented properly. I think it's valuable for that - to help people know if they'd want it or not!
– scipilot
Apr 27 '17 at 4:34
This is a bit buggy (e.g. with tab-autocomplete and history) but it's a very good demo of what this UI might feel like if it was implemented properly. I think it's valuable for that - to help people know if they'd want it or not!
– scipilot
Apr 27 '17 at 4:34
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%2f35627%2fpushdown-terminal-output%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
This would confuse me, but I applaud your efforts. On of linux/unix/open source major lesssons is that One Size Does Not Fit All.
– Bruce Ediger
Apr 3 '12 at 17:18
I think this is not possible at all unless you change the source code of the shell (e.g.
bash
).– Renan
Apr 3 '12 at 17:20
4
You'd need to hack more than just the shell. Terminals have been scrolling this way since they were electromechanical. At the very least, I'd say you'd need to hack a terminal emulator, maybe also a shell.
– Alexios
Apr 3 '12 at 17:31
This is actually counter intuitive. Have you noticed the ENTER key arrow? It points to the line below, not above.
– dresende
Apr 3 '12 at 18:07
Is there a way to grab the items of out put from a terminal, my thought is to create some sort of wrapper which grabs each of these output items, treats each of them similar to how tweets are posted with the newest always apear on top and sticking the input prompt at the top of the Wrapper UI.
– rudolph9
Apr 3 '12 at 21:13