Hello,
Bash has a nice feature to walkthrough the lines of the command history by
arrow keys.
But when a command is executed and leaves arbitrary traces on stdout I am
forced to take the mouse to copy lines of interest
if I want to use it again.
Im not talking about directing the output of a comm
On Wed, Jun 17, 2015 at 04:05:56AM -0700, Hrazel wrote:
> Now it would be nice just to log the last lines on stdout and walk it
> through line by line ready to be put to the clipboard.
This has nothing to do with bash. You would have to request this
kind of feature at the terminal level (where "t
Hrazel writes:
> Now it would be nice just to log the last lines on stdout and walk it
> through line by line ready to be put to the clipboard.
M-x shell
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for
Hrazel wrote:
> It would be so cool just to [shift] + [arrow up] to go to the line of
> interest. [arrow right] to copy it to the clipboard and return to the
> normal console again. then I can decide what to do with it next.
This would need some type of wrapper around everything such as GNU
'sc
I was surprised when the following script did NOT exit at the indicated
line:
set -e
export X=$(false)
# should not reach here
echo did not exit
Similarly, this fails in the same way:
set -e
X=$(false) export X
# should not reach here
echo did not exit
while, conversely, this did exit as expect
