Re: Perform diff as exact line match

2018-06-29 Thread Tim Chase
On 2018-06-28 18:30, Joseph L. Casale wrote: > Does a means or plugin exist to perform a diff between two > tabs/files that compares entire lines? I've occasionally hacked this by inserting a unique tag (usually just an incrementing number) after each line in the file, something like :windo

Re: Perform diff as exact line match

2018-06-29 Thread Gary Johnson
On 2018-06-29, arocker wrote: > >> diff --changed-group-format= file1 file2 > >> comm -12 file1 file2 > >> > > > That's insightful but is the side-by-side comparison I was hoping for in > > vim so I could visually assess how the collections differed. > > > > Pipe into less? E.g. comm

Re: Perform diff as exact line match

2018-06-29 Thread Arun
On Fri, Jun 29, 2018 at 6:19 AM, Joseph L. Casale wrote: > On Thursday, June 28, 2018 at 7:46:51 PM UTC-6, Tony Mechelynck wrote: > > No plugin required, provided that you have a Vim compiled with +diff > > and that the diff utility is installed and can be found on your $PATH. > > > > See ":help

Re: Perform diff as exact line match

2018-06-29 Thread Joseph L. Casale
On Friday, June 29, 2018 at 10:55:25 AM UTC-6, Gary Johnson wrote: > There's also sdiff: > > sdiff file1 file2 | less > > or > > sdiff file1 file2 | vim - That worked brilliantly! Thanks. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply

debugging vim via gdb, best practices

2018-06-29 Thread Greg Mattson
all, I was wondering, what is the best method to use for debugging vim itself? I'd like to be able to load up an interactive vim session in one window, and attach to the vim process in another, be able to set breakpoints, etc in such a way that I minimize the interference to the underlying

Re: Perform diff as exact line match

2018-06-29 Thread Joseph L. Casale
On Friday, June 29, 2018 at 8:57:45 AM UTC-6, Gary Johnson wrote: > I _think_ I understand what you want, but I don't know of a way to > make Vim's internal comparison algorithm do that. > > Either of these two Linux commands will generate an output of only > the lines common to file1 and file2,

Re: Perform diff as exact line match

2018-06-29 Thread arocker
>> diff --changed-group-format= file1 file2 >> comm -12 file1 file2 >> > That's insightful but is the side-by-side comparison I was hoping for in > vim so I could visually assess how the collections differed. > Pipe into less? E.g. comm -12 file1 file2 | less -- -- You received

Re: Perform diff as exact line match

2018-06-29 Thread Gary Johnson
On 2018-06-29, Joseph L. Casale wrote: > On Thursday, June 28, 2018 at 7:46:51 PM UTC-6, Tony Mechelynck wrote: > > No plugin required, provided that you have a Vim compiled with +diff > > and that the diff utility is installed and can be found on your $PATH. > > > > See ":help diff.txt" > > Hi

Re: Perform diff as exact line match

2018-06-29 Thread Joseph L. Casale
On Thursday, June 28, 2018 at 7:46:51 PM UTC-6, Tony Mechelynck wrote: > No plugin required, provided that you have a Vim compiled with +diff > and that the diff utility is installed and can be found on your $PATH. > > See ":help diff.txt" Hi Tony, Specifically, I need to match lines completely