Matt Wozniski <[email protected]> [09-07-26 19:41]: > > On Thu, Jul 23, 2009 at 12:35 PM, <[email protected]> wrote: > > > > Tim Chase <[email protected]> [09-07-23 18:29]: > >> > >> > is it possible to vimdiff two "streams" coming from > >> > two stdin sources somehow? > >> > > >> > Thank you very much for any help in advance! > >> > >> Well, Vim only gets one "stdin". > >> > >> However, in bash, you can used anonymous pipes: > >> > >> vimdiff <(somecmd1 filea | filterX) <(somecmd2 fileb | filterY) > >> > >> to take the output of a series of commands and treat it as a > >> pseudo-file. In vim, you'd see this as editing /dev/fd/63 with a > >> note that it's a fifo/socket but you can write the results > >> wherever you want. > > > > Hi Tim, > > > > sounds good ! I am using zsh, but I think there are similiar > > mechanisms available as with bash. > > Yes, zsh supports both <(...) and >(...) as in bash, and also supports > =(...) which instead of giving you a read-only or write-only handle to > a FIFO on a file descriptor, gives you the name of a temporary file > that the shell will clean up after when the program is done. See man > zshexpn, the PROCESS SUBSTITUTION section. > > ~Matt > > THANK YOU ! :)
Meino -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
