Re: [Fish-users] Copying and pasting long commands

2012-08-29 Thread Maxim Gonchar
It seems that fish also puts hard new-line in the output, so the terminal do not reformat the buffer when resizing. I've created a ticket for things discussed here: https://github.com/fish-shell/fish-shell/issues/300 regards, Maxim On Fri, 24 Aug 2012 11:39:07 +0400, Jan Kanis wrote: > I pers

Re: [Fish-users] Copying and pasting long commands

2012-08-24 Thread Jan Kanis
I personally wouldn't find it a problem if both the ellipsis and the newline are removed from fish's output. On Fri, Aug 24, 2012 at 6:36 AM, Kevin Ballard wrote: > I'm pretty certain the shell can't prevent the ellipsis from getting into the > clipboard, since Terminal is copying the actual emi

Re: [Fish-users] Copying and pasting long commands

2012-08-23 Thread Kevin Ballard
I'm pretty certain the shell can't prevent the ellipsis from getting into the clipboard, since Terminal is copying the actual emitted text. In any case, I'm guessing bash doesn't bother to emit a hard newline and lets the terminal's wrapping take care of it, which allows the copy to work just f

Re: [Fish-users] Copying and pasting long commands

2012-08-23 Thread David Frascone
And, for those not running osx: codemonkey@monkeytree ~/W/MonkeyTools> alias pbcopy 'xsel --clipboard --input' codemonkey@monkeytree ~/W/MonkeyTools> alias pbpaste 'xsel --clipboard --output' -Dave On Thu, Aug 23, 2012 at 3:56 AM, Jon Clayden wrote: > Fair enough, but then why have the shell

Re: [Fish-users] Copying and pasting long commands

2012-08-23 Thread Jon Clayden
Fair enough, but then why have the shell insert the ellipsis characters in the first place? Personally I would rather not have the visual continuation cue and be able to copy/paste simply. Long commands can be copy/pasted perfectly successfully under bash, so unless Terminal.app does something spec

Re: [Fish-users] Copying and pasting long commands

2012-08-23 Thread pants
On Thu, Aug 23, 2012 at 08:24:55AM +0100, Jon Clayden wrote: > Surely it would be possible, however, for the shell to ignore the > ellipsis/newline sequence, at the very least? Rewriting the command to > remove it would be better still, but perhaps that's more tricky. Possible, but hardly desirabl

Re: [Fish-users] Copying and pasting long commands

2012-08-23 Thread Jon Clayden
Thanks for the responses, and for the suggestions. Surely it would be possible, however, for the shell to ignore the ellipsis/newline sequence, at the very least? Rewriting the command to remove it would be better still, but perhaps that's more tricky. All the best, Jon On 23 Aug 2012, at 07:

Re: [Fish-users] Copying and pasting long commands

2012-08-22 Thread Maxim Gonchar
You can also bind some key to save the current commandline: bind \ey 'commandline | pbcopy' Maxim On Thu, 23 Aug 2012 08:12:41 +0400, Kevin Ballard wrote: > Copying & Pasting is a terminal-level thing. You can only copy the > actual text that's rendered on the terminal. So yes, you're going t

Re: [Fish-users] Copying and pasting long commands

2012-08-22 Thread Kevin Ballard
Copying & Pasting is a terminal-level thing. You can only copy the actual text that's rendered on the terminal. So yes, you're going to get the ellipsis/newline as well. Sadly, there's no avoiding that. However, you could work around this by piping text to `pbcopy`. If you have a command in you

[Fish-users] Copying and pasting long commands

2012-08-22 Thread Jon Clayden
Dear all, Before raising an issue for this I wanted to check if this behaviour is intended or unavoidable. It seems that when long commands are copied and pasted between fish instances, the inserted ellipsis characters and line breaks are pasted too, and interpreted. The practical upshot of this i